| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Queue Managers And Channel Types ! |
« View previous topic :: View next topic » |
| Author |
Message
|
| objectthinker06 |
 Posted: Wed Aug 16, 2006 12:14 pm Post subject: Queue Managers And Channel Types ! |
 |
|
Novice
Joined: 15 Aug 2006
Posts: 15
|
Pls help me on the following two questions, I have limited experience in MQ:
1) Lets say for example there is a need to have 60 different queue's each for a type of business entity, in this context would it be a good idea to have multiple queue managers or one ? What are the heuristics on when to go for one queue manager or n queue managers from your experience ?
2) What are the pros/cons of using the below mentioned channel types ? or when to use what ?
--Sender-Receiver Channel
--Requestor-Sender Channel
--Requestor-Server Channel
Thanks |
|
| Back to top |
|
 |
| Vitor |
| Posted: Thu Aug 17, 2006 12:07 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
1) It's always better to have one queue manager hosting 10 queues than 10 queue managers hosting one each. IMHO you should in general separate queue managers when there's a network or geographic connection issue or you have a pressing need to segregate traffic - between dev & prod is the classic example of this. I think if all you have are 60 queues I'd go with 1 queue manager and a solid naming convention. The break even point is where the problems of maintenance & administration outweigh the resource cost of new logging and CPU.
(The exception which proves this is load balancing and high availability scenarios!) 
There's a couple of Redbooks & support packs that talk about this. The platform specific books will give you details of resources required for a new queue manager. Think also about the application design - you really want 60 possible connections in your programme??
2) There's an entire manual devoted to those questions. It depends on your achitecture, mostly on which side initiates the converstion. Try the Intercommunication manual, which talks though various scenarios.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| tleichen |
| Posted: Thu Aug 17, 2006 7:31 am Post subject: |
|
|
Yatiri
Joined: 11 Apr 2005
Posts: 663
Location: Center of the USA
|
This has often been a kind of "pet peeve" subject for me. I have seen many installations use way too many queue managers for the job at hand, simply because they were not willing to read the manuals to find out how to keep different applications out of each other's queues (via access security, etc.).
Keep in mind, with two queue managers you have to allocate log space for each, etc. Why double the resources used for no good reason? 
_________________
IBM Certified MQSeries Specialist
IBM Certified MQSeries Developer |
|
| 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
|
|
|
|
