WebSphere Message Brokers
File: ah23831_
Writer: Kate Hostler

Task topic

This build: July 31, 2007 21:30:35

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

Migrate a broker to use the enhanced facilities available in a Version 6.1 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.1 broker.

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

Select the topic that is appropriate to your environment.

Migrating a Version 5.0 broker to Version 6.1

Before you start

Before migrating a broker, ensure that you do not have any aggregations in progress. When you migrate a broker to WebSphere® Message Broker Version 6.1, any live data that is being stored for aggregations in progress will be 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.1 at the same location, complete the following steps:
  1. Install WebSphere Message Broker Version 6.1 in the same location as WebSphere Business Integration Message Broker Version 5.0.
  2. Stop the Version 5.0 broker.
  3. Stop any channels to the Version 5.0 broker.
  4. Update the ODBC definitions file to Version 6.1 format by following the instructions in Updating your ODBC definitions when migrating.
  5. Set up the correct Version 6.1 command environment.
    • Linux platform UNIX platform On Linux® and UNIX® systems, run the environment profile mqsiprofile.
    • Windows platform On Windows®, open a Command Console from the Start menu.
  6. Enter the mqsimigratecomponents command to migrate the broker. For example:
    mqsimigratecomponents Broker1
  7. If you are running Version 6.1 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:
      export LD_LIBRARY_PATH=[DB2instanceDir]/sqllib/lib32:$LD_LIBRARY_PATH
      export SHLIB_PATH=$ORACLE_HOME/lib32:$SHLIB_PATH
    • If you set the environment variable MQSI_LIBPATH64 on your Version 6.1 operating system to use 64-bit execution groups, you can now remove this variable. For example:
      export MQSI_LIBPATH64=[DB2InstanceDir]/sqllib/lib64:$MQSI_LIBPATH64
    • If you want to continue to use 32-bit execution groups, and you use DB2® for your broker database, or interact with DB2 user databases from the message flows within those execution groups, you must set the following environment variable:
      MQSI_LIBPATH32=[DB2InstanceDir]/sqllib/lib32:$MQSI_LIBPATH32
      If your broker will support only 64-bit execution groups, this variable is not required.
  8. Start the Version 6.1 broker.

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.1 Message Broker Toolkit available.

Note:

Before migrating a broker, ensure that you do not have any aggregations in progress. When you migrate a broker to Version 6.1, any live data that is being stored for aggregations in progress will be 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.1 at a different location on the same computer, or to a different computer, complete the following steps:
  1. Install WebSphere Message Broker Version 6.1 either as a new instance on the computer where WebSphere Business Integration Message 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.1 format by following the instructions in Updating your ODBC definitions when migrating.
  3. Create a Version 6.1 broker; 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.

  4. Start the Version 6.1 broker.
  5. 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
  6. 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.1 Message Broker Toolkit to complete this step.
  7. Deploy the message flows and message sets of the Version 5.0 broker to the Version 6.1 broker. Use either the Version 5.0 or Version 6.1 Message Broker Toolkit to complete this step.
  8. Configure any other relevant properties of the Version 5.0 broker on the Version 6.1 broker. For example, you might need to configure properties that you set using the mqsichangeproperties command, or as a result of using certain nodes, such as Publication or SCADA nodes.
  9. Stop the Version 5.0 broker.
  10. Remove the Version 5.0 broker from the workbench.
  11. Redeploy the topology.
  12. Delete the Version 5.0 broker.
When you have migrated the broker, ensure that you have migrated 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, 2007Copyright IBM Corporation 1999, 2007. All Rights Reserved.
This build: July 31, 2007 21:30:35

ah23831_ This topic's URL is: