Before you start
This task is part of the following
larger task:
See the larger task to understand the context of this task and what you
must do before you start this task.
To complete this task you must have
either a Version 5.0 or a Version 6.0 broker
available.
If the lack of availability of aConfiguration Manager during
migration is an issue, you might want to migrate the Configuration Manager to
a second system. To migrate a Configuration Manager to
a second system that does not have DB2 or a DB2 JDBC client installed, complete
the following steps:
- Migrate the Version 5.0 Configuration Manager to Version 6.0 on the same system. Complete the following
tasks:
- Stop the Version 5.0 Configuration Manager. For detailed instructions, see the WebSphere Business Integration Message Broker Version
5.0 information
center.
- Install WebSphere Business Integration Message Broker Version
6.0 in the same
location where WebSphere Business Integration Message Broker Version
5.0 is installed. For detailed instructions, see Installation Guides.
- Start the Version 6.0 Configuration Manager. For detailed instructions, see Starting and stopping the Configuration Manager.
When you start the Version 6.0 Configuration Manager for the first time, the Version 6.0 Configuration Manager automatically detects domain information
in the DB2 database of the Version 5.0 Configuration Manager,
and migrates it into the internal repository of the Version 6.0 Configuration Manager. No user intervention is required, and
the DB2 database is not modified.
- Stop the Version 6.0 Configuration Manager,
and make a copy of its internal repository using the mqsibackupconfigmgr command. For detailed instructions, see Starting and stopping the Configuration Manager [AND
MQSIBACKUPCONFIGMGR TOPIC, FEATURE 34278 TO BE WRITTEN FOR B1].
- Install WebSphere Business Integration Message Broker Version
6.0 on the second
system. For detailed instructions, see Installation Guides.
- On the second system, create a Version 6.0 Configuration Manager.
You
must use different queue manager names for the Version 5.0 Configuration Manager and Version 6.0 Configuration Managers to maintain uniqueness in the WebSphere
MQ network.
- On the second system, configure WebSphere MQ to allow the Version 6.0 Configuration Manager to communicate with the broker network.
For example, you might need to configure channels, transmission queues, and
remote queue manager definitions. For detailed instructions, refer
to WebSphere MQ documentation.
- On the second system, use the mqsirestoreconfigmgr command
to overwrite the contents of the empty Version 6.0 Configuration Manager repository with the repository that you
backed up from the first system. For detailed instructions, see
[MQSIRESTORECONFIGMGR TOPIC, FEATURE 34278 TO BE WRITTEN FOR B1].
- On the second system, start the Version 6.0 Configuration Manager. For detailed instructions,
see Starting and stopping the Configuration Manager.
- On the second system, deploy the complete topology to associate
all the brokers in the domain with the Version 6.0 Configuration Manager. You can deploy the topology
using either the Message
Brokers Toolkit or the command-line
interface, on either Version 5.0 or Version 6.0.
For detailed instructions, see Deploying a topology configuration or
the WebSphere Business Integration Message Broker Version
5.0 information center.
If they are no longer required, you can now remove DB2 and WebSphere Business Integration Message Broker Version
5.0 from
both systems. Refer to DB2 documentation and to the WebSphere Business Integration Message Broker Version
5.0 information
center for instructions.