Migrating the Message Brokers Toolkit from WebSphere Business Integration Message Broker Version 5.0 to WebSphere Message Broker Version 6.0

Migrate the Message Brokers Toolkit Version 5.0.

If you are using Message Brokers Toolkit Version 5.1, follow the instructions in this topic, replacing all references to "Message Brokers Toolkit Version 5.0" with "Message Brokers Toolkit Version 5.1".

When you start using your resources in Message Brokers Toolkit Version 6.0, restrictions apply to the use of these same resources again with Message Brokers Toolkit Version 5.0 or Version 5.1. For more information, see Conditions for using migrated resources with previous versions of the Message Brokers Toolkit.

To migrate Message Brokers Toolkit Version 5.0 to Version 6.0:

  1. Install Version 6.0 in a different location from WebSphere Business Integration Message Broker Version 5.0.
  2. Migrate Version 5.0 mappings using the mqsimigratemfmaps command.
  3. When you start the Message Brokers Toolkit Version 6.0 for the first time, you are prompted to enter a workspace location. Enter the directory where the Message Brokers Toolkit Version 5.0 workspace that you want to migrate is located. In Version 5.0, the default location is install_dir/eclipse/workspace.
    • Version 5.0 message flows are converted to the Version 6.0 format automatically when you save them for the first time. Message Brokers Toolkit Version 5.0 cannot read message flows that have been saved in Version 6.0 format.
    • If your message flows use WebSphere MQ Everyplace® (MQe) nodes, follow the instructions in Migrating a message flow that contains WebSphere MQ Everyplace nodes.
    • If your message flows use XML style sheets, follow the instructions in Migrating style sheets and XML files.
    • Start of changeIf you have previously activated validation on a message flow, but have reset the Validation property of the input node to None, you must ensure that the Parse Timing property is set to the default value On Demand before you migrate the message flow.

      Although the Parse Timing property is ignored by a Version 5.0 broker if Validation is set to None, it is not ignored in Version 6.0, and the message flow will fail.

      If Validation is set to None and Parse Timing is not set to the default value, first reset Validation to another value. The Parse Timing property is enabled and you can set it back to the default value On Demand, then reset the Validation property back to None.

      Migrate the message flow with these updated values; it is migrated correctly and with valid settings for Version 6.0.

      End of change
    • Version 5.0 message sets are converted automatically to Version 6.0 format when you save them for the first time. Message Brokers Toolkit Version 5.0 cannot read message sets that have been saved in Version 6.0 format.
  4. Clean and rebuild your workspace.
  5. To migrate user-defined nodes from Version 5.0, import the user-defined node project into the Version 6.0 workbench and rebuild the project. If you are migrating user-defined nodes from Version 5.0, perform the following additional steps:
    1. Modify the <requires> element in the plugin.xml file in the user-defined node project root to match the following example. Ensure that you delete all extraneous entries from the Version 5.0 plugin.xml file so that it matches the following example exactly:
      <requires>
      	<import match="greaterOrEqual" plugin="com.ibm.etools.mft.api" version="6.0.0"/>
      </requires>
    2. Modify the "org.eclipse.help.contexts" extension in the same plugin.xml file to match the following example:
      <extension point="org.eclipse.help.contexts">
      	<contexts file="HelpContexts.xml"/>
      </extension>
    3. Restart the Message Brokers Toolkit using the -clean option.

If you have configured MCA users on the WebSphere MQ channels to the Configuration Manager, you might encounter problems when you try to connect to the migrated Configuration Manager from Message Brokers Toolkit Version 6.0. To resolve these problems, configure access control lists for users who are running the Message Brokers Toolkit Version 6.0. Follow the instructions in Considering security for the workbench.

When you have migrated the Message Brokers Toolkit, migrate the rest of the components:

When you have completed these tasks, see Post-migration tasks for information about tasks that you might want to perform after migration.

Related concepts
Conditions for using migrated resources with previous versions of the Message Brokers Toolkit
Message Brokers Toolkit
Migrating style sheets and XML files
Related tasks
Migrating from WebSphere Business Integration Message Broker Version 5.0 to WebSphere Message Broker Version 6.0
Migrating a user-defined node from Version 5.0 or Version 5.1
Related reference
Installation Guide
Migrating a message flow that contains WebSphere MQ Everyplace nodes
mqsimigratemfmaps command
Notices | Trademarks | Downloads | Library | Support | Feedback

Copyright IBM Corporation 1999, 2009Copyright IBM Corporation 1999, 2009.
Last updated : 2009-01-07 15:22:09

ah23850_