| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Controlling the Config Manager via the QM |
« View previous topic :: View next topic » |
| Author |
Message
|
| PeterPotkay |
 Posted: Wed Oct 29, 2008 6:59 pm Post subject: Controlling the Config Manager via the QM |
 |
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
MQ 6.0.2.5
WMB 6.1.0.2
We have a script that we run while logged on as the mqm ID. This script stops and starts the QM. Since MQ 6.0 came out, we moved a lot of stuff out of the script and made them Service objects under the QM. The Trigger Monitor and QPASA are the 2 mains ones. And of course the Listener is now controlled directly by the QM.
What about the WMB Config Manager? If we created the Config Manager under UserID A, which was in the mqm group and the mqbrkrs goup, can we use mqsichangeconfigmgr with the -i switch to run the Config Manager as the mqm ID? If yes, then I think we can make a new Service object to have the QM start and stop the Config Manager. The mqm ID is in the mqbrkrs group already. The Brokers are on another server, running under User ID A.
Any gotchas? Should be fine, right?
Considering security for a Configuration Manager
http://publib.boulder.ibm.com/infocenter/wmbhelp/v6r1m0/topic/com.ibm.etools.mft.doc/ap03984_.htm
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
 |
| mqjeff |
| Posted: Thu Oct 30, 2008 2:06 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
You can't change the configmgr service user with mqsichangeconfigmgr.
You should still be able to write a script that can be called as an MQ Service that will start the configMgr, using su -c/sudo on Unix or contact admin on Windows. |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Thu Oct 30, 2008 11:14 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
Considering security for a Configuration Manager
http://publib.boulder.ibm.com/infocenter/wmbhelp/v6r1m0/topic/com.ibm.etools.mft.doc/ap03984_.htm
"When you set the service ID with the -i option on the mqsicreateconfigmgr or mqsichangeconfigmgr command, you determine the user ID under which the Configuration Manager component process runs."
For the script that runs when the server is restarted, no prob, we can just have the script (running under root) su over to the mqm ID for the QM and to the wmb ID we use for the Config Manager.
But we also have a script that we use so the MQ Admin can stop and start the QM (logged in as their ID and then they su over to mqm). As we take more and more out of that script and allow the QM to handle it, I guess it becomes easier and easier to just issue strmqm. And at that point I suppose its just as easy to issue strmqsi or stopmqsi.
Just looking for a way to have the MQ admin not have to worry about stopping or starting the Config Manager individually. Either by somehow having the script run by mqm do it (but we won't hardcode a password for the su command) or as an MQ QM Service object.
On Windows, the Service dependecies help you not stop the MQ service before the Config Managr service. Looking for a little of that kinda UNIX.
Yesterday on the lab machine we needed to bounce the QM to pick up some changes, ran the mqm script to restart MQ, and proceeded to hose the Config Manager because the CM was left running as the QM came down. No way to recover other than killing the bip* PIDs at that point.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| 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
|
|
|
|
