| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Using Multiple Queue Manager |
« View previous topic :: View next topic » |
| Author |
Message
|
| ajayvizag |
 Posted: Mon Apr 13, 2009 4:28 am Post subject: Using Multiple Queue Manager |
 |
|
Apprentice
Joined: 20 Feb 2009
Posts: 31
|
How do we decide wether to use a single queue manager and make evry application to connect to the same queue manager as clients or to create more than one queue manager and provede Message channels between them.
Please let me know what all are the criteria.
Last edited by ajayvizag on Mon Apr 13, 2009 4:45 am; edited 1 time in total |
|
| Back to top |
|
 |
| mqjeff |
| Posted: Mon Apr 13, 2009 4:45 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
Well, you can either hire a software architect who has middleware expertise particularly with WebSphere MQ Design, or you can get training on how to be a software architect for WebSphere MQ Design.
You can hire people using the "Job Posting" section of this forum.
You can't get training using any section of this forum. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Mon Apr 13, 2009 5:12 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
Sounds like a job interview question.
How many of something you have is usually determined by how much risk there is in having just one. The offset is how much more effort and other costs there will be having more than one.
How many servers does your organization have? How did they decide on that number?
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| Sam Uppu |
| Posted: Mon Apr 13, 2009 7:25 am Post subject: |
|
|
Yatiri
Joined: 11 Nov 2008
Posts: 610
|
According to best practices:
For architectural as well as performance reasons, it is usually better to create one queue manager with 100 queues as opposed to 100 queue managers with one queue apiece. Where it makes sense, try to limit the number of queue managers in an MQ environment. A single queue manager per server can usually fulfill the needs of all of the queues and applications on that server. While the queue manager can fulfill multiple roles, the segregation of responsibility should occur at the queue level, preferably with a function identifier in the queue name.
Thanks. |
|
| 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
|
|
|
|
