WebSphere® Event 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.
If you migrate from WebSphere MQ Integrator Broker Version 2.1 (or other supported Version 2.1 products), migrate the following resources:
For detailed instructions, see Migrating message flows from Version 2.1.
You do not have to migrate any resources to Version 6.0.
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.
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.
You can create a new Version 6.0 BAR file that includes message flows 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®.