| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| MQ failover |
« View previous topic :: View next topic » |
| Author |
Message
|
| floring |
 Posted: Tue Jul 20, 2004 10:45 am Post subject: MQ failover |
 |
|
Newbie
Joined: 20 Jul 2004
Posts: 4
Location: Bucharest, Romania
|
Hi gurus,
We have two servers, each one with a queue manager on it; second one is the backup of the first one (same configuration: queues etc);
The clients are connecting using MQ java client.
My problem is, if i want to switch over from the first queue manager to the second one, i must tell the client to change the name of the cluster in ther MQ client config (queue manager name must be changed in the bindings file).
Is there any posibility not to do this ?
Something like a "queue manager alias". The clients would connect to this alias. In case first queue manager would be unavailable, the alias should point to the second one.
Is there any posibility to define this kind of alias? |
|
| Back to top |
|
 |
| kingsley |
| Posted: Tue Jul 20, 2004 10:57 am Post subject: |
|
|
Disciple
Joined: 30 Sep 2001
Posts: 175
Location: Hursley
|
If you are using the Unix or Windows cluster, keep the Queuemanager name same on both the box (which is mandatory). keep the svrconn and other objects identical.
Build the svrconn with Virtual IP of the cluster (not the box name)
When the fail over occurs, the client will automically use the second qmgr since ip will same and failover is seemless.
No more problems. I have implemented in Unix, Windows. They are working simply fine. |
|
| Back to top |
|
|
| floring |
| Posted: Wed Jul 21, 2004 1:21 am Post subject: |
|
|
Newbie
Joined: 20 Jul 2004
Posts: 4
Location: Bucharest, Romania
|
In fact, both systems are HACMP clusters.
The problem is that every cluster is in different locations and I want a transparent switvh-over (from a client point of view) betwen these two locations.
In MQ Intercommunication book, page 26, I found something about "queue manager alias", but there are only a few lines and I do not understand if this "queue manager alias" could help me.
Also, is it possible to use a "MQ cluster" to solve that problem? In documentation they said a MQ cluster helps to assure availability, but I do not understand how.
If anybody can help me, I'd appreciate a lot.
Florin |
|
| Back to top |
|
|
| zpat |
| Posted: Wed Jul 21, 2004 1:54 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
The easier way is to have the Java client read a list of potential queue manager names from it's configuration file.
It should select one (either in order or at random) to connect to. If the connection is unsuccessful or later fails, it should use the other one (or choose one at random again).
That gives client connection failover and (if desired) load-balancing.
You can't "cluster connect" from a MQ client to achieve this. |
|
| Back to top |
|
|
| floring |
| Posted: Thu Jul 22, 2004 4:23 am Post subject: |
|
|
Newbie
Joined: 20 Jul 2004
Posts: 4
Location: Bucharest, Romania
|
Thanks, Zpat,
I think this is the best solution.
Florin |
|
| 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
|
|
|
|
