Author |
Message
|
cots |
Posted: Wed Mar 24, 2004 10:30 am Post subject: Same QM name on a cluster? |
|
|
Centurion
Joined: 16 Jun 2003 Posts: 105
|
Hi all,
I have five AIX boxes including MQSeries 5.3. What I like to do is,
1. Create a MQ cluster among all the QM.
2. Two of them having the same queue manager name.
3. the two queue manager from above 2, on one of them will be a full repository.
Can someone pls tell me whether is this fessible or not? What I really concern about is, among the cluster there are queue manager with the same name, is it OK or not?
thanks in advance |
|
Back to top |
|
 |
Michael Dag |
Posted: Wed Mar 24, 2004 10:58 am Post subject: |
|
|
 Jedi Knight
Joined: 13 Jun 2002 Posts: 2607 Location: The Netherlands (Amsterdam)
|
|
Back to top |
|
 |
cots |
Posted: Wed Mar 24, 2004 1:16 pm Post subject: |
|
|
Centurion
Joined: 16 Jun 2003 Posts: 105
|
Hi Michael,
Thank you for the response and pardon of my unawareness, I couldn't find any place where it mentioned not to use same queueu manager name in the cluster. could you pls give the exactly chapter in the book or URL to the information
Thanks again |
|
Back to top |
|
 |
vennela |
Posted: Wed Mar 24, 2004 1:22 pm Post subject: |
|
|
 Jedi Knight
Joined: 11 Aug 2002 Posts: 4055 Location: Hyderabad, India
|
But why do you want to use the same names for two different queue managers and cluster them. Even if it is possible to do so it is not a good thing to do. WHY do you want to cluster them |
|
Back to top |
|
 |
jefflowrey |
Posted: Wed Mar 24, 2004 1:28 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002 Posts: 19981
|
It's not a good thing to have two Queue Managers with the same name, period.
It may or may not be bad, but it's certainly not good.
And the manual on Clustering should tell you why it's not allowed to have two QMs with the same name in the same cluster. _________________ I am *not* the model of the modern major general. |
|
Back to top |
|
 |
EddieA |
Posted: Wed Mar 24, 2004 3:17 pm Post subject: |
|
|
 Jedi
Joined: 28 Jun 2001 Posts: 2453 Location: Los Angeles
|
Taken from the Cluster manual:
Quote: |
Each cluster queue manager must have a name that is unique throughout all the clusters of which it is a member. |
Or:
Quote: |
Queue manager names must be unique within a cluster for it to work correctly |
Cheers, _________________ Eddie Atherton
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Message Broker V7.0 |
|
Back to top |
|
 |
cots |
Posted: Thu Mar 25, 2004 7:08 am Post subject: |
|
|
Centurion
Joined: 16 Jun 2003 Posts: 105
|
Thank you very much for all the responses |
|
Back to top |
|
 |
Michael Dag |
Posted: Thu Mar 25, 2004 9:09 am Post subject: |
|
|
 Jedi Knight
Joined: 13 Jun 2002 Posts: 2607 Location: The Netherlands (Amsterdam)
|
jefflowrey wrote: |
It's not a good thing to have two Queue Managers with the same name, period. |
a little addition to that statement is needed (IMHO): within the same environment
Working with fully seperated DTAP environments, of each QueueManager with the same name I have 4  _________________ Michael
MQSystems Facebook page |
|
Back to top |
|
 |
jefflowrey |
Posted: Thu Mar 25, 2004 9:51 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002 Posts: 19981
|
MichaelDag wrote: |
jefflowrey wrote: |
It's not a good thing to have two Queue Managers with the same name, period. |
a little addition to that statement is needed (IMHO): within the same environment |
Not by my opinion. I'd qualify it as "within the same network".
MichaelDag wrote: |
Working with fully seperated DTAP environments, of each QueueManager with the same name I have 4  |
Again, I'd rather differentiate my DTAP environments in the QM name as well. Apps shouldn't know what the QM name is, and deployment tools should be smart enough to adjust for the correct environment.
I'd hate to be in a situation where the only way I can reliably tell where a message came from is an automatically generated MsgID. But if I was in such a situation, I'd hate to be stuck not knowing if it came from Dev or Test or Prod....
But that's just me. _________________ I am *not* the model of the modern major general. |
|
Back to top |
|
 |
Michael Dag |
Posted: Thu Mar 25, 2004 2:40 pm Post subject: |
|
|
 Jedi Knight
Joined: 13 Jun 2002 Posts: 2607 Location: The Netherlands (Amsterdam)
|
jefflowrey wrote: |
Again, I'd rather differentiate my DTAP environments in the QM name as well. Apps shouldn't know what the QM name is, and deployment tools should be smart enough to adjust for the correct environment. |
As always interested in other points of view.
Does that mean you always work with default QM's?
Which tools do you think are that 'smart'?
for example do you use the QMnames in channelnames?
say you have QM1DEV, QM1TST, QM1ACC, QM1PRD, how do you deal with those changes when going through DTAP? _________________ Michael
MQSystems Facebook page |
|
Back to top |
|
 |
jefflowrey |
Posted: Thu Mar 25, 2004 8:01 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002 Posts: 19981
|
MichaelDag wrote: |
As always interested in other points of view.
Does that mean you always work with default QM's? |
No. That's not a requirement. The app should just be written in such a way that the QM name is taken from some form of deployment descriptor.
Quote: |
Which tools do you think are that 'smart'? |
I'm rather sure I said "should be"...
Quote: |
for example do you use the QMnames in channelnames?
say you have QM1DEV, QM1TST, QM1ACC, QM1PRD, how do you deal with those changes when going through DTAP? |
Well... runmqsc takes a text input file, right... And text is text is text... I suppose if I felt really ambitious (and like overengineering something) I could model the runmqsc commands in a TDS message set, and use a database table and a custom-plugin...
But there are a lot easier ways to replace known pieces of text in a file with other known pieces of text...
Plus, I'm pretty sure I've mostly worked on smaller networks than you have, so the requirements are a little different. _________________ I am *not* the model of the modern major general. |
|
Back to top |
|
 |
Michael Dag |
Posted: Fri Mar 26, 2004 1:28 am Post subject: |
|
|
 Jedi Knight
Joined: 13 Jun 2002 Posts: 2607 Location: The Netherlands (Amsterdam)
|
jefflowrey wrote: |
No. That's not a requirement. The app should just be written in such a way that the QM name is taken from some form of deployment descriptor. |
ok, understand and agree.
jefflowrey wrote: |
I'm rather sure I said "should be"...
|
you did! I just couldn't think of one, so thought there was such a 'smart' tool I didn't know about...
jefflowrey wrote: |
Well... runmqsc takes a text input file, right... And text is text is text... I suppose if I felt really ambitious (and like overengineering something) I could model the runmqsc commands in a TDS message set, and use a database table and a custom-plugin...
|
ROFL!
jefflowrey wrote: |
Plus, I'm pretty sure I've mostly worked on smaller networks than you have, so the requirements are a little different. |
I don't know if my environment is bigger, I am fortunate to work at a big company that has major inhouse apps and have a fully seperated DTAP strategy,
that way we can stick with keeping as much as possible the same through all environments (except connames and security keys)
By having as few changes as possible when moving through DTAP we are also able to reduce the potential of errors sneaking in.
as always interesting comparing notes _________________ Michael
MQSystems Facebook page |
|
Back to top |
|
 |
|