| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Redirecting messages to another Queue manager |
« View previous topic :: View next topic » |
| Author |
Message
|
| Rangarajan |
 Posted: Tue Sep 17, 2002 10:24 pm Post subject: Redirecting messages to another Queue manager |
 |
|
Novice
Joined: 01 Aug 2002
Posts: 22
|
I have two Queue Managers installed in a single box. Both these Queue managers point to the same destination Queue Manager. I have an application which uses one of the Queue Managers to send message to the destination. If this sending queue manager is down, can we configure the queue manager, such that the messages are re-directed to the second queue manager in the same machine.
In this way my application will be able to send messages always to the destination. Can some one explain me the process in detail, if this re- direction is possible. |
|
| Back to top |
|
 |
| oz1ccg |
| Posted: Tue Sep 17, 2002 11:46 pm Post subject: |
|
|
Yatiri
Joined: 10 Feb 2002
Posts: 628
Location: Denmark
|
What you could do is similar to a solution presented earlier..... QMX2 in this senario uses this model.
http://d1o112.dk.telia.net/~u149101068/cluster_qmb_3.htm
What you could do was creating two sender channels on the destiantion qmgr, using the same XMITQ... this gives you the ablity to failover.... but why.. This approach will require some automation tools to swing back when the "dead" one comes back...
What your "client" application could do is place the client-QMGRID as part of the ReplyToQueue.. In this way the destiantion QMGR would know where to send it ... And when the client program changes to the other CLient-qmgr in case of a failure, it automatily changes the ReplyToQueue to the new one there... Many of my customers are using this technique to archive availability.
Just my $0.02 
_________________
Regards, Jørgen
Home of BlockIP2, the last free MQ Security exit ver. 3.00
Cert. on WMQ, WBIMB, SWIFT. |
|
| Back to top |
|
|
| Rangarajan |
| Posted: Wed Sep 18, 2002 1:07 am Post subject: |
|
|
Novice
Joined: 01 Aug 2002
Posts: 22
|
Jorgen,
Please correct me if my understanding is wrong.
Do you mean to say that the client application has to control the whole operation. It has to find whether the original Queue manager is down. In that case it has to put the message in the backup queue manager. Then set the replytoqmgr and replytoqueue with the values of this backup queuemanager name and queue name.
Can u please explain more about this. |
|
| Back to top |
|
|
| oz1ccg |
| Posted: Thu Sep 19, 2002 3:13 am Post subject: |
|
|
Yatiri
Joined: 10 Feb 2002
Posts: 628
Location: Denmark
|
nononono....
What I meant was that the CLIENT have to know which QMGR it's connected to (tiny MQINC call), and use this information to tell the SERVER application that.
I have to make clear that this solution covers a transactional model, say client request an reply from the server.
I'm working on a interesting solution... just have to test it...
Just my $.25
_________________
Regards, Jørgen
Home of BlockIP2, the last free MQ Security exit ver. 3.00
Cert. on WMQ, WBIMB, SWIFT. |
|
| 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
|
|
|
|
