| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
| Moving a queue manager to a DR site |
« View previous topic :: View next topic » |
| Author |
Message
|
| bruce2359 |
 Posted: Wed Aug 04, 2010 2:46 pm Post subject: |
 |
|
Poobah
Joined: 05 Jan 2008
Posts: 9475
Location: US: west coast, almost. Otherwise, enroute.
|
The usual, and best-practice, method is for the application to MQOPEN a queue, AND specify only the queuename - NOT the qmgr name - in the MQOD (Object Descriptor).
_________________
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: Wed Aug 04, 2010 3:34 pm Post subject: |
|
|
Jedi Knight
Joined: 25 Mar 2003
Posts: 2538
Location: Melbourne, Australia
|
| bruce2359 wrote: |
| The usual, and best-practice, method is for the application to MQOPEN a queue, AND specify only the queuename - NOT the qmgr name - in the MQOD (Object Descriptor). |
...unless the app is putting reply messages that need to be delivered to a specific remote queue manager, because there is no qremote, qalias or unique clustered queue for the replies.
_________________
Glenn |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Wed Aug 04, 2010 5:08 pm Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9475
Location: US: west coast, almost. Otherwise, enroute.
|
Yep, exactly. The replying application is the special-case where the name of the reply-to-queue and reply-to-qmgr are not known (in advance) by the replying app. These fields come from the inbound request message.
[edit]
The usual, and best-practice, method for the requesting application is for the application at MQOPEN to specify only the queuename - NOT the qmgr name - in the MQOD (Object Descriptor).
_________________
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: Thu Aug 05, 2010 4:39 pm Post subject: |
|
|
Jedi Knight
Joined: 25 Mar 2003
Posts: 2538
Location: Melbourne, Australia
|
| bruce2359 wrote: |
| The usual, and best-practice, method for the requesting application is for the application at MQOPEN to specify only the queuename - NOT the qmgr name - in the MQOD (Object Descriptor). |
Yes, because the app has already connected to a specific qmgr name, or the default (blank) qmgr name. 
_________________
Glenn |
|
| Back to top |
|
|
| mvic |
| Posted: Thu Aug 05, 2010 5:02 pm Post subject: |
|
|
Jedi
Joined: 09 Mar 2004
Posts: 2080
|
| gbaddeley wrote: |
| bruce2359 wrote: |
| The usual, and best-practice, method for the requesting application is for the application at MQOPEN to specify only the queuename - NOT the qmgr name - in the MQOD (Object Descriptor). |
Yes, because the app has already connected to a specific qmgr name, or the default (blank) qmgr name. |
A subtle point, but (possibly?) worth making, because the above is not precise in terminology.
Once you are connected to a qmgr, a blank qmgr name in the MQOD does not give you the "default queue manager", it only gives you a slightly different initial state as you enter into the name resolution table (in the APG). |
|
| 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
|
|
|
|
