| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| connect two qmgrs with the same name |
« View previous topic :: View next topic » |
| Author |
Message
|
| flaufer |
 Posted: Thu Mar 10, 2011 2:27 am Post subject: connect two qmgrs with the same name |
 |
|
Acolyte
Joined: 08 Dec 2004
Posts: 59
|
Folks,
I've somewhat... well... found a solution to my problem, however am not sure that I've missed some things. This is on labs only, so not production relevant.. I just want a few messages to flow for a couple of days.
Imagine a three qmgr setup.
QM1(old)
QM1(new)
QM2
QM1(new) will replace QM1(old) in short term. Both Queue Managers have been setup with the same QMGR-Name (QM1).
Two applications communicate bidirectionally. One connects to QM1, the other to QM2. The app has been moved to QM1(new). QM1(old) is still up and running.
I have (that is the reason for my q&d setup) no network connectivity from QM2->QM1(new), thus thought about hopping over QM1(old), which I can connect to.
So messages would go the route QM2->QM1(old)->QM1(new).
Channel between QM1(old) and QM1(new) is working.
On QM1(old):
DEFINE QREMOTE(APPQ) +
XMITQ('CROSSTEST') +
RNAME(APPQ) +
RQMNAME('TEMPQM')
on QM1(new):
DEFINE QL(APPQ)
DEFINE QREMOTE(TEMPQM) RNAME(' ') RQMNAME(' ')
Messages from QM1(new) to QM2 work fine through direct channel.
If I put a message into the APPQ@QM1-old it ends up in APPQ@QM1-new, as desired.
I'm now redirecting the messages from QM2 towards QM1(and) and hope they will also end up in the proper queues (of course, Qremotes defined on QM1(old)).
I'm just wondering if I totally misunderstood this... my understand would be that one should not put two QMs with the same name within a MQ DQM landscape.
Felix |
|
| Back to top |
|
 |
| exerk |
| Posted: Thu Mar 10, 2011 3:01 am Post subject: Re: connect two qmgrs with the same name |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
| flaufer wrote: |
| ...my understand would be that one should not put two QMs with the same name within a MQ DQM landscape... |
Correct, it's really not a good idea and most especially if there is queue manager clustering involved.
I find the following statements contradictory because they imply you have unidirectional connectivity?
| flaufer wrote: |
...I have no network connectivity from QM2->QM1(new)...
...Messages from QM1(new) to QM2 work fine through direct channel... |
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
|
| flaufer |
| Posted: Thu Mar 10, 2011 3:40 am Post subject: Re: connect two qmgrs with the same name |
|
|
Acolyte
Joined: 08 Dec 2004
Posts: 59
|
| exerk wrote: |
| flaufer wrote: |
| ...my understand would be that one should not put two QMs with the same name within a MQ DQM landscape... |
Correct, it's really not a good idea and most especially if there is queue manager clustering involved.
|
No clustering :-) I inititally thought it would never work, but the QMALIAS fixed it... I'm not sure about reply-to stuff would work in this scenario... but I believe I don't need it from the app point of view.
| exerk wrote: |
I find the following statements contradictory because they imply you have unidirectional connectivity?
| flaufer wrote: |
...I have no network connectivity from QM2->QM1(new)...
...Messages from QM1(new) to QM2 work fine through direct channel... |
|
I do. There is a firewall between QM1(*) and QM2 and comms is blocked for QM2->QM1(new). In the final run the firewall will be open, but not yet and I need messages to go to the QM1(new).
Thanks,
Felix |
|
| Back to top |
|
|
| exerk |
| Posted: Thu Mar 10, 2011 3:57 am Post subject: Re: connect two qmgrs with the same name |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
| flaufer wrote: |
| ...I inititally thought it would never work, but the QMALIAS fixed it... I'm not sure about reply-to stuff would work in this scenario... but I believe I don't need it from the app point of view... |
If you need a reply-to path just use another queue manager alias back to QM1(old), i.e. an XMITQ named QM1NEW in QM2 and appropriate channels between QM2 and QM1(old), then bounce from QM1(old) to QM1(new). Just make sure the application can set the reply-to-queue manager, or force it using yet another queue manager alias.
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| 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
|
|
|
|
