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

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

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

To migrate the Version 5.0 Message Brokers Toolkit to Version 6.0, complete the following steps:

  1. Install WebSphere Message Broker Version 6.0 in a different location from WebSphere Business Integration Message Broker Version 5.0.
  2. Migrate any Version 5.0 mappings using the mqsimigratemfmaps command. (There is no migration tool to migrate a mapping that is called from ESQL.)
  3. When you start the Version 6.0 Message Brokers Toolkit for the first time, you are prompted to enter a workspace location. Enter the directory where the Version 5.0 or Version 5.1 Message Brokers Toolkit workspace that you want to migrate is located. In Version 5.0, the default location is <BrokersInstallPath>/eclipse/workspace.
    • Version 5.0 message flows are converted to the Version 6.0 format automatically when you save them for the first time. The Version 5.0 Message Brokers Toolkit cannot read message flows that have been saved in Version 6.0 format.
    • If your message flows use 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 Migration of style sheets and XML files.
    • Version 5.0 message sets are converted to the Version 6.0 format automatically when you save them for the first time. The Version 5.0 Message Brokers Toolkit 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 or Version 5.1, 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 or Version 5.1 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 the Version 6.0 Message Brokers Toolkit. To resolve this, configure access control lists (ACLs) for users who are running the Version 6.0 Message Brokers Toolkit. Follow the instructions in Considering security for the workbench.

When you have migrated the Message Brokers Toolkit, ensure that you have migrated the rest of the components: then see the 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
Client environment
Related tasks
Migrating from WebSphere Business Integration Message Broker Version 5.0 to WebSphere Message Broker Version 6.0
Migrating a user-defined node
Related reference
Installation Guide
mqsimigratemfmaps command