| Author |
Message
|
| dasnani |
 Posted: Tue Jan 23, 2007 12:47 pm Post subject: Migrating applications from one cluster to another |
 |
|
Newbie
Joined: 15 Jan 2007
Posts: 7
|
Hi,
Has anyone ever cut-over an application from one EAI cluster to another? What are the general steps involved and any issues that we should be careful about?
Both clusters have two EAI servers running MQ v6 and Message Broker v 6 on Unix systems.
Thanks, Dheeraj. |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Tue Jan 23, 2007 1:05 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
The application shouldn't know that there is or is not a cluster, if it is a well-behaved MQ application.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| dasnani |
| Posted: Tue Jan 23, 2007 3:03 pm Post subject: |
|
|
Newbie
Joined: 15 Jan 2007
Posts: 7
|
Hi,
I agree... but what I was expecting was more basic steps such as below (this is what I envision).
1. Set up queue definitions for application A on new cluster. say NEW.APPA
2. Connect application A to the new cluster. Note that at this point application A will be connected to both clusters but will only communicate to the old cluster.
3. Change alias of input queue on application A to point to new cluster. i.e change OLD.APPA to NEW.APPA
4. Remove queue deinitions from old cluster.
I do not have much experience with MQ clusters so please elaborate on the steps that would be involved or point me to any resource where I can find this information.
Thanks in advance. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Tue Jan 23, 2007 3:28 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Applications don't connect to clusters. They connect to queue managers.
An application shouldn't connect to more than one queue manager at a time, except in certain specific cases (and this isn't one).
If you know so little about MQ and clusters, why are you the one trying to plan this migration?
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| dasnani |
| Posted: Wed Jan 24, 2007 5:49 am Post subject: |
|
|
Newbie
Joined: 15 Jan 2007
Posts: 7
|
| jefflowrey - thanks for your insight into the matter. If you have anything to say about the actual steps involved, I would appreciate it. |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed Jan 24, 2007 5:53 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
If the queue manager is being migrated from one cluster to another, there should be no application impact. The only impact is if the queue manager is moving (new IP address and so forth).
As to moving a queue manager from one cluster to another, this is described in the Clustering manual. My tip - be sure to plan the sequence of events and follow the plan. Most problems in clustering come from poor preparation (decomissioning a queue manager without first properly removing it from the cluster for instance).
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Wed Jan 24, 2007 5:58 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
If an application is being migrated from one queue manager to another, then you need to make sure that
1) All of the QLOCALs that the application gets from (and hopefully there's only one) are defined as QLOCALs on the new queue manager
2) All the queues that the application PUTS to are findable in their correct location from the new queue manager.
With clustering, #2 is usually handled automatically if the cluster is correct.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
|
|
