ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » General Discussion » best practices on Queue Managers

Post new topic  Reply to topic
 best practices on Queue Managers « View previous topic :: View next topic » 
Author Message
biyer
PostPosted: Sun Jul 16, 2006 7:51 pm    Post subject: best practices on Queue Managers Reply with quote

Newbie

Joined: 16 Jul 2006
Posts: 4

Hi,

I am checking if there are any best practices that people in this forum are aware of when managing queue managers.

In our environment, we have a problem where we have a single queue manager installed across multiple countries. We are facing a problem now, when it comes to installing patches...etc that we need to take approvals from all countries before stopping and starting the queue manager and its services. I feel that this kind of component sharing is not something that is good from an availability and recovery perspective.

At the same time, I also need to know what are the pro(s) and con(s) of having a single queue manger across all countries(9) in total from perspective of availability, performance and importantly security.

thank you.

Balaji
Back to top
View user's profile Send private message
zpat
PostPosted: Sun Jul 16, 2006 10:32 pm    Post subject: Reply with quote

Jedi Council

Joined: 19 May 2001
Posts: 5866
Location: UK

Use a hardware cluster (MSCS for Windows, HACMP for AIX etc) to host the queue manager.
Back to top
View user's profile Send private message
biyer
PostPosted: Sun Jul 16, 2006 11:27 pm    Post subject: Reply with quote

Newbie

Joined: 16 Jul 2006
Posts: 4

Thanks !

Is that the only option ? This will mean, I'll have to ask our mgmt to fork out extra $ for another set of H/W and the clustering solution.

Any other best practices under management of queue managers of reason why not have more than 1 Queue manager
Back to top
View user's profile Send private message
Vitor
PostPosted: Sun Jul 16, 2006 11:56 pm    Post subject: Reply with quote

Grand High Poobah

Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA

biyer wrote:
why not have more than 1 Queue manager


Because MQ Clustering is not a substitute for hardware clustering (see the apparently endless discussions on this topic in the forum). It's a load balancing solution that can also aid the administration of multiple queue managers.
_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
zpat
PostPosted: Mon Jul 17, 2006 1:01 am    Post subject: Reply with quote

Jedi Council

Joined: 19 May 2001
Posts: 5866
Location: UK

So you fork out for more queue managers instead then... up to you.

I would personally suggest that having at least one hardware clustered queue manager per (large) country or region makes sense.

You might want to host several queue managers on the same platform for different uses (eg levels of testing) and of course have separate test and production hardware installations.

Virtual servers may provide a cheaper option for hardware but you still pay the same license for MQ.
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » General Discussion » best practices on Queue Managers
Jump to:  



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
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.