| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Single MQM supports multiple testing environment |
« View previous topic :: View next topic » |
| Author |
Message
|
| mqsme |
 Posted: Wed Oct 11, 2017 1:44 pm Post subject: Single MQM supports multiple testing environment |
 |
|
Acolyte
Joined: 16 Sep 2013
Posts: 51
|
Hi,
If i want to configure single MQM to support different testing environments like below, instead of setting up multiple MQM, what do you think?
ENV1 sender --> MQM.Queue.ENV1 --> ENV1 consumer
ENV2 sender --> MQM.Queue.ENV2 --> ENV2 consumer
ENV3 sender --> MQM.Queue.ENV3 --> ENV3 consumer
setting up a new MQ with environment as suffix is easier for me to setup new server, install new IBM MQ and create new MQ manager
Sorry for my poor searching skill. Haven't found any discussion about this idea on the web, can only find topics about mutli-instance or clustering.
thanks. |
|
| Back to top |
|
 |
| exerk |
| Posted: Wed Oct 11, 2017 2:16 pm Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
The number of queue managers on a single node is governed by the resources available on that node - you can have as many as capacity will allow.
If you are asking whether you can have one queue manager, which hosts queues for different environments then the answer is yes - a single queue manager can host those environments, but it's up to you to ensure the applications in one 'environment' do not interfere with messages from another.
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
|
| gbaddeley |
| Posted: Wed Oct 11, 2017 3:43 pm Post subject: |
|
|
Jedi Knight
Joined: 25 Mar 2003
Posts: 2538
Location: Melbourne, Australia
|
It is a valid technique to use queue name suffixes to indicate the environment. A down side is that each app environment needs to be separately configured to use different queue names.
A common simplification is to use the same queue names across all environments, but use different queue manager names. This makes app deployment through the environment stages a bit easier.
This also insulates the test environments from each other. ie. A qmgr for one environment can be restarted, reconfigured etc. without affecting the other environments' qmgrs.
It is not a big deal to run multiple qmgrs on one server. I have seen up to 10 running on a moderately resourced server. YMMV.
_________________
Glenn |
|
| Back to top |
|
|
| mqsme |
| Posted: Wed Oct 11, 2017 4:42 pm Post subject: |
|
|
Acolyte
Joined: 16 Sep 2013
Posts: 51
|
| thanks exerk and gbaddeley's reply. Actually i also like gbaddeley's idea to create multiple MQM. it save the effort of creating new VM but can separate messages. |
|
| Back to top |
|
|
| JosephGramig |
| Posted: Tue Oct 17, 2017 6:30 am Post subject: |
|
|
Grand Master
Joined: 09 Feb 2006
Posts: 1244
Location: Gold Coast of Florida, USA
|
By "MQM" do you mean Qmgrs (aka Queue Managers)?
I would prefix queue names with the environment rather than use suffixes. Then you can apply security to those queues more generically. But that is just me. |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
