| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| single queue/multiple queue ? |
« View previous topic :: View next topic » |
| Author |
Message
|
| grasupt |
 Posted: Wed Jan 09, 2002 7:53 am Post subject: |
 |
|
Newbie
Joined: 06 Jan 2002
Posts: 2
|
Is it best to base the number of in/out queues on logical units of work within the communicating applications , or solely based on the transactions that are fired.
ASP->CICS
For a general example, would it be best have a queue for each CICS transaction that is launched to retrieve a person's name/address and demographics (which is 3 cics transactions) or have one queue for the the 3 calls to flow?
Thanx |
|
| Back to top |
|
 |
| PeterPotkay |
| Posted: Wed Jan 09, 2002 8:51 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
If the three different transactions need to TRIGGER 3 different CICS proccesses, then you will need 3 different queues, since a queue can only trigger 1 process.
If the 3 different front end requests are all going to be handled by 1 CICS process, then its tomaaayyyto vs. tomaaaahhto. Some people like to really seperate everything, but technically 1 queue will suffice for the requests, and if the frontend apps are getting their replies by Corrl-ID, then 1 reply queue will also work.
Another spin on this is that the frontends can have 3 different ALIAS request queues that all resolve to the same CICS request queue. This way each frontend thinks they're special with their own queue, but we make the CICS side simple with only 1 queue.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| 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
|
|
|
|
