Migrating a Version 5.0 Configuration Manager to Version 6.0 on the same computer

Migrate a Version 5.0 Configuration Manager to Version 6.0 on the same 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 Version 5.0 Configuration Manager to Version 6.0:
  1. Install WebSphere Event Broker Version 6.0 in a location other than where Version 5.0 is installed.
  2. In your Version 5.0 command environment, stop the Version 5.0 Configuration Manager by using the mqsistop command.
  3. Start of changeSet up the correct Version 6.0 command environment:
    • Linux platformUNIX platform Start of changeOn Linux® and UNIX® systems, open a new shell and run the environment profile mqsiprofile for this Version 6.0 installation.End of change
    • Windows platform On Windows®, click Start, and open the Command Console that is associated with this Version 6.0 installation.
    End of change
  4. Run the mqsimigratecomponents command to migrate your Version 5.0 Configuration Manager. For example:
    mqsimigratecomponents ConfigMgr
  5. Run the mqsistart command to start the Version 6.0 Configuration Manager.

If you do not have additional hardware available, but you want to confirm the successful migration of the Configuration Manager before you remove the Version 5.0 Configuration Manager, migrate the Configuration Manager to a different location on the same computer. If you use this method, you can also change the name of the Configuration Manager.

Complete the following steps:
  1. Install WebSphere Event Broker Version 6.0 in a location other than where Version 5.0 is installed.
  2. In your Version 5.0 command environment, stop the Version 5.0 Configuration Manager by using the mqsistop command.
  3. Start of changeSet up the correct Version 6.0 command environment:
    • Linux platformUNIX platform Start of changeOn Linux and UNIX systems, open a new shell and run the environment profile mqsiprofile for this Version 6.0 installation.End of change
    • Windows platform On Windows, click Start, and open the Command Console that is associated with this Version 6.0 installation.
    End of change
  4. Create a new Version 6.0 Configuration Manager by using the mqsicreateconfigmgr command.

    You must specify a different name and a different queue manager name for the Version 6.0 Configuration Manager.

    Use the -n parameter of the mqsicreateconfigmgr command to specify the Version 5.0 Configuration Manager database. This option initializes the Version 6.0 Configuration Manager with the domain configuration details from the Version 5.0 Configuration Manager.

  5. Configure WebSphere MQ to connect the Version 6.0 Configuration Manager to the broker network. For example, you might need to configure channels and transmission queue definitions.
  6. Start the Version 6.0 Configuration Manager by using the mqsistart command.
  7. Deploy the complete topology by 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.

If you have configured MCA users on the WebSphere MQ channels to the Configuration Manager, you might encounter problems when you try to connect to the migrated Configuration Manager from the Message Brokers Toolkit Version 6.0. To resolve these problems, configure access control lists for users who are running the Message Brokers Toolkit Version 6.0. Follow the instructions in Considering security for the workbench.

Before you migrate your brokers, or make any configuration changes, perform the following checks to ensure that your Configuration Manager has been migrated correctly:
  1. Start the migrated Configuration Manager.
  2. Start the Message Brokers Toolkit and connect it to the domain that is managed by this Configuration Manager.
  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
Backing up WebSphere Business Integration Event Broker Version 5.0 resources
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
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

ah23824_