| Author |
Message
|
| venkat kurra |
 Posted: Mon Jan 10, 2005 2:37 pm Post subject: Moving configuration manager to a different server |
 |
|
Master
Joined: 18 Oct 2001
Posts: 245
Location: Bloomington , IL
|
Hi,
We have a WBIMB Broker and the Configuration manager running on the same server(Windows 2000).We are planning to move the configuration manager to a different server(Windows 2000).
Can we use the same configuration database/qmgr for the other server?
If we delete the existing configuration manager then the broker doesn't like the new deploy by the other configuration manager(New).
Any ideas to keep some work?
_________________
Thanks,
Venkat Kurra
IBM Certified Specialist-MQSeries
IBM Websphere MQSeries Administrator
IBM WebSphere Message Broker System Admin |
|
| Back to top |
|
 |
| kirani |
| Posted: Mon Jan 10, 2005 4:54 pm Post subject: |
|
|
Jedi Knight
Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA
|
This is what I think you should do,
1. Backup your config mgr DB first.
2. Delete the Broker physically and also from the topology.
3. Delete the config mgr on machine 1.
4. Create the config mgr on machine 2 using the same/old config mgr and MRM db.
5. Create the broker once again on machine 1 using the old Broker DB.
6. Add the broker to the configuration manager and deploy complete topology on machine 2.
_________________
Kiran
IBM Cert. Solution Designer & System Administrator - WBIMB V5
IBM Cert. Solutions Expert - WMQI
IBM Cert. Specialist - WMQI, MQSeries
IBM Cert. Developer - MQSeries
|
|
| Back to top |
|
|
| jefflowrey |
| Posted: Mon Jan 10, 2005 5:01 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
I wonder if it's not simpler than that.
I haven't tried this, but I wonder if merely backing up the config mgr, and the broker, and then deleting the config manager, recreating it on the new machine, and then restoring *both* databases won't work?
Hrm.
Oh!
No. I think there would be an issue with the change in queue manager names with the configuration manager. Because the Config Manager is moving, you'll need a new queue manager for it, which will have a different name (unless you weren't using the same in a single machine install).
That will likely hose up the registration with the broker.
Kirani's way is better.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| venkat kurra |
| Posted: Tue Jan 11, 2005 1:18 pm Post subject: |
|
|
Master
Joined: 18 Oct 2001
Posts: 245
Location: Bloomington , IL
|
Kirani, Currect me if i am wrong.
| Quote: |
1. Backup your config mgr DB first.
2. Delete the Broker physically and also from the topology.
3. Delete the config mgr on machine 1.
4. Create the config mgr on machine 2 using the same/old config mgr and MRM db.
5. Create the broker once again on machine 1 using the old Broker DB.
6. Add the broker to the configuration manager and deploy complete topology on machine 2. |
If i backup the config mgr DB first then the database has broker topology information, Is it possible to add the broker(same name with different UUID) and deploy in step 6?
If we need the Broker for some time, Can i delete and recreate the broker after finishing all my configuration work(2 & 5 after 1,3 & 4)?
Step 2: Do you want me delete the Broker with out work path option(-w)? If so i can use the old Broker DB for step 5.
_________________
Thanks,
Venkat Kurra
IBM Certified Specialist-MQSeries
IBM Websphere MQSeries Administrator
IBM WebSphere Message Broker System Admin |
|
| Back to top |
|
|
| kirani |
| Posted: Tue Jan 11, 2005 11:29 pm Post subject: |
|
|
Jedi Knight
Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA
|
| venkat kurra wrote: |
If i backup the config mgr DB first then the database has broker topology information, Is it possible to add the broker(same name with different UUID) and deploy in step 6?
|
Yes, you can.
| venkat kurra wrote: |
If we need the Broker for some time, Can i delete and recreate the broker after finishing all my configuration work(2 & 5 after 1,3 & 4)?
|
I think so.
| venkat kurra wrote: |
Step 2: Do you want me delete the Broker with out work path option(-w)? If so i can use the old Broker DB for step 5.
|
Yes. you don't have to use the workpath option.
Please make sure you backup all your DB before you try this.
_________________
Kiran
IBM Cert. Solution Designer & System Administrator - WBIMB V5
IBM Cert. Solutions Expert - WMQI
IBM Cert. Specialist - WMQI, MQSeries
IBM Cert. Developer - MQSeries
|
|
| Back to top |
|
|
| venkat kurra |
| Posted: Fri May 13, 2005 5:38 am Post subject: |
|
|
Master
Joined: 18 Oct 2001
Posts: 245
Location: Bloomington , IL
|
Now i am executing the proof of concept to move the configuration to a different server.
Some how it was not successfull with the following scenario....
1. Configuration manager and broker are on Node1
2. Stop the configuration and broker services and take the backup of configuration database.
3. delete the broker (mqsideletebroker <broker name>)
4. start the configuration and delete the broker from the toolkit
Here are the Toolkit event messages…
BIP1537W: Unable to remove configuration data from broker BROKER: broker no longer exists on queue manager BROKER.
Broker BROKER was deleted using the Message Brokers Toolkit and a deploy operation subsequently attempted to remove all configuration data. However the broker was found to no longer exist on queue manager BROKER.
No action should be required. This normally means that the broker been deleted using the mqsideletebroker command.
BIP1540I: Broker BROKER has been removed from the configuration repository.
Broker BROKER was deleted using the Message Brokers Toolkit and a deploy operation subsequently attempted to remove all configuration data. Either the deploy operation succeeded, or the broker was found to no longer exist on the target queue manager, as indicated by earlier messages. Accordingly the Configuration Manager has removed all trace of the broker from the configuration repository. No user action required.5. FTP the configuration database to node2 and restore the database
6. Create the configuration manager on node2 with the restored database(the queue manager name is same as the configuration queue manager on node1). Start the configuration manager.
7. Create the broker with the existing database on node1 & start the broker.
8. Switch the broker channels point to new configuration queue manager(reset all channels)
9. Once I connect to the configuration manager through toolkit, I can see the broker and all Execution groups.
10. If I do a complete deploy then getting the following errors
BIP2056I: Broker BROKER successfully processed the entire internal configuration message.
An internal configuration message was processed to completion. No user action required.
BIP4045I: Configuration changed successfully.
The message broker received a configuration message and updated its configuration accordingly. This change concerned its publish-subscribe capability. No user action required.
BIP1536S: Configuration Manager unable to register for internal subscriptions with broker BROKER.
Although the preceding deploy operation was successful, a subsequent attempt by the Configuration Manager to register for internal subscriptions with broker BROKER was not successful. This means that the Message Brokers Toolkit may not reliably show the correct status of the resources assigned to broker BROKER. The Configuration Manager also writes this message to the system event log, accompanied by other messages giving details of the problem.
Look at the messages for this problem in the system event log. Determine and correct the cause of the problem before attempting to deploy to this broker again. If this problem persists, contact your IBM support center.
11. If I try to start a flow
BIP2087E: Broker BROKER was unable to process the internal configuration message.
The entire internal configuration message failed to be processed successfully.
The internal configuration message failed to be processed, use the messages following this message to determine the reasons for the failure.
BIP2062E: Broker BROKER (UUID 1f000ad2-0301-0000-0080-aa13e7f09b7e) Execution Group '' (UUID 20000ad2-0301-0000-0080-aa13e7f09b7e) detected that the deployed configuration message received contained an invalid XML tag.
The configuration message received could not be applied to the broker's configuration. This could occur for any of the following reasons: The configuration message XML tag directs an execution group to be created but the execution group already exists. The configuration message XML tag directs an execution group to be changed but the execution group does not exist. The configuration message is rejected.
Use the Message Brokers Toolkit to redeploy to the Execution Group. Contact your IBM support center if you are unable to resolve the problem.
Did i miss any thing?
_________________
Thanks,
Venkat Kurra
IBM Certified Specialist-MQSeries
IBM Websphere MQSeries Administrator
IBM WebSphere Message Broker System Admin |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Fri May 13, 2005 5:54 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
| venkat kurra wrote: |
| Did i miss any thing? |
Step 3 and 4 are in the wrong order.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| venkat kurra |
| Posted: Fri May 13, 2005 11:13 am Post subject: |
|
|
Master
Joined: 18 Oct 2001
Posts: 245
Location: Bloomington , IL
|
No luck Jeff.
(deleted broker reference from the toolkit and then deleted the broker)
This time i used only one server to narrow down...
Broker and configuration created and deployed a test flow
Stop the configuration manager and took the DB backup
Stop the broker and took the broker DB backup
Start the config and Delete the Broker reference on the toolkit
Delete the broker(mqsideletebroker <broker name>)
Stop the config and delete the configuration manager(deleteconfigmgr -w -n)
Restore the Configuration database on the same server
Create the configuration manager & start
Create the broker with the exisitng database(also tried a different scenario with the broker original backup copy) & start
Connect to the toolkit and can see the broker and execution group with a flow.
Still i am getting exact same error(BIP1436S) after the deploy.
_________________
Thanks,
Venkat Kurra
IBM Certified Specialist-MQSeries
IBM Websphere MQSeries Administrator
IBM WebSphere Message Broker System Admin |
|
| Back to top |
|
|
| venkat kurra |
| Posted: Fri May 13, 2005 12:10 pm Post subject: |
|
|
Master
Joined: 18 Oct 2001
Posts: 245
Location: Bloomington , IL
|
It Works like this,
Disconnect Configuration manager from the Toolkit
Stop the configuration manager and take the database backup
Delete the configuration manager(deleteconfigmgr -w -n)
Recreate the configuration manager with the backup copy
Start the configuration manager.
"Don't tuch the broker"
If you delete and recreate the broker, then the UUID might be causing the problem.
_________________
Thanks,
Venkat Kurra
IBM Certified Specialist-MQSeries
IBM Websphere MQSeries Administrator
IBM WebSphere Message Broker System Admin |
|
| Back to top |
|
|
| mqmatt |
| Posted: Sat May 14, 2005 11:57 am Post subject: |
|
|
Grand Master
Joined: 04 Aug 2004
Posts: 1213
Location: Hursley, UK
|
| venkat kurra wrote: |
It Works like this,
Disconnect Configuration manager from the Toolkit
Stop the configuration manager and take the database backup
Delete the configuration manager(deleteconfigmgr -w -n)
Recreate the configuration manager with the backup copy
Start the configuration manager.
"Don't tuch the broker"
If you delete and recreate the broker, then the UUID might be causing the problem. |
...so long as the new Config Manager has the same queue manager name, or you somehow connect up the old queue manager's SYSTEM.BROKER.ADMIN.REPLY queue to point to the new one.
Otherwise, the broker will be publishing status messages (start/stop message flows etc.) to the wrong place.
A complete deploy should sort things out. |
|
| Back to top |
|
|
| Satyanarayan Mishra |
| Posted: Fri Sep 09, 2005 3:41 am Post subject: Excution Group is not running |
|
|
Novice
Joined: 22 Aug 2004
Posts: 19
|
Hi all
I am using WBIMB 5.0 with csd05 on win2k
While depolying on the default execution group i am getting this errors one after another.
1. BIP2062E: Broker BRK_LC (UUID 265d6b3a-0601-0000-0080-a31dcf1739c8) Execution Group 'Test' (UUID 569b7c3a-0601-0000-0080-a31dcf1739c8) detected that the deployed configuration message received contained an invalid XML tag.
The configuration message received could not be applied to the broker's configuration. This could occur for any of the following reasons: The configuration message XML tag directs an execution group to be created but the execution group already exists. The configuration message XML tag directs an execution group to be changed but the execution group does not exist. The configuration message is rejected.
Use the Message Brokers Toolkit to redeploy to the Execution Group. Contact your IBM support center if you are unable to resolve the problem.
2. BIP2087E: Broker BRK_LC was unable to process the internal configuration message.
The entire internal configuration message failed to be processed successfully.
The internal configuration message failed to be processed, use the messages following this message to determine the reasons for the failure.
Any ideas
Thanks |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Fri Sep 09, 2005 3:43 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
You should have started a new thread for this question.
You should have used the search to find the other instances of this same problem.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
|
|
