| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| clustering vs shared queue |
« View previous topic :: View next topic » |
| Author |
Message
|
| lai2809 |
 Posted: Sun Jun 10, 2007 8:49 pm Post subject: clustering vs shared queue |
 |
|
Newbie
Joined: 10 Jun 2007
Posts: 2
|
Hello,
I have the following senarios:
-2 identical applications, APP1 and APP2 running on different LPAR. APP1
is a primary. APP2 does nothing unless APP1 is down.
-each LPAR has its own qmgr, QM1 and QM2 which hosts Q1 and Q2 respectively.
-APP1 retrieves msgs from Q1. APP2 retrieve msgs from Q2.
-a qmgr GATEWAY acts as a relay qmgr to QM1 or QM2. GATEWAY is primarily pointing to QM1.
-if QM1 is down, GATEWAY to QM1 will be manually altered to point to QM2.
Should i use clustering or shared queue? i'm leaning toward shared queue. what do you think? need your expert advice please.
Thanks. |
|
| Back to top |
|
 |
| Vitor |
| Posted: Sun Jun 10, 2007 11:53 pm Post subject: Re: clustering vs shared queue |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| lai2809 wrote: |
Should i use clustering or shared queue? i'm leaning toward shared queue. what do you think? need your expert advice please.
|
What is your motivation for changing? Is it simply to improve failover or are you trying to load balance? How often does the APP1 / QM1 side fail, and if it's often have you considered root cause analysis to prevent it? On what platform is the gateway hosted?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| lai2809 |
| Posted: Mon Jun 11, 2007 7:08 pm Post subject: |
|
|
Newbie
Joined: 10 Jun 2007
Posts: 2
|
hi,
thanks for the response. here are my answers to the questions and additional info
I'm not worry about load balancing
App1/Qm1 does not fail. i stop the application app1 when i need to migrate the application code. During the code migration, app2/qm2 will be initiated which requires the Gateway to point to qm2 to avoid outages.
Gateway is running on sun solaris.
The motivation for changing is to avoid a manual process from Gateway qmgr to App2/Qm2.
thanks. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Mon Jun 11, 2007 8:15 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| lai2809 wrote: |
hi,
thanks for the response. here are my answers to the questions and additional info
I'm not worry about load balancing
App1/Qm1 does not fail. i stop the application app1 when i need to migrate the application code. During the code migration, app2/qm2 will be initiated which requires the Gateway to point to qm2 to avoid outages.
Gateway is running on sun solaris.
The motivation for changing is to avoid a manual process from Gateway qmgr to App2/Qm2.
thanks. |
There is no need in a cluster for a manual process. If you need to put App1 in maintenance put inhibit the queue for App1. You can then put app1 in maintenance and the new messages will be automatically be directed to App2. When done put enable the queue for App1 and the cluster will load balance again...
Standard cluster behavior. Read up in the clustering manual... Enjoy 
_________________
MQ & Broker admin |
|
| 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
|
|
|
|
