Migrating a Version 2.1 Configuration Manager to Version 6.0: to a different computer that has DB2 installed

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

Before you start

To complete this task you must have either a Version 2.1 or a Version 6.0 broker available. Read about Coexistence with previous versions and other products.

If the lack of availability of a Configuration Manager during migration is an issue, migrate the Configuration Manager to a different computer.

An existing Windows Configuration Manager can be migrated to a Version 6.0 Configuration Manager on any of the supported operating systems via a JDBC Type 4 Universal DB2 connection.

To migrate a Configuration Manager to a different computer that has a JDBC Type 4 Universal DB2 connection installed, complete the following steps:

  1. Install WebSphere Message Broker Version 6.0 on the computer to which you want to migrate your Version 2.1 Configuration Manager.
  2. Add the following files to the environment in which you are going to create the new Configuration Manager. On z/OS, update the BIPCPROF file and submit the BIPGEN job. On all other operating systems, update the local environment.
    1. Add the following classes to the CLASSPATH:

      <db2 install>/jcc/classes/sqlj.zip
      <db2 install>/jcc/classes/db2jcc.jar
      <db2 install>/jcc/classes/db2jcc_javax.jar
      <db2 install>/jcc/classes/db2jcc_license_cisuz.jar                                  

    2. Add to the computer-specific environment variable for libraries (for example LIBPATH on z/OS):

      <db2 install>/jcc/lib

    3. Add to the PATH:

      <db2 install>/jcc/bin

    where <db2 install> is where DB2 is installed at your location (for example /usr/lpp/db2710/db2710).
  3. Stop the Version 2.1 Configuration Manager.
  4. Create a Version 6.0 Configuration Manager on the second computer by running the mqsicreateconfigmgr command (or the BIPCRCM job on z/OS), specifying the data source, user name, and password required to access the Version 2.1 Configuration Manager database. For example:

    -u (userid) The database userid on the Windows computer for the
    Configuration Manager
    -p (password) The database password on the Windows computer
    for the Configuration Manager
    -n (database name) //<server>:<port>/<database name>

    where:
    • //<server> is the IP address of the Windows computer (for example //9.20.235.197)
    • :<port> is the port number of DB2 on Windows
    • /<database name> is the name of the Windows Configuration Manager database (for example /MQSICMDB)
    For example: //9.20.235.197:50000/MQSICMDB

    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 2.1 Configuration Manager database is copied automatically to the Version 6.0 Configuration Manager internal repository. This might take a few minutes to migrate the database.

  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. Start the Version 6.0 Configuration Manager.
  7. On the second computer, deploy the complete topology to associate all the brokers in the domain with the Version 6.0 Configuration Manager. Deploy the topology using either the Message Brokers Toolkit or the command-line interface, on either Version 2.1 or Version 6.0.

If necessary, uninstall DB2 and the Version 2.1 broker.

After you have migrated the Configuration Manager, go to Migrating the broker.

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 replacing Version 2.1
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 components on different computers
Migrating the tooling
Migrating the broker
Migrating the User Name Server
Related reference
mqsimigratecomponents command