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 a Configuration Manager during
migration is an issue, or if you do not have additional hardware available,
you might want to migrate the Configuration Manager to
a different location on the same system. Complete the following steps:
- Install WebSphere Business Integration Message Broker Version
6.0 in a location
other than where WebSphere Business Integration Message Broker Version
5.0 is installed. For detailed instructions, see Installation Guides.
- Create a Version 6.0 Configuration Manager specifying
the data source, user name, and password required to access the Version 5.0 Configuration Manager database.
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.
- 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.
- Stop the Version 5.0 Configuration Manager. For detailed instructions, see the WebSphere Business Integration Message Broker Version
5.0 information
center.
- Start the Version 6.0 Configuration Manager. For detailed instructions, see Starting and stopping the Configuration Manager.
- Within the WebSphere Business Integration Message Broker Version
6.0 installation,
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.
Refer to DB2 documentation for instructions.