| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| two different qmgrs for both broker and configmgr |
« View previous topic :: View next topic » |
| Author |
Message
|
| dotaneli |
 Posted: Tue Jun 12, 2007 1:08 am Post subject: two different qmgrs for both broker and configmgr |
 |
|
Voyager
Joined: 19 Oct 2005
Posts: 99
Location: Israel
|
Hello everyone,
I have just installed a test enveiorment server, including
wbi 6.0.0.3, mq 6.0.2.0
both cfgmgr and broker are on the same server, but every component has a different qmgr - for logical reasons.
However, another QMgr will use more resources. My client within my enterprise says that he wants to save resources, but i believe
apparting the qmgrs is an important standard for maintanance.
What are the pros and conns of different qmgrs for these compononets?
P.S There is no need for HA enviorment...
Thank you in advance, |
|
| Back to top |
|
 |
| premkumar |
| Posted: Tue Jun 12, 2007 3:00 am Post subject: |
|
|
Apprentice
Joined: 24 Feb 2004
Posts: 40
|
Normally in production machine will not have the configuration manager, cos cfg mgr can manage more than one broker....means there can be more than one broker production machine.
Conf Qmg can be started only during the deployment in the production and hence there will be no usege of the memory... You can stop the confi mgr service and its qmgr.... |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Tue Jun 12, 2007 3:11 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| premkumar wrote: |
Conf Qmg can be started only during the deployment in the production and hence there will be no usege of the memory... You can stop the confi mgr service and its qmgr.... |
Possible but not practical. If you have a fairly sized development crew you will keep the config mgr running all the time for obvious reasons...
Once things have calmed down and you are in pure maintenance mode you could shutdown the config mgr when not needed...
The main reason to keep the config mgr apart is maintenance. You can perform maintenance on the config mgr box without impacting the brokers... unless you need to deploy something... 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| dotaneli |
| Posted: Tue Jun 12, 2007 3:37 am Post subject: |
|
|
Voyager
Joined: 19 Oct 2005
Posts: 99
Location: Israel
|
Okay, thanks.
Anyways, this is a TEST enviroment, not a PRODUCTION one.
What is the resource cost of another QMGR and the extra CONFIGMGR? |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Tue Jun 12, 2007 4:01 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Depending on what kind of TEST environment it is, it might need to look EXACTLY like production.
If it's just a unit test environment, then don't bother with another queue manager.
If it's a stress/acceptance test environment, that needs to mirror production, then ... make it mirror production.
_________________
I am *not* the model of the modern major general. |
|
| 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
|
|
|
|
