Start of change

Migrating a Version 5.0 Configuration Manager to Version 6.0: at the same location

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 migrate a Version 5.0 Configuration Manager to Version 6.0 at the same location, complete the following steps:
  1. Stop the Version 5.0 Configuration Manager. For detailed instructions, see the WebSphere Business Integration Message Broker Version 5.0 information center.
  2. 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.
  3. 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. User intervention is not required, and the DB2 database associated with the Version 5.0 Configuration Manager is not modified.

After migration, the Version 6.0 Configuration Manager modifies the Version 6.0 internal repository only. The Version 6.0 Configuration Manager does not modify the DB2 database of the Version 5.0 Configuration Manager.
If it is no longer required, you can now remove DB2 from the system. Refer to DB2 documentation for instructions.
Related concepts
Configuration Manager
Related tasks
Starting and stopping the Configuration Manager
Installation Guides
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