Conditions for a Version 5.0 broker participating in a Version 6.0 broker domain

If you choose to include a Version 5.0 broker in a Version 6.0 broker domain, certain conditions and restrictions apply.

If you preserve a broker at the Version 5.0 level of code during migration to WebSphere® Message Broker Version 6.0, the broker can subsequently participate in the Version 6.0 broker domain and can be managed by the Version 6.0 Configuration Manager. The Version 5.0 broker can be from either of the following products:

You cannot preserve a WebSphere MQ Event Broker broker at the Version 5.0 level of code when you migrate a WebSphere Business Integration Event Broker Version 5.0 broker domain to a Version 6.0 broker domain.

The following conditions apply:

After migration, a Version 5.0 broker can continue to use the same WebSphere MQ queue manager, with the same WebSphere MQ configuration, and with the same release and service level of the WebSphere MQ product code, as it did before migration.

You might need to perform migration tasks for user-defined extensions, mapping files, and data definitions; see Message flow migration notes for details. You can continue to use other resources, such as message flow files, message set definition files, ESQL files, Java™ files, XML Schema files, and broker archive files, without change.

When you have migrated Version 5.0 mapping files (.mfmap) to Version 6.0 mapping files (.msgmap) using the mqsimigratemfmaps command, edit them only with a Version 6.0 Message Brokers Toolkit.

Related concepts
Coexistence with previous versions and other products
Deployment overview
Related tasks
Migrating and upgrading
Migrating publish/subscribe applications
Related reference
Message flow migration notes
Migrating message mappings from Version 5.0
mqsimigratemfmaps command
Notices | Trademarks | Downloads | Library | Support | Feedback

Copyright IBM Corporation 1999, 2009Copyright IBM Corporation 1999, 2009.
Last updated : 2009-01-07 15:21:59

ah13705_