Start of change

Migrating a Version 5.0 Configuration Manager to Version 6.0: to a second system that has DB2 installed

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, you might want to migrate the Configuration Manager to a second system. To migrate a Configuration Manager to a second system that has DB2 or a DB2 JDBC client installed, complete the following steps:
  1. Install WebSphere Business Integration Message Broker Version 6.0 on the second system to which you want to migrate your Version 5.0 Configuration Manager. For detailed instructions, see Installation Guides.
  2. Check that the second system has a data source that can access the Version 5.0 Configuration Manager database.
  3. Stop the Version 5.0 Configuration Manager. For detailed instructions, see the WebSphere Business Integration Message Broker Version 5.0 information center.
  4. Create a Version 6.0 Configuration Manager on the second system, 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 two Configuration Managers to maintain uniqueness in the WebSphere MQ network.

    When you create the Version 6.0 Configuration Manager, domain information from the Version 5.0 Configuration Manager database is automatically copied to the Version 6.0 Configuration Manager internal repository.

  5. 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.
  6. Start the Version 6.0 Configuration Manager. For detailed instructions, see Starting and stopping the Configuration Manager.
  7. 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.
Related concepts
Configuration Manager
Related tasks
Installation Guides
Deploying a topology configuration
Starting and stopping the Configuration Manager
Migrating a Configuration Manager from WebSphere Business Integration Message Broker Version 5.0 to WebSphere Business Integration Message Broker Version 6.0


End of change