| Author |
Message
|
| NickB |
 Posted: Fri Dec 14, 2001 4:37 am Post subject: |
 |
|
Centurion
Joined: 20 May 2001
Posts: 107
Location: Zurich Financial Services
|
I understand how to set up multi-hopping where just one intermediate qmgr is involved (i.e. define a qremote on QM1 which points to qlocal on QM3 using an xmitq named QM2 which is the intermediate qmgr).
However if I have
QM1 -> QM2 -> QM3 -> QM4
how do I define my qremote on QM1 to point to a qlocal on QM4? |
|
| Back to top |
|
 |
| EddieA |
| Posted: Fri Dec 14, 2001 10:15 am Post subject: |
|
|
Jedi
Joined: 28 Jun 2001
Posts: 2453
Location: Los Angeles
|
OK.
I'll assume that you've got a Remote Queue definition that points to a Queue on QM4.
On QM1, the remote queue definition points to the XmitQ to take you to QM2. The same as your QM1 -> QM3 case. At this point previously you would have relied on an XmitQ called QM3 to get you to your destination. Obviously, now you can't do that as the message says it's for QM4.
BTW If you don't have an XmitQ called QM3, then the following technique would be needed to get you to QM3 in your QM1 -> QM3 case.
So, on QM2, you set up a Queue Manager alias. This is a Remote Queue definition that doesn't contain a queue name.
DEFINE QR(QM4) RQMNAME(QM3) [XMITQ(xmitq to qm3)]
The XMITQ specification is optional if you have an XmitQ called QM3. Otherwise it gives the XmitQ that will get you to QM3.
This will route the message on to QM3, where you could either have an XmitQ called QM4 or you would need another alias to get you to QM4.
Hope that helps.
Cheers,
_________________
Eddie Atherton
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Message Broker V7.0 |
|
| Back to top |
|
|
| NickB |
| Posted: Wed Dec 19, 2001 3:52 am Post subject: |
|
|
Centurion
Joined: 20 May 2001
Posts: 107
Location: Zurich Financial Services
|
Eddie
Thanks for the suggestion which sort of confirmed how I thought it would work.
However it still doesn't work and in fact the message goes to the DLQ of QM3 with a reason code of 2085 as the destination qmgr in the MQMD is "QM3"! Myself and a colleague have independantly set up multi qmg rconfigurations using a combination of NT and AIX and MQ 5.1 and MQ 5.2 and we both get the same result.
Any other suggestions would be appreciated. |
|
| Back to top |
|
|
| NickB |
| Posted: Wed Dec 19, 2001 5:53 am Post subject: |
|
|
Centurion
Joined: 20 May 2001
Posts: 107
Location: Zurich Financial Services
|
OK the problem has now been solved. In fact the solution suggested earlier will not work as the "wrong" remote qmgr name was specified in the qmgr alias definition on the 2nd qmgr. The qmgr alias on qm2 should read
DEF QR(QM4) RQMNAME(QM4) XMITQ(QM3)
This then works perfectly.
|
|
| Back to top |
|
|
| EddieA |
| Posted: Wed Dec 19, 2001 9:49 am Post subject: |
|
|
Jedi
Joined: 28 Jun 2001
Posts: 2453
Location: Los Angeles
|
Nick,
Thanks for correcting my post, which was taken from my memory, not a working system.
The only thing it proved, is that my 'ancient' memeory isn't what it used to be.
Cheers,
_________________
Eddie Atherton
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Message Broker V7.0 |
|
| Back to top |
|
|
|
|
