| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Cluster Implementation |
« View previous topic :: View next topic » |
| Author |
Message
|
| gag_nm |
 Posted: Wed Mar 20, 2013 10:00 pm Post subject: Cluster Implementation |
 |
|
Centurion
Joined: 16 Oct 2008
Posts: 102
|
Hi,
we have 2 Clusters CLUSA and CLUSB.each Cluster has 2 FR's and 2 PR's.
2 PR's Queue Managers where two Applications are connecting to Cluster Hosted in Different Physical Servers (Server1 and Server2).
Server1 has 2 Queue Mangers(QMPR1 which is Part of CLUSA,QMPR3 Which is Part of CLUSB)
Server2 has 2 Queue Mangers(QMPR2 which is Part of CLUSA,QMPR4 Which is Part of CLUSB)
CLUSTER CLUSA (QMFR1,QMFR2,QMPR1,QMPR2)
CLUSTER CLUSB (QMFR3,QMFR4,QMPR3,QMPR4)
Application(APP1) Connects to Cluster (CLUSA) by Using QMPR1 Queue manager
Application(APP2) Connects to Cluster (CLUSA) by Using QMPR2 Queue manager
When every CLUSA goes down, then Application side we have to change Request Queue Manager Property Follows.
Application(APP1) Request QM Property should be changed to QMPR3 Queue Manager which Connects to Cluster (CLUSB)
Application(APP2) Request QM Property should be changed to QMPR4 Queue Manager which Connects to Cluster (CLUSB)
Can we provide Solution at CLUSTER Level to Avoid changing Request QM Property at Application Side when CLUSTER CLUS A is Down, Seamless Switch over to CLUSTER CLUSB.
Please Advise .. |
|
| Back to top |
|
 |
| mqjeff |
| Posted: Thu Mar 21, 2013 3:29 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
Your question and your topology show that you don't understand clusters or MQ high availability and load balancing questions.
Applications don't connect to clusters.
Applications don't make requests of clusters.
You need someone to sit down and explain all of this to you, and work through the real objectives of your design and rework your application topology and MQ network topology to achieve the real objectives.
You've built a two-door coupe when you thought you were building a lorry. |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Mar 21, 2013 4:47 am Post subject: Re: Cluster Implementation |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| gag_nm wrote: |
| Can we provide Solution at CLUSTER Level to Avoid changing Request QM Property at Application Side when CLUSTER CLUS A is Down, Seamless Switch over to CLUSTER CLUSB. |
No, and I echo the comments of my most worhty associate.
Given that applications don't connect to clusters but to queue managers it's a simple task under WMQv7 to have the application connect to an alternate queue manager in the event of failure. This may or may not be what you need, and may or may not require you to alter your topology.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| gag_nm |
| Posted: Thu Apr 11, 2013 8:18 am Post subject: |
|
|
Centurion
Joined: 16 Oct 2008
Posts: 102
|
| Quote: |
Applications don't connect to clusters.
Applications don't make requests of clusters.
You need someone to sit down and explain all of this to you, and work through the real objectives of your design and rework your application topology and MQ network topology to achieve the real objectives.
You've built a two-door coupe when you thought you were building a lorry. |
I have clearly mentioned Applications connect to queue manager, respective queue manager is part of cluster.
| Quote: |
| Application(APP1) Connects to Cluster (CLUSA) by Using QMPR1 Queue manager |
|
|
| Back to top |
|
|
| mqjeff |
| Posted: Thu Apr 11, 2013 8:25 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| gag_nm wrote: |
I have clearly mentioned Applications connect to queue manager, respective queue manager is part of cluster.
| Quote: |
| Application(APP1) Connects to Cluster (CLUSA) by Using QMPR1 Queue manager |
|
The order of the words in that phrase are incorrect.
| Quote: |
| Application APP1 connects to QMPR1, which is a member of Cluster CLUSA |
is the correct way to say it.
Nothing, at all, connects to a cluster. Queue managers belong to one or more clusters, or participate in one or more clusters.
Queues are shared in one or more clusters.
If you have this proper understanding of what things connect to what things, then you can design a proper architecture that allows APP1 to connect to one or more queue managers that are sufficiently available to meet it's requirements. And that APP1 uses the correct mechanisms to ensure that it's response messages get sent back to the correct location where it is expecting them. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Thu Apr 11, 2013 7:16 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20696
Location: LI,NY
|
@gag_nm
You need to think differently for the use of the word cluster.
In MQ, MQ Cluster == load balancing and load balancing only!
In MQ Hi Availability is achieved either through OS HA Cluster or Multi - instance qmgrs.
Now go and read up on both!  
_________________
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
|
|
|
|
