| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Creating more then 1 Qmgr |
« View previous topic :: View next topic » |
| Author |
Message
|
| jrjoe |
 Posted: Mon Jul 12, 2004 7:54 am Post subject: Creating more then 1 Qmgr |
 |
|
Acolyte
Joined: 20 Jan 2003
Posts: 60
|
I was wondering what the best practice for creating Qmgrs is.
I have 5 groups of applications on an AIX box that will all be using MQ.
I was going to create 1 Qmgr with the Prefix directory separate from the applications.
Would it be better to have a separate Qmgr for each application group?
Thanks in advance
Joe |
|
| Back to top |
|
 |
| oz1ccg |
| Posted: Mon Jul 12, 2004 10:52 am Post subject: |
|
|
Yatiri
Joined: 10 Feb 2002
Posts: 628
Location: Denmark
|
Hi Joe,
Personally I would prefer one qmgr per box. I don't care about the number of applications sharing the queue manager, as long as the queue manager is able to handle the message traffic. I don't like spending the overhead running multiple qmgrs. There might be some exceptions to this in special cases..... 
You can limit the access to all objects, so one application can't reach another applications data (if applications are running under seperate userids).
I have 1+ qmgrs on some boxes like: one for internal and one for external communication due to security concerns. The same with test vs. production in some cases eg. z/OS. Another special purpose is controlling a SHARED queue environment, where I've created a backup qmgr just to handle backup the shared queues, so the the logs of the normal qmgrs are not disturbed with with the backup job.
Typicly you place the queue manager path under something like /var/mqm/.....
Just my thoughts 
_________________
Regards, Jørgen
Home of BlockIP2, the last free MQ Security exit ver. 3.00
Cert. on WMQ, WBIMB, SWIFT. |
|
| Back to top |
|
|
| SAFraser |
| Posted: Tue Jul 13, 2004 9:08 am Post subject: |
|
|
Shaman
Joined: 22 Oct 2003
Posts: 742
Location: Austin, Texas, USA
|
I agree very much with Jorgen.
In addition to setting application-specific security on queues for separation of the environments, you can easily create application-specific channels (if they use channels). That way, if one of the application groups needs to have their channel traffic stopped for some reason, you can do so without impacting the other applications.
You can create a queue naming scheme that identifies which app group the queue is intended to service. If you use a prefix to identify the app group, they will all display together (alphabetically). For example:
APP1.REQS.CREATED
APP1.REQS.WORKED
APP2.ORDERS.PENDING
APP2.ORDERS.CLOSED
These same types of ideas can be used when naming channels, too.
Good luck,
Shirley |
|
| Back to top |
|
|
| jrjoe |
| Posted: Thu Jul 15, 2004 11:54 am Post subject: |
|
|
Acolyte
Joined: 20 Jan 2003
Posts: 60
|
| I would like to thank you both for the info. |
|
| 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
|
|
|
|
