| Author |
Message
|
| wssuite01 |
 Posted: Thu Apr 24, 2008 9:29 am Post subject: Shared Qmgr for Broker and Configuration Manager |
 |
|
Newbie
Joined: 07 Jan 2005
Posts: 8
|
Hello all
Is it a good practice to share a single qmgr between a broker and configuration manager ?
Are there any potential issues with this approach ?
Awaiting your reply,
Thanks
Sam |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Thu Apr 24, 2008 10:01 am Post subject: Re: Shared Qmgr for Broker and Configuration Manager |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| wssuite01 wrote: |
Hello all
Is it a good practice to share a single qmgr between a broker and configuration manager ?
Are there any potential issues with this approach ?
Awaiting your reply,
Thanks
Sam |
It makes migrating one without the other to a different hardware box a little more complex...
because you will need some extra steps...
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| mqmatt |
| Posted: Thu Apr 24, 2008 10:23 am Post subject: |
|
|
Grand Master
Joined: 04 Aug 2004
Posts: 1213
Location: Hursley, UK
|
It's really up to you. Users I speak to tend to be split 50:50 on this 
There are a couple of technical advantages to sharing queue managers: (a) less MQ configuration, (b) it makes cancel deploy a bit safer.
But a centralised Config Manager allows one CM to multiple brokers, which might make your overall domain administration easier. |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Thu Apr 24, 2008 12:50 pm Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
Take advantage of the flexibility IBM gave you. Opt to keep your Config Manager on a separate Queue Manager on a separate server. The Broker is your runtime environment that can't afford an unscheduled outage. Why add something optional to that server? What happens when the Config Manager goes loopy and you need to reboot the box (its happened more than once). Since my Config Manager is on its own server we are quite alright with bouncing it even in the middle of the day. Not that this is a constant reoccuring problem. But every few months the Config Manager hangs after our nightly Config Manager DB backup script runs (yes we stop the CM first) and the only option is to reboot or kill the bipconfig exe.
I'm not saying you have to do this. Like Matt said there are lots of people out there that run 1 CM for each Broker and they share the same QM.
But a Config Manager is a very light weight application. Its a perfect candidate for being hosted on a VMWare session, either Windows or Linux, so the "cost" of another server is quite low to get this separation.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| rknox |
| Posted: Fri Apr 25, 2008 7:44 am Post subject: |
|
|
Apprentice
Joined: 28 Aug 2007
Posts: 34
|
| I don't mean to hijack this thread, but Peter would you also recommend putting a usernameserver on separate hardware? We are just beginning to consider pub/sub and I'm doing some initial reading on the requirements. |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Fri Apr 25, 2008 8:23 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
My expirience with a User Name Server is too limited to offer practical advice. Hopefully someone else can offer advice here.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Fri Apr 25, 2008 9:06 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Very few people find they have a hard and fast need for the User Name Server.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
|
|
