| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Clustering brokers. |
« View previous topic :: View next topic » |
| Author |
Message
|
| jgooch |
 Posted: Tue Feb 04, 2003 7:34 am Post subject: Clustering brokers. |
 |
|
Acolyte
Joined: 29 May 2002
Posts: 63
Location: UK
|
We're in the process of upgrading to v2.1, and I'm planning to implement clustering under the brokers (there will be four brokers). The idea is that the cluster will hide which broker is servicing which flow from the outlying queue managers. This is also a first step towards a high availability configuration.
This will be the first MQ cluster we've implemented. At the moment, we run two brokers on our production machine, and the remote queues on the outlying queue managers are configured to point to whichever broker queue manager is running the appropriate flow.
Should we include the outlying application queue managers in the broker cluster? I can see how this might simplify the congfiguration but am concerned that it would be confusing to identify where each queue was physically located. Also, some of these machines are on remote sites (ie the messages come through a firewall). Is this an issue with the cluster?
If there are any general hints'n'tips, I'd also appreciate gaining the benefit of others' experience.
J. |
|
| Back to top |
|
 |
| jgooch |
| Posted: Tue Feb 04, 2003 7:42 am Post subject: |
|
|
Acolyte
Joined: 29 May 2002
Posts: 63
Location: UK
|
| ...should we consider implementing overlapping clusters or is this trying to run before we can walk? |
|
| Back to top |
|
|
| philip.baker |
| Posted: Tue Feb 04, 2003 9:36 am Post subject: |
|
|
Voyager
Joined: 21 Mar 2002
Posts: 77
Location: Baker Systems Consulting, Inc. - Tampa
|
J.,
One solution is to have the outlying queue manager(s) as part of a cluster that also includes each of the four broker QMGRs. Each QMGR broker would have queues of the same name to which a message flow Input Node is using as its input queue. (These queues, of course, are cluster queues.) The application would put messages on the queue that feeds the required message flow. No QMGR is specified. The MQ Clustering will know that the queue resides under four QMGRs and will route the message to one of the four. If one of the four goes down, the MQ Clustering will simply not route the message to the downed QMGR but will now send to one of the other three.
There are other issues to consider when implementing a proper MQClustering solution with WMQI, but the above should give you a start.
_________________
Regards,
Phil |
|
| 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
|
|
|
|
