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 IBM MQ Support » Sharing Q-Mgrs or isolated Q-Mgrs?

Post new topic  Reply to topic
 Sharing Q-Mgrs or isolated Q-Mgrs? « View previous topic :: View next topic » 
Author Message
kme_1998
PostPosted: Mon Aug 26, 2002 3:14 am    Post subject: Sharing Q-Mgrs or isolated Q-Mgrs? Reply with quote

Novice

Joined: 04 Jun 2001
Posts: 14

From the vast experience out there please speak up. What is generally considered best practice for running Q-mgrs in MVS. Large company with multiple business units. What are peoples opinions regarding simplicity of admin vs. advantage of isolation? Should every unit get their own or all share a couple Q_MGRS. Most of the data exists in shared LPAR environment.

This is a difficult question with many assumptions but would love to hear opinions on both sides.
Back to top
View user's profile Send private message Send e-mail
oz1ccg
PostPosted: Tue Aug 27, 2002 4:01 am    Post subject: Reply with quote

Yatiri

Joined: 10 Feb 2002
Posts: 628
Location: Denmark

Well,

That's a tuff question Anyhow when dealing with MVS, there are no reason for having a QMGR per project/business unit.

There are strong security, high availablity, enought capacity (there are a mousetrap with max. msg length and number channels..) it's less overhead, and there are a limited number of subsystems available.

If you meet performace problems it can be a reason for adding one or more qmgrs.... I haven't faced it yet.

It's the same as with DB2, do you give every business unit their own DB2 subsystem with datasharing ? NO, you don't. It's the same approach with MQSeries one MQ per LPAR for production and evt. one for testing purpose.

The main benefits here is simple administration (small number of MQs to tune), you can give the business units their own pagesets/CF-structures to cover their data. But shared logging etc.

The biggest problem is to expand pageset size, while running (keep always some extra defined in the QMGRs, so you in flight can move/add queues if space problems.

Some of my customers are doing it this way, one production QMGR per LPAR covering all their business units.

OperTune from BMC can add pagesets while running.

What benefit can we get when giving each business unit their own QMGR ? The only one I can see is stopping it without borther the other business units..

Just my $0.02
_________________
Regards, Jørgen
Home of BlockIP2, the last free MQ Security exit ver. 3.00
Cert. on WMQ, WBIMB, SWIFT.
Back to top
View user's profile Send private message Send e-mail Visit poster's website MSN Messenger
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » General IBM MQ Support » Sharing Q-Mgrs or isolated Q-Mgrs?
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.