| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Balancing/HA with QM aliases |
« View previous topic :: View next topic » |
| Author |
Message
|
| eniomarques |
 Posted: Fri Aug 10, 2018 8:31 am Post subject: Balancing/HA with QM aliases |
 |
|
Novice
Joined: 25 May 2015
Posts: 24
Location: Brazil
|
Hello everyone!
I'm trying to find a solution to avoid a possible point of failure. 
Currently, we have two QMs that act as a gateway to a partner, and these two QMs are part of a cluster.
This partner, have several QM aliases that uses the xmitq of only one of our gateway QMs, and the idea would be to have them use both, case something goes wrong with one of our gateways.
Is there any way to make it work? I was thinking about using a namelist (not sure if it would work, have not tested yet), but I believe that even with a namelist, if one of the QMs goes down, the messages will still end up in its xmitq.
Thanks! |
|
| Back to top |
|
 |
| exerk |
| Posted: Fri Aug 10, 2018 9:25 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
1. Put MQ IPT in front of both queue managers, with an internal route defined for each (one route active, one dormant, i.e. shut down);
2. Use the same queue manager alias in both your gateways (this alias will be the symbolic queue manager name you give to your partner - if you want to maintain your current set-up, you will only need an alias in the other gateway);
3. If gateway 'Active' queue manager goes down, de-activate the 'active' IPT route and activate the 'dormant' route.
You may have to amend SSLPEER values if you use SSL pass-through in IPT, and reset channel sequence numbers, but this set-up would give you what you want. Undoubtedly others will be along to offer alternatives.
_________________
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 |
|
|
| eniomarques |
| Posted: Tue Aug 14, 2018 10:37 am Post subject: |
|
|
Novice
Joined: 25 May 2015
Posts: 24
Location: Brazil
|
| exerk wrote: |
1. Put MQ IPT in front of both queue managers, with an internal route defined for each (one route active, one dormant, i.e. shut down);
2. Use the same queue manager alias in both your gateways (this alias will be the symbolic queue manager name you give to your partner - if you want to maintain your current set-up, you will only need an alias in the other gateway);
3. If gateway 'Active' queue manager goes down, de-activate the 'active' IPT route and activate the 'dormant' route.
You may have to amend SSLPEER values if you use SSL pass-through in IPT, and reset channel sequence numbers, but this set-up would give you what you want. Undoubtedly others will be along to offer alternatives. |
Thank you, looks like that's all we need! Not sure if we will be able to implement it though. I'll let you know  |
|
| 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
|
|
|
|
