|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
runmqsc -w and default QM |
« View previous topic :: View next topic » |
Author |
Message
|
mqperson |
Posted: Fri Jul 20, 2007 12:32 pm Post subject: runmqsc -w and default QM |
|
|
Apprentice
Joined: 10 Jan 2006 Posts: 32
|
I have a pair of TEST Solaris boxes in a VCS Cluster and 2 Production Solaris boxes in another VCS HA Cluster. We are working on setting up MQ monitoring using home-grown unix shell scripts.
I would like to use "runmqsc -w" from one of the TEST boxes to access the Production QMs - this is to avoid running the MQ monitoring script on the production box.
But the catch is that, to do a "runmqsc -w" from the TEST box, you need a default QM on that box - which is not possible as TEST has 2 QMs in a cluster and so there can be no default QM. TEST is a look-alike of Production and we cannot create a dummy QM there.
I tried the mqsc client supportpac, but that would require a lot of changes in our monitoring script as the format in which it displays queue attributes, etc is not consistent with the usual runmqsc format.
Am I missing something ? Is there someway of working around the "runmqsc -w" needing a default qm ?
Thanks in advance. |
|
Back to top |
|
 |
EddieA |
Posted: Fri Jul 20, 2007 2:33 pm Post subject: Re: runmqsc -w and default QM |
|
|
 Jedi
Joined: 28 Jun 2001 Posts: 2453 Location: Los Angeles
|
mqperson wrote: |
which is not possible as TEST has 2 QMs in a cluster and so there can be no default QM. |
I'm assuming that you're talking hardware cluster here, and not MQ cluster.
I don't see why not, as the QMs should be mirrors of each other, and only one will be active, at any point in time, and the ini file will declare the active QM as the default.
Cheers, _________________ Eddie Atherton
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Message Broker V7.0 |
|
Back to top |
|
 |
mqperson |
Posted: Mon Jul 23, 2007 9:22 am Post subject: |
|
|
Apprentice
Joined: 10 Jan 2006 Posts: 32
|
Yes, they are in a VCS cluster, they are not in a MQ cluster. Can I still define one of them as a default. Would that not confuse the VCS clustering service at the time of failover ? |
|
Back to top |
|
 |
jefflowrey |
Posted: Mon Jul 23, 2007 9:31 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002 Posts: 19981
|
I would think that your network/security folks would not be happy to learn that you are connecting the test region to the production region.
In general, this is a poor idea.
For example, what if you need to take your test environment down? Now you won't know if sometihng breaks in production...
If you need to run this monitoring scripts, and the scripts themselves have too big an impact to run on the production machines themselves... then set up another machine in the production environment and run your monitoring from there. _________________ I am *not* the model of the modern major general. |
|
Back to top |
|
 |
mqperson |
Posted: Mon Jul 23, 2007 9:34 am Post subject: |
|
|
Apprentice
Joined: 10 Jan 2006 Posts: 32
|
Thanks Jeff, that makes sense. Its going to be difficult to convince them into setting up another machine for Production, but will definitely give that a shot before settling for running the scripts on Production.
Thank you guys! |
|
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
|
|
|
|