Conditions for using migrated resources with previous versions of the Message Brokers Toolkit

WebSphere® Message Broker Version 6.0 can interoperate with components of previous versions. Conditions apply when you use migrated development and deployed resources with previous versions of the Message Brokers Toolkit.

Version 2.1

If you migrate from WebSphere MQ Integrator Broker Version 2.1 (or other supported Version 2.1 products), migrate the following resources:

  • Message flows: use the mqsimigratemsgflows command.
  • User-defined extensions: use the mqsimigratemsgflows command.
  • Message sets: use the mqsimigratemsgsets command.

For detailed instructions, see Migrating message flows from Version 2.1 and Migrating Message Sets from Version 2.1.

Version 5.0

If you migrate from WebSphere Business Integration Message Broker Version 5.0 (or other supported Version 5.0 products), migrate the following resources:

You do not have to migrate any other development or deployment resources, such as message flow files, message set definition files, ESQL files, XML Schema files, and broker archive files.

Restrictions after migration

After you have migrated workbench resources to Version 6.0, your use of these resources in the Version 5.0 or Version 5.1 Message Brokers Toolkit is restricted.

Development resources

Resources in Version 5.0, 5.1, and 6.0 formats can coexist in the Version 6.0 workspace.

Resources remain in their original format until you save them in the Version 6.0 Message Brokers Toolkit. After saving, all resources are stored in the Version 6.0 format.

You can no longer use these saved resources in earlier versions of the Message Brokers Toolkit. Therefore you cannot share development resources between the Version 6.0 and previous versions of the Message Brokers Toolkit.

If you expect to continue development of these resources, you must retain a Message Brokers Toolkit at the version that you require.

Deployment resources
You can deploy from the Version 6.0 Message Brokers Toolkit broker archive (BAR) files that you created in earlier versions. You can deploy these BAR files to brokers that are at previous versions, provided that the development resources referenced in the BAR file do not use any features that are available only in Version 6.0.

You can create a new Version 6.0 BAR file that includes message flows and message dictionaries that were compiled in earlier versions of the workbench.

The Version 6.0 Message Brokers Toolkit can coexist with either the Version 5.0 or Version 5.1 Message Brokers Toolkit on the same computer. However, because you cannot share development resources between the Version 6.0 Message Brokers Toolkit and previous versions of the Message Brokers Toolkit, you might find that it is appropriate to create and maintain a different workspace for the Version 6.0 Message Brokers Toolkit.

The Version 5.0 and Version 5.1 Message Brokers Toolkit cannot coexist on the same computer. Both versions are available only on Windows®.

Related concepts
Coexistence with previous versions and other products
Related tasks
Migrating a user-defined node from Version 5.0 or Version 5.1
Related reference
Migrating message mappings from Version 5.0
mqsimigratemfmaps command
mqsimigratemsgflows command
mqsimigratemsgsets command
Notices | Trademarks | Downloads | Library | Support | Feedback

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

ah23940_