Migrating a Version 2.1 Configuration Manager to Version 6.0: to a different computer that does not have DB2 installed

This topic describes one of three ways in which to migrate a Version 2.1 Configuration Manager to Version 6.0.

Before you start

Read about Coexistence with previous versions and other products.

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 2.1 Configuration Manager to Version 6.0 on the same computer. Complete the following tasks:
    1. Install WebSphere Message Broker Version 6.0 in a location other than where WebSphere MQ Integrator Broker Version 2.1 is installed.
    2. Stop the Version 2.1 Configuration Manager.
    3. Launch a Version 6.0 Command Console and issue the mqsimigratecomponents command to migrate your Version 2.1 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 2.1 Configuration Manager, and migrates it into the internal repository of the Version 6.0 Configuration Manager. No user intervention is required, 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 Message Broker Version 6.0 on the second computer.
  4. On the second computer, create a Version 6.0 Configuration Manager by issuing the mqsicreateconfigmgr command (or the BIPCRCM job on z/OS).

    Use different queue manager names for the Version 2.1 Configuration Manager and Version 6.0 Configuration Managers to maintain uniqueness in the WebSphere MQ network.

  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. In order to associate all brokers in the domain with the new Configuration Manager, so that the brokers publish their status messages to the correct queue manager, a complete topology deploy is required on the second computer. Deploy the topology using either the Message Brokers Toolkit or the command-line interface.

    When the topology deploy has completed re-subscribing to the brokers in the domain, the brokers are managed by the new 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's 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, your Configuration Manager has been migrated successfully. If they are unsuccessful, resolve any problems before you migrate further components or make configuration changes.

After you have migrated the Configuration Manager, migrate the User Name Server.

Related tasks
Backing up Version 2.1 resources
Planning for migration from Version 2.1
Migrating from WebSphere MQ Integrator Broker Version 2.1 to WebSphere Message Broker Version 6.0
Migrating from Version 2.1 to Version 6.0: Version 6.0 coexisting temporarily with Version 2.1
Migrating from Version 2.1 to Version 6.0: migrating applications and runtime components
Migrating the tooling
Migrating the broker
Migrating the User Name Server
Related reference
mqsimigratecomponents command