| Author |
Message
|
| TonyD |
 Posted: Wed Nov 26, 2008 2:17 pm Post subject: Including ConfigMgr QM in broker clusters |
 |
|
Knight
Joined: 15 May 2001
Posts: 540
Location: New Zealand
|
We have our brokers in MQ clusters for the usual reasons and I was wondering about the advisability, or otherwise, of including the CM queue manager in the clusters. We have a CM that administers six brokers, three clusters each with a pair of brokers. The CM QM would need three cluster receiver channels, one for each cluster, and a cluster sender channel to a repository QM in each cluster. In addition I expect the SYSTEM.BROKER queues at each broker QM would have to be defined as cluster queues. The XQH in messages from the CM QM includes the destination QM so messages should be delivered to the correct broker.
Has anyone investigated or implemented this approach? The six channel defs would replace twelve channel defs and twelve XMITQ defs. |
|
| Back to top |
|
 |
| PeterPotkay |
| Posted: Wed Nov 26, 2008 2:22 pm Post subject: Re: Including ConfigMgr QM in broker clusters |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
I'm about to stand up a bunch of new Brokers and was mulling over the same thing yesterday. I'm leaning towards using conventional channels. Its just easier to do problem resolution. I don't need to load balance from the CM to the Brokers. And while there maybe less MQ Objects to build, big deal, I only have a few brokers in each cluster.
If I had 100 Brokers, then maybe my answer would be different.
| TonyD wrote: |
| In addition I expect the SYSTEM.BROKER queues at each broker QM would have to be defined as cluster queues. |
I dunno. Maybe not. Probably not. The CM is not spraying its deploy messages to any SYSTEM.BROKER.* queue, its going to address it specifically to a particular QM. Inside an MQ cluster you can send messages to a specific non clustered queue as long as you specify the destination QM and the destination QM is happily partcipating in the cluster otherwise.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| TonyD |
| Posted: Wed Nov 26, 2008 2:49 pm Post subject: |
|
|
Knight
Joined: 15 May 2001
Posts: 540
Location: New Zealand
|
Hi Peter, I was hoping you might see and comment on this, bearing in mind your considerable cluster experience.
At the moment I have used conventional channels. As you say, there is no load balancing ... on the contrary it must be avoided ... and the only real benefit is the reduction in admin overhead. However I quite like the idea of using the cluster facilities as the site standard unless there is a specific reason not to.
Are you aware of any IBM recommendation or discussion paper on this subject? |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Wed Nov 26, 2008 2:51 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
With you a 100 % Peter.
Using the Namelist you could have the cluster receiver linked to the name list: (clustnl) and as such have only 1 cluster receiver channel.
At the same time and as you are not an FR in any of the clusters I believe you would have to have a cluster sender chl to one FR of each cluster.
If you have a common FR qmgr for all clusters (reposnl); you can use the same technique and have only 1 cluster sender channel defined using the afore mentioned namelist.
Total 2 to 4 chl definitions and not 6. Have fun 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| TonyD |
| Posted: Wed Nov 26, 2008 3:16 pm Post subject: Re: Including ConfigMgr QM in broker clusters |
|
|
Knight
Joined: 15 May 2001
Posts: 540
Location: New Zealand
|
| PeterPotkay wrote: |
| TonyD wrote: |
| In addition I expect the SYSTEM.BROKER queues at each broker QM would have to be defined as cluster queues. |
I dunno. Maybe not. Probably not. The CM is not spraying its deploy messages to any SYSTEM.BROKER.* queue, its going to address it specifically to a particular QM. Inside an MQ cluster you can send messages to a specific non clustered queue as long as you specify the destination QM and the destination QM is happily partcipating in the cluster otherwise. |
As you thought ... did a quick test where I created a new broker and then added its QM and an existing CM QM I have to a new cluster. 4 * cluster channels (since both are FRs). Deploys then worked fine from the CM to the new broker over the cluster channels and to an existing broker over conventional channels. |
|
| Back to top |
|
|
| TonyD |
| Posted: Wed Nov 26, 2008 6:14 pm Post subject: |
|
|
Knight
Joined: 15 May 2001
Posts: 540
Location: New Zealand
|
Found this:
| Quote: |
If you use clusters with WebSphere Message Broker, consider the following queues:
For SYSTEM.BROKER queues:
The SYSTEM.BROKER queues are defined for you when you create WebSphere Message Broker components, and are not defined as cluster queues. Do not change this attribute.
For broker, Configuration Manager, and User Name Server connectivity:
If you define the queue managers that support your brokers, the Configuration Manager, and the User Name Server to a cluster, you can benefit from the simplified administration provided by WebSphere MQ clusters. You might find this particularly relevant for the brokers in a collective, which must all have WebSphere MQ interconnections.
|
I think we'll go with it! |
|
| Back to top |
|
|
|
|
