WebSphere Message Broker Version 6.0 can coexist with previous versions and other products. This topic explains the conditions that apply when you use migrated resources with previous versions of the Message Brokers Toolkit.
Except for user-defined extensions and mapping files, you do not need to perform any tasks to migrate your Version 5.0 development and deployment resources, such as message flow files, message set definition files, ESQL files, XML Schema files, and broker archive files. You can start using your Version 5.0 resources with WebSphere Message Broker Version 6.0 immediately. After you have migrated Version 5.0 mapping files (.mfmap) to Version 6.0 mapping files (.msgmap) using the mqsimigratemfmaps command, edit them in the Version 6.0 Message Brokers Toolkit. (There is no migration tool to migrate a mapping that is called from ESQL.)
When you migrate from Version 2.1, you must also migrate your message flows, message sets, and user-defined extensions using the mqsimigratemsgflows command and mqsimigratemsgsets command.
However, after you start using your resources in the Version 6.0 Message Brokers Toolkit, there are restrictions on using these same resources again with the Version 5.0 or Version 5.1 Message Brokers Toolkit. These are described in the following sections.
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, it is recommended that the Version 6.0 Message Brokers Toolkit uses a different workspace to either the Version 5.0 or Version 5.1 Message Brokers Toolkit.
The Version 5.0 and Version 5.1 Message Brokers Toolkit cannot coexist on the same computer.
Notices |
Trademarks |
Downloads |
Library |
Support |
Feedback
![]() ![]() |
ah23940_ |