| Author |
Message
|
| sclarke |
 Posted: Mon Mar 08, 2004 12:45 pm Post subject: Splitting control center machine |
 |
|
Apprentice
Joined: 05 Jan 2002
Posts: 39
|
I currently have one control center machine which has our development, qa and production environments. We are going to decommission this machine and create 2 new control center machines – one of which is going to control our development and test brokers and the other will control qa, training and 2 production brokers.
I would like to do this without having to redeploy to the various brokers - which I think I would have to do if I exported all the flows and messagesets and manually imported them into the new control center – I believe the UUID’s would not match what is in production. Is this a correct assumption?
Would I have to restore the configuration database and the mr db from the original machine and restore it to the new control center machine configuration database and then delete all references to the brokers I don’t want them to deploy to? (if you recall one will deploy only to dev/test, the other to production, qa and training).
Thank you in advance for any insights. |
|
| Back to top |
|
 |
| Michael Dag |
| Posted: Mon Mar 08, 2004 1:32 pm Post subject: |
|
|
Jedi Knight
Joined: 13 Jun 2002
Posts: 2607
Location: The Netherlands (Amsterdam)
|
well after many stumbles I now know how to 'play' with the config mgr,
but there is no easy way explaining all the details.
Are you completely getting rid of the original machine?
If not, keep that one for the production brokers,
delete the test and dev brokers from that box and deploy so the brokers are deleted... (wait for the msg broker removed from config mgr...)
Delete the dev and test brokers
and rebuild the dev and test environments from scratch... (good exercise aswell  )
_________________
Michael
MQSystems Facebook page |
|
| Back to top |
|
|
| sclarke |
| Posted: Mon Mar 08, 2004 3:08 pm Post subject: |
|
|
Apprentice
Joined: 05 Jan 2002
Posts: 39
|
| I am getting rid of the original machine - that is the problem - two completely new machines. |
|
| Back to top |
|
|
| Michael Dag |
| Posted: Mon Mar 08, 2004 3:23 pm Post subject: |
|
|
Jedi Knight
Joined: 13 Jun 2002
Posts: 2607
Location: The Netherlands (Amsterdam)
|
I was afraid of that...
Then the only way to recreate the config mgr on the new machine is to:
- backup the DB2 tables for config mgr and mrm
- install mq, mqsi, db2 on the new machine
- restore the DB2 tables
- create odbc refences
- recreate config mgr using mqsicreateconfig mgr and point to the restored DB2 tables
and then proceed with the steps described in the previous post
(keep the old machine around while doing this )
Good luck
_________________
Michael
MQSystems Facebook page |
|
| Back to top |
|
|
| mgadiraju |
| Posted: Tue Mar 09, 2004 1:27 pm Post subject: splitting control center machine |
|
|
Newbie
Joined: 09 Mar 2004
Posts: 2
Location: Melbourne, Australia
|
I am trying to do the same as sclarke and thinking along the same lines. However, I thought using the same queue manager name on the new machines might be useful. Any comments on this.
Thanks. |
|
| Back to top |
|
|
| Michael Dag |
| Posted: Tue Mar 09, 2004 2:23 pm Post subject: |
|
|
Jedi Knight
Joined: 13 Jun 2002
Posts: 2607
Location: The Netherlands (Amsterdam)
|
for the broker certainly as the relation Qmgrname - Broker name is in the original tables.
for the configmgr I did a manual scan through the tables and did not find a direct reference (also you need to recreate the configmgr and then the Qmgrname for the configmgr is part of that command)
ofcourse you need to define a transmissionQ and channels to the broker queuemanager...
So for the the recreation/restore of the production environment I would certainly use the same names to be save...
_________________
Michael
MQSystems Facebook page |
|
| Back to top |
|
|
|
|
