Migrating a Version 5.0 broker to Version 6.0 on distributed operating systems

Migrate a broker to use the enhanced facilities available in a Version 6.0 broker domain.

If you stop the broker, you can migrate it immediately to the new version on the same computer. If you prefer not to stop the broker to avoid problems for your business applications, or if you want to reproduce the broker capability on another computer, you can move the Version 5.0 broker's application logic onto a separate Version 6.0 broker.

If you are using the Version 5.1 Message Brokers Toolkit, replace all references to "Version 5.0" with "Version 5.1".

Select the topic that is appropriate to your environment.

Migrating a broker on the same computer

To migrate a Version 5.0 broker on distributed operating systems to Version 6.0 on the same computer, complete the following steps:
  1. Install WebSphere® Event Broker Version 6.0 in a different location from WebSphere Business Integration Event Broker Version 5.0.
  2. In your Version 5.0 command environment, stop the Version 5.0 broker.
  3. Stop all channels that are connected to the Version 5.0 broker.
  4. Update the ODBC definitions file to Version 6.0 format by following the instructions in Updating your ODBC definitions when migrating.
  5. 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
  6. Enter the mqsimigratecomponents command to migrate the broker. For example:
    mqsimigratecomponents Broker1
  7. If you are running Version 6.0 on a 64-bit operating system, make the following changes to your environment:
    • You no longer have to export 32-bit libraries in the LIBPATH environment variable. Remove all variable settings similar to the following settings:
      export LD_LIBRARY_PATH=[DB2instanceDir]/sqllib/lib32:$LD_LIBRARY_PATH
      export SHLIB_PATH=$ORACLE_HOME/lib32:$SHLIB_PATH
    • If you want to continue to use 32-bit execution groups, and you use DB2® for your broker database, set the appropriate environment variable for the DB2 version that you have installed.

      For DB2 Version 8:

      MQSI_LIBPATH32=$MQSI_LIBPATH32:[DB2InstanceDir]/sqllib/lib
      For DB2 Version 9:
      MQSI_LIBPATH32=$MQSI_LIBPATH32:[DB2InstanceDir]/sqllib/lib32
      If your broker will support only 64-bit execution groups, this variable is not required.
  8. Start the Version 6.0 broker by using the mqsistart command.

Migrating a Version 5.0 broker's application logic to another installation

Before you start

To complete this task you must have either a Version 5.0 or a Version 6.0 Message Brokers Toolkit available.

Before you migrate a broker, ensure that you do not have any aggregations in progress. When you migrate a broker to Version 6.0, all live data that is being stored for aggregations in progress is lost.

If the broker 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 broker on distributed operating systems to Version 6.0 at a different location on the same computer, or to a different computer, complete the following steps:
  1. Install WebSphere Event Broker Version 6.0 either as a new instance on the computer where WebSphere Business Integration Event Broker Version 5.0 is installed, or on a different computer. For detailed instructions, see the Installation Guide.
  2. Update the ODBC definitions file to Version 6.0 format by following the instructions in Updating your ODBC definitions when migrating.
  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 Version 6.0 broker by using the mqsicreatebroker command; give it a name that is different from the name of the Version 5.0 broker.

    Brokers cannot share queue managers. You cannot migrate a broker to a queue manager that is already being used by an existing broker.

  5. Start the Version 6.0 broker by using the mqsistart command.
  6. Add the new broker to the domain by completing the following tasks:
    1. Create a Configuration Manager
    2. Create a domain connection
    3. Connect to the broker domain
    4. Add a broker to a broker domain
  7. Write a list of the execution groups that you have on the Version 5.0 broker, and create these same execution groups on the new broker. Use either the Version 5.0 or Version 6.0 Message Brokers Toolkit to complete this step.
  8. Deploy the message flows of the Version 5.0 broker to the Version 6.0 broker. Use either the Version 5.0 or Version 6.0 Message Brokers Toolkit to complete this step.
  9. Configure all other relevant properties of the Version 5.0 broker on the Version 6.0 broker. For example, you might need to configure properties that you set by using the mqsichangeproperties command, or as a result of using certain nodes, such as Publication or SCADA nodes.
  10. Stop the Version 5.0 broker. Start of changeIf you have installed Version 6.1 on the same computer, you must enter the mqsistop command in the correct Version 5.0 command environment.End of change
  11. Remove the Version 5.0 broker from the workbench.
  12. Redeploy the topology.
  13. Delete the Version 5.0 broker by using the mqsideletebroker command.
When you have migrated the broker, 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
Brokers
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:35

ah23831_