| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Using the same namelist with multiple clusters |
« View previous topic :: View next topic » |
| Author |
Message
|
| mqlover |
 Posted: Mon Oct 01, 2012 2:03 am Post subject: Using the same namelist with multiple clusters |
 |
|
Disciple
Joined: 25 Jul 2010
Posts: 176
|
Using the namelist and by increasing the NAMCOUNT property of the namelist to more than 1, can I provide multiple cluster names in the property NAME ?
Would there be any disadvantages using this?
Ex : I have a namelist NL1 and has names (CLUS1,CLUS2).
If in the cluster channels of CLUS1 I give the property CLUSNL(NL1) and in the queue managers of CLUS2 also I give CLUSNL(NL1), wont there be any problem for the queue managers to understand that to which clusters they belong?
Could anybody help on this.
Thanks |
|
| Back to top |
|
 |
| bruce2359 |
| Posted: Mon Oct 01, 2012 4:33 am Post subject: Re: Using the same namelist with multiple clusters |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
| mqlover wrote: |
Using the namelist and by increasing the NAMCOUNT property of the namelist to more than 1, can I provide multiple cluster names in the property NAME ?
Would there be any disadvantages using this?
Ex : I have a namelist NL1 and has names (CLUS1,CLUS2).
If in the cluster channels of CLUS1 I give the property CLUSNL(NL1) and in the queue managers of CLUS2 also I give CLUSNL(NL1), wont there be any problem for the queue managers to understand that to which clusters they belong?
Could anybody help on this.
Thanks |
What exactly is the purpose of a NAMELIST? Why would queue managers have a problem understanding for which clusters they are repositories?
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Mon Oct 01, 2012 5:05 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
You can't define a namelist on one queue manager, and refer to it from another.
If you specify CLUSNL, the queue manager in question or the object in question belongs to *all* clusters in the namelist. |
|
| Back to top |
|
|
| mqlover |
| Posted: Mon Oct 01, 2012 5:48 pm Post subject: Using the same namelist with multiple clusters |
|
|
Disciple
Joined: 25 Jul 2010
Posts: 176
|
Hi,
My scenario :
I have a namelist NL1.channels and in the property names(CLUS1).
Similarly, NL1.repos for repositories and in the property names(CLUS1).
This CLUS1 is the cluster for queue managers Gateway and QM1.
The REPOSNL propety of Gateway and QM1 queuemanager have NL1.repos.
Now, I have a requirement to build a cluster between the queuemanagers Gateway and QM2 say CLUS2.
If I alter the namelist NL1.repos to hold both the clusters in the names property then my wont my QM2 also be part of CLUS1 which I do not want to happen.
How could I design this effectively so that
a)Gateway and QM1 belong to CLUS1.
b)Gateway and QM2 belong to CLUS2.
Thanks in advance. |
|
| Back to top |
|
|
| exerk |
| Posted: Tue Oct 02, 2012 12:46 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
If you want separation of queue managers in clusters then do NOT namelist their channels - use separate CLUSSDR/CLUSRCVR channels for each cluster. In regard to clusters, the only namelist I would recommend for use is one for REPOSNL, where a queue manager is FR for multiple clusters.
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Tue Oct 02, 2012 6:07 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| exerk wrote: |
| If you want separation of queue managers in clusters then do NOT namelist their channels - use separate CLUSSDR/CLUSRCVR channels for each cluster. In regard to clusters, the only namelist I would recommend for use is one for REPOSNL, where a queue manager is FR for multiple clusters. |
Abandon your notion of using namelists here, you'll end up with all qmgrs being part of all clusters before you realize it.
Second of all, you don't remotely have enough queue managers to actually use a cluster here, much less two. You should have at least five - three in cluster1 and four in cluster 2.
If you insist on doing this with only three qmgrs, then - gateway should be a partial repository for only clus1
- qm1 should be an FR for clus1, and a pr for clus2 (that means it's repos attribute is only clus1)
- qm2 is an fr for clus2
|
|
| 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
|
|
|
|
