Migrating a Version 5.0 Configuration Manager to Version 6.0 on a different computer that has 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.

An existing Windows® Configuration Manager can be migrated to a Version 6.0 Configuration Manager on any of the supported operating systems through 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 Event Broker Version 6.0 on the computer to which you are migrating your Version 5.0 Configuration Manager.
  2. Modify the environment in which you are going to create the Version 6.0 Configuration Manager. On z/OS®, update the BIPCPROF file and submit the BIPGEN job when you have completed these updates. On all other operating systems, update the local environment.
    1. Add the following files 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 the following entry to the environment variable for libraries (for example, LIBPATH on z/OS):

      db2_install/jcc/lib

    3. Add the following content to the PATH:

      db2_install/jcc/bin

    where db2_install is the directory in which DB2 is installed at your location (for example /usr/lpp/db2710/db2710).

  3. Stop the Version 5.0 Configuration Manager.
  4. Create a Version 6.0 Configuration Manager on the second computer by issuing the mqsicreateconfigmgr command or run the BIPCRCM job on z/OS. Specify the database name, user name, and password that are required to access the Version 5.0 Configuration Manager database on Windows. For example:
    -u (userid)
    The user ID for the Configuration Manager configuration repository database.
    -p (password)
    The password associated with the database user ID.
    -n (database name)
    The identification of the database, in the following format:
    //server:port/database_name
    where:
    • server is the IP address of the computer where the database exists.
    • port is the port number of DB2 on that computer.
    • database_name is the name of the database (for example MQSICMDB)
    For example: //9.20.235.197:50000/MQSICMDB.
    To determine the port number:
    1. Open the DB2 Control Center and right-click the DB2 instance.
    2. Select Setup Communications....
    3. Enter the user ID and password, if required.
    The properties box contains the address and port number for this DB2 instance.

    To maintain uniqueness in the WebSphere MQ network, use different queue manager names for the two Configuration Manager components.

    When you create the Version 6.0 Configuration Manager, domain information from the Version 5.0 Configuration Manager database is copied to the Version 6.0 Configuration Manager internal repository, therefore it 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. 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, 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 of the migrated 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
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
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

ah23822_