| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
| Queue manager alias |
« View previous topic :: View next topic » |
| Author |
Message
|
| sumit |
 Posted: Fri Aug 08, 2008 12:21 pm Post subject: |
 |
|
Partisan
Joined: 19 Jan 2006
Posts: 398
|
rdx,
| Quote: |
| If the local queue manager is REALQM, it puts the messages to the queue THISQ, which is a local queue. If the local queue manager is not called REALQM, it routes the message to a transmission queue called REALQM. The queue manager changes the transmission header to say REALQM instead of YOURQM. |
If you read the above quote, it represents the working of a normal QR definition. An application while connecting to a queue manager mentions the queue name where it want to put a message. If it finds the queue as local, it will put message there itself.
And, if it finds a remote queue with desired name, it directs the message to remote queue which will send it to xmitq for transmission.
In your case, when you connect to REALQM, the application is able to find THISQ as local and hence putting the message there itself. Whereas, when you connect to YOURQM, the application finds THISQ as remoteq, and thus routes the message to xmitq.
_________________
Regards
Sumit |
|
| Back to top |
|
 |
| sami.stormrage |
| Posted: Sat Aug 09, 2008 1:21 pm Post subject: |
|
|
Disciple
Joined: 25 Jun 2008
Posts: 186
Location: Bangalore/Singapore
|
| Quote: |
This shows that the real queue manager to be used, when an application puts messages to queue manager YOURQM, is REALQM. If the local queue manager is REALQM, it puts the messages to the queue THISQ, which is a local queue. If the local queue manager is not called REALQM, it routes the message to a transmission queue called REALQM. The queue manager changes the transmission header to say REALQM instead of YOURQM. |
Thanks buddy for refreshing my QmgrAlias knowledge..
Actually speaking there can be two scenarios.. The one you've mentioned is also used.. ( The infrastructure project which I worked had this kind of setup for replying back messages from provider to sender directly, without involving any load balancing.. )
And the other.. is below..
http://www.mrmq.dk/index.htm?cluster_qmc_1.htm
but dont think it can be called a clusterQmgrAlias  (but wonder if it is a mq V8 concept..   )
_________________
*forgetting everything  * |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Sat Aug 09, 2008 1:43 pm Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9482
Location: US: west coast, almost. Otherwise, enroute.
|
| Quote: |
| In the mqopen call as mentioned in the manual i am using THISQ(localQM2) and queue manager QM1(YOURQM). |
This is a choice. The MQOPEN call does not require that you code qname and qmgr name. The manual gives you all kinds of possible ways to use the API calls. Just because you can do something doesn't mean that you should.
What business reason led you to code the MQOPEN (or Java equivalent) with both qname and qmgrname? What did you want to accomplish with this technique?
_________________
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 |
|
|
|
|
|
|
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
|
|
|
|
