| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Routing into Cluster |
« View previous topic :: View next topic » |
| Author |
Message
|
| saurabh25281 |
 Posted: Mon Jul 01, 2019 12:03 pm Post subject: Routing into Cluster |
 |
|
Centurion
Joined: 05 Nov 2006
Posts: 108
Location: Bangalore
|
Hi All
1. Can we deliver message from a non-clustered Qmgr to a Cluster queue using multiple Gateway Qmgr such that if one of the Gateway Qmgr is down, the messages are routed to the destination via another Gateway Qmgr. The setup should enable automatic switch to alternate Gateway Qmgr.
2. The Connection Name parameter in a Sender channel allows comma seperated values of multiple destinations and is probably used for multi-instance setup. Can this attribute be used to automatically redirect messages (in a non-mulit-instance setup) to an alternative IP(port), if the initial conname is not available, without performing any manual changes to the Remote Queue Definition at the sender side? The destination is a Cluster Queue.
The examples I see across are all using a Single Gateway Qmgr (single point of failure) which would require manual intervention to restore message route.
Regards
Saurabh |
|
| Back to top |
|
 |
| Vitor |
| Posted: Mon Jul 01, 2019 12:13 pm Post subject: Re: Routing into Cluster |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| saurabh25281 wrote: |
| 1. Can we deliver message from a non-clustered Qmgr to a Cluster queue using multiple Gateway Qmgr such that if one of the Gateway Qmgr is down, the messages are routed to the destination via another Gateway Qmgr. The setup should enable automatic switch to alternate Gateway Qmgr. |
Yes.
| saurabh25281 wrote: |
| 2. The Connection Name parameter in a Sender channel allows comma seperated values of multiple destinations and is probably used for multi-instance setup. Can this attribute be used to automatically redirect messages (in a non-mulit-instance setup) to an alternative IP(port), if the initial conname is not available, without performing any manual changes to the Remote Queue Definition at the sender side? The destination is a Cluster Queue. |
Yes, but the destination of a Sender channel is not any kind of queue - it's a Receiver channel.
The need to make manual changes to a QREMOTE is entirely dependent on how you've defined it and your topology. Specifically how you're using name resolution.
| saurabh25281 wrote: |
| The examples I see across are all using a Single Gateway Qmgr (single point of failure) which would require manual intervention to restore message route. |
Unless the Gateway queue manager is Highly Available.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| saurabh25281 |
| Posted: Wed Jul 03, 2019 3:34 am Post subject: |
|
|
Centurion
Joined: 05 Nov 2006
Posts: 108
Location: Bangalore
|
| Thanks for the response Vitor. We were able to configure our specific requirement. |
|
| 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
|
|
|
|
