| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| What are the pros and cons of using multiple queue managers? |
« View previous topic :: View next topic » |
| Author |
Message
|
| rgross999 |
 Posted: Fri Feb 13, 2004 12:55 pm Post subject: What are the pros and cons of using multiple queue managers? |
 |
|
Newbie
Joined: 15 Jan 2004
Posts: 8
|
What are the pros and cons of using multiple queue managers on the same Windows server?
My company sells insurance in a handful of states. We want to group messages by type of insurance and state. To clarify, we will have one type of message for Minnesota homeowners policies, one type of message for Minnesota contact admin, one type of message for Wisconsin homeowners policies, one message for Wisconsin contact admin, etc.
I do not know whether it is better to have separate queue managers for each state, with a homeowners and auto queue in each queue manager, or if it is better to have a single queue manager that contains a Minnesota homeowners queue, Minnesota auto queue, Wisconsin homeowners queue, Wisconsin auto, etc?
Which way is better, more queue managers or fewer queue managers?
Thanks.
RG |
|
| Back to top |
|
 |
| mq_developer |
| Posted: Fri Feb 13, 2004 1:47 pm Post subject: |
|
|
Voyager
Joined: 18 Feb 2002
Posts: 82
|
Is memory a critical factor on your windows servers ? That would decide it all , as you create new queue managers you are going to start all the queue manager process again ...
Design wise , i feel , isolation of the data can be better managed and handled at queue level and with proper queue naming convention ... like MN.AUTO.INSURANCE ... AZ.HOME.INSURANCE .... If you are using any built in programs or MQSI to perform the routing of message , they can rely on this naming convention / rule ...
if you have a queue manager on a state by state basis servers are going to explode with all AMQ process .. in the same lines you dont want to create 1000s of queues on a single queue manager .. so best design would be is to mix and match .... and i would recommend create queue managers based on the business function areas and create queues for each state ... So AUTO would be auto insurance queue manager having queues for each state ....
Ram |
|
| Back to top |
|
|
| kman |
| Posted: Mon Feb 16, 2004 11:55 pm Post subject: |
|
|
Partisan
Joined: 21 Jan 2003
Posts: 309
Location: Kuala Lumpur, Malaysia
|
| Quote: |
| .... and i would recommend create queue managers based on the business function areas and create queues for each state ... So AUTO would be auto insurance queue manager having queues for each state .... |
That's a good observation. That is akin to having a queue manager for each application system, like AUTO system, HOME system, etc.,
If you take queue managers for eaxh states.. that a whole lot of queue managers runnign around.. completes with all the processes and default systems processes..
But like someone used to say in this forum ( I can't remember off hand) - it depends.  |
|
| 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
|
|
|
|
