| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Design patterns for clusters |
« View previous topic :: View next topic » |
| Author |
Message
|
| jhidalgo |
 Posted: Mon Jun 02, 2008 1:26 pm Post subject: Design patterns for clusters |
 |
|
Disciple
Joined: 26 Mar 2008
Posts: 161
|
Hi MQAs,
We have a very big infrastructure and we create one cluster per service(product), for example if the service1 is only available in state1, state2 and state5 then I create a cluster including the qmgrs for those states. If there is a new service which includes state2, state3 and state6 that will be another cluster, including the qmgrs involved. This is because each service uses a different set of ports (with QoS, etc.) and needs to be available only for some areas.
This is all ok, but now I want to have FRs only in two servers with high availability, but that leads me to the following question:
¿Should I have one qmgr for each cluster in this two servers?
That makes like 5 qmgrs on each box for a start which is not recommended either... |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Mon Jun 02, 2008 7:35 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
If you should decide so ....
you can have 2 qmgrs highly available and be repositories for all your clusters.
For this you need to
- Ensure that all your cluster names are unique in your cluster realm
- Create a namelist including all the cluster names
- Recommended but not mandatory: the highly available repositories host no cluster queues themselves and serve only as repositories...
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
|
|
|
|
