| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| MQ point-to-point architecture |
« View previous topic :: View next topic » |
| Author |
Message
|
| zaepster |
 Posted: Tue Jul 26, 2022 2:49 am Post subject: MQ point-to-point architecture |
 |
|
Newbie
Joined: 26 Jul 2022
Posts: 1
|
Hi guys,
sorry for the silly question but I'm new to MQ.
I would like to setup a simple architecture where App1 writes on a queue a message and App2 reads the message from that queue.
I don't get why in the documentation the basic arcihtecture shows 2 queue managers linked by a channel. Each QMgr is managing a different queue and the messages are sent from queue1 to queue2 through channel, after that the App2 is reading from queue2.
Can't the App2 read the message directly from the same queue1 where the App1 is writing? Why I need 2 queue managers and 2 queues ? |
|
| Back to top |
|
 |
| bruce2359 |
| Posted: Tue Jul 26, 2022 5:16 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
While it is a bit old, this primer will provide you the fundamental concepts in MQ
https://www.redbooks.ibm.com/redpapers/pdfs/redp0021.pdf
One possible implementation configuration is where producer apps and consumer apps can use (MQCONNect) a single queue manager. If producer app and consumer app are not on the same platform, then distributed queueing is the solution - where messages are sent across an MQ channel from producing app platform to consuming app platform.
_________________
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 |
|
|
| gbaddeley |
| Posted: Tue Jul 26, 2022 2:37 pm Post subject: |
|
|
Jedi Knight
Joined: 25 Mar 2003
Posts: 2538
Location: Melbourne, Australia
|
| bruce2359 wrote: |
While it is a bit old, this primer will provide you the fundamental concepts in MQ
https://www.redbooks.ibm.com/redpapers/pdfs/redp0021.pdf
One possible implementation configuration is where producer apps and consumer apps can use (MQCONNect) a single queue manager. If producer app and consumer app are not on the same platform, then distributed queueing is the solution - where messages are sent across an MQ channel from producing app platform to consuming app platform. |
If the apps are not on the same platform, MQ Client is also a solution. Depending on volume, response time, quality of service requirements, app platform type, it is cheaper to have a single queue manager rather than multiple queue managers. MQ Client has no license cost, whereas MQ Server (queue manager) license cost is quite significant.
MQ Clustering is similar to distributed queueing, and has a number of advantages depending on complexity and messaging requirements of solutions.
_________________
Glenn |
|
| 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
|
|
|
|
