Migrating a Version 5.0 Configuration Manager to Version 6.0 on a different computer that does not have DB2 installed

Migrate a Version 5.0 Configuration Manager to Version 6.0 on another system.

Before you start

Read about Coexistence with previous versions and other products.

If the Configuration Manager runs in a locale that is not listed in the Locales topic, check that the code page is one of the supported code pages and that the locale is set up correctly.

To migrate a Configuration Manager to a different computer that does not have DB2 or a JDBC client for DB2® installed, complete the following steps:

  1. Migrate the Version 5.0 Configuration Manager to Version 6.0 on the same computer:
    1. Install WebSphere Event Broker Version 6.0 in a location other than where WebSphere Business Integration Event Broker Version 5.0 is installed.
    2. Stop the Version 5.0 Configuration Manager.
    3. Launch a Version 6.0 Command Console and enter the mqsimigratecomponents command to migrate your Version 5.0 Configuration Manager.
    4. Start the Version 6.0 Configuration Manager.

      When you start the Version 6.0 Configuration Manager for the first time, it 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. You do not need to do anything, and the DB2 database is not modified.

  2. Stop the Version 6.0 Configuration Manager, and make a copy of its internal repository using the mqsibackupconfigmgr command.
  3. Install WebSphere Event Broker Version 6.0 on the second computer.
  4. On the second computer, create a Version 6.0 Configuration Manager by either issuing the mqsicreateconfigmgr command or running the BIPCRCM job on z/OS®.

    You must maintain unique queue manager names in your WebSphere MQ network. When you create the Version 6.0 Configuration Manager, choose a different queue manager name.

  5. On the second computer, 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.
  6. On the second computer, issue the mqsirestoreconfigmgr command (or the BIPRSCM job on z/OS) to overwrite the contents of the empty Version 6.0 Configuration Manager repository with the repository that you backed up from the original computer.
  7. On the second computer, start the Version 6.0 Configuration Manager.
  8. Deploy the complete topology using either the Message Brokers Toolkit or the mqsideploy command. This action subscribes all brokers in the domain with the new Version 6.0 Configuration Manager, so that the brokers publish their status messages to the correct queue manager. When deployment is complete, the brokers are managed by the Version 6.0 Configuration Manager on the new system; do not use the previous Configuration Manager.
Before you migrate your brokers, or make any configuration changes, ensure that your Configuration Manager has been migrated correctly by performing the following checks:
  1. Start the migrated Configuration Manager.
  2. Start the Message Brokers Toolkit and connect it to the Configuration Manager domain.
  3. Check the list of domain components and see if any errors are produced.
  4. Check the list of alerts for the domain and see if anything has stopped.
  5. Check that you can open the Event Log.
  6. Optional: If you have a broker running, stop and start a message flow, and check for a successful response; check that the Alerts view is updated when the message flow is stopped, and clear when the message flow is started.
If these steps are successful, you have successfully migrated your Configuration Manager . If they are unsuccessful, resolve any problems before you migrate further components or make configuration changes.
When you have migrated the Configuration Manager, migrate the rest of the components:

When you have completed these tasks, see the post-migration tasks for information about tasks that you might want to perform after migration.

Related concepts
Configuration Manager
Related tasks
Migrating a Configuration Manager from WebSphere Business Integration Event Broker Version 5.0 to WebSphere Event Broker Version 6.0
Starting and stopping a Configuration Manager
Deploying a publish/subscribe topology
Related reference
Installation Guide
mqsimigratecomponents command
mqsibackupconfigmgr command
mqsirestoreconfigmgr command
mqsideploy command
Notices | Trademarks | Downloads | Library | Support | Feedback

Copyright IBM Corporation 1999, 2009Copyright IBM Corporation 1999, 2009. All Rights Reserved.
Last updated : 2009-01-07 15:40:34

ah23823_