| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Configuration manager migration from version 5 to version 6 |
« View previous topic :: View next topic » |
| Author |
Message
|
| jlalbor |
 Posted: Mon Jun 19, 2006 10:28 am Post subject: Configuration manager migration from version 5 to version 6 |
 |
|
Apprentice
Joined: 18 Feb 2003
Posts: 38
|
Hi, we have migrated a configuration manager from version 5 with fix pack 6 to version 6.0.0.1, from a windows machine to an AIX.
We followed all steps in the Migration Manual (page 60 Migrating a Version 5.0 Configuration Manager to Version 6.0: to a different computer that has DB2 installed)
Everything seems to be fine, using the new configuration manager we can view the domain topology, start and stop flows, deploy message flows, etc.
But we have seen an issue, if we are connected to the new configuration manager using the toolkit and then stop a broker in the domain using the mqsitop command, the configuration manager never recives the messages indicating that the broker was stopped, so the toolkit never shows in the alert window that the message flows of that broker are not running.
We found that the broker is sending these messages to the old queue manager, and this is because in the broker´s configuration database there is a table named BCLIENTUSER with some records on it and in the column CLIENTID, there are values like this:
QM_WBI_CONFGIG:SYSTEM.BROKER.ADMIN.REPLY:4366674d677253756231
wich is the old configuration manager´s queue manager. We have use a different name for the new configuration manager´s Queue Manager (as recommended in the migration manual) and the new queue manager is QM.CFGMGR.DESA.01
Its obvious that the brokers have not change this value in their configuration databases, so we think that all events generated by the brokers are being sent to the old configuration manager´s queue manager.
The migration manual does not specify any migration steps to be done in the brokers when migrating the configuration manager from one machine to another.
The question here is,
Are there some migration steps we have to follow in order to change this values in the brokers databases?,
Could we change this values manually without affection the brokers configuration?
Thanks.
_________________
Ing. José Luis Albor GarcÃa
IBM Certified System Administrator – WebSphere MQ V6.0
IBM Certified Solution Designer – WebSphere Message Broker V6.0 |
|
| Back to top |
|
 |
| mqmatt |
| Posted: Tue Jun 20, 2006 3:43 am Post subject: |
|
|
Grand Master
Joined: 04 Aug 2004
Posts: 1213
Location: Hursley, UK
|
When moving the Config Manager to a new machine, you need to deploy the topology. This is to tell the brokers in the domain to start reporting their status to the new Config Manager.
Cheers
-Matt |
|
| Back to top |
|
|
| jlalbor |
| Posted: Tue Jun 20, 2006 6:59 am Post subject: |
|
|
Apprentice
Joined: 18 Feb 2003
Posts: 38
|
| mqmatt wrote: |
When moving the Config Manager to a new machine, you need to deploy the topology. This is to tell the brokers in the domain to start reporting their status to the new Config Manager.
Cheers
-Matt |
Hi Matt, what do you mean by deploying the topology?
cause what we did was:
In the Broker administration perspective in the toolkit, under the queue managers name i selected Deploy Topology Configuration -> Complete
The Configuration managers Event log returns successful messages for each broker in the domain:
| Quote: |
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.
|
But the values in the column CLIENTID in the table BCLIENTUSER in each borkers database are not updated with the new queue managers name.
Thanks & Regards.
_________________
Ing. José Luis Albor GarcÃa
IBM Certified System Administrator – WebSphere MQ V6.0
IBM Certified Solution Designer – WebSphere Message Broker V6.0 |
|
| Back to top |
|
|
| mqmatt |
| Posted: Tue Jun 20, 2006 8:00 am Post subject: |
|
|
Grand Master
Joined: 04 Aug 2004
Posts: 1213
Location: Hursley, UK
|
| Quote: |
| Deploy Topology Configuration -> Complete |
and
| Quote: |
| The Configuration managers Event log returns successful messages for each broker in the domain |
should update the subscriptions fine... please raise a PMR.  |
|
| Back to top |
|
|
| jlalbor |
| Posted: Tue Jun 20, 2006 8:38 am Post subject: |
|
|
Apprentice
Joined: 18 Feb 2003
Posts: 38
|
OK Matt, we will raise a PMR. I will update the post as soon as i have an answer from IBM.
Thanks a lot.
_________________
Ing. José Luis Albor GarcÃa
IBM Certified System Administrator – WebSphere MQ V6.0
IBM Certified Solution Designer – WebSphere Message Broker V6.0 |
|
| Back to top |
|
|
| born2win |
| Posted: Mon Nov 06, 2006 10:17 am Post subject: |
|
|
Novice
Joined: 01 Feb 2006
Posts: 16
|
| Any update after opening the PMR? |
|
| 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
|
|
|
|
