|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
creating new windows configmgr for old solaris brokers |
« View previous topic :: View next topic » |
Author |
Message
|
smaram1 |
Posted: Fri Jul 18, 2003 10:47 am Post subject: creating new windows configmgr for old solaris brokers |
|
|
Novice
Joined: 06 May 2003 Posts: 19
|
Hi All,
I went through forum and there were several threads on this issue but not clear.
This is the situation.
I have two solaris brokers and i am using one windows configuration manager to deploy same flows onto both solaris brokers. It works fine.
Jus imagine that there was a hardware failure and i lost windows machine. I am trying to create a new windows configmgr and i am seeing some issues.
I DONT WANT TO TOUCH SOLARIS BROKERS. I JUS WANT TO CONFIGURE NEW WINDOWS CONFIGMGR AND DEPLOY. IS THIS POSSIBLE?
I installed new configmgr, imported messages flows, created brokers, did assignments and when i try to deploy i am getting this problem.
BIP2045E: Broker MQSI2_BROKER (UUID 4aad59f6-f000-0000-0080-c11313c38303) running on WebSphere MQ queue manager 'QM_MQSI2_BROKER_1' could not process an internal configuration message because the broker identity received in the message (UUID 104a9176-f600-0000-0080-92045d29ce6a) did not match that of this broker.
Suggested Solution:
Otherwise, if the broker definition was deleted and recreated, you must use the mqsideletebroker and mqsicreatebroker commands to recreate the broker, then redeploy the configuration for the broker in order to reestablish the correct broker identity.
I tried doing this but it never works.
Can someone please comment more on this issue?
Thanks
Suresh |
|
Back to top |
|
 |
jefflowrey |
Posted: Fri Jul 18, 2003 11:49 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002 Posts: 19981
|
You need to back up and restore your ConfigMgr database to the new machine.
You will then not need to recreate your logical brokers in the new configmgr. When you created your brokers in the new ConfigMgr, it created brand new references with new IDs in the ConfigMgr database, and then tried to tell the brokers to register themselves using that ID. Since the brokers had already registered themselves with other IDs to the old ConfigMgr, this could not be done. So you need to restore the registrations in the old ConfigMgr database, or delete and recreate your brokers and then register them with the new ConfigMgr.
You may also need to import a workspace file from a Control Center connected to the old ConfigMgr, but I don't know that for sure. |
|
Back to top |
|
 |
smaram1 |
Posted: Fri Jul 18, 2003 1:15 pm Post subject: |
|
|
Novice
Joined: 06 May 2003 Posts: 19
|
Thanks for the reply Jeff.
You have certainly cleared up my doubts. I will look try to backup data on old machine and see how it works once i import onto new machine.
Thanks
Suresh |
|
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
|
|
|
|