Coexistence with previous releases and other products

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

No other components of these products, or any previous releases of these products, can participate in a Version 5.0 broker domain. This means that you must migrate all your Version 2.1 Control Center, Configuration Manager, and User Name Server components at the same time, but you can migrate your Version 2.1 brokers in stages.

The conditions under which a Version 2.1 broker can participate in a WebSphere Business Integration Message Broker Version 5.0 broker domain are as follows:

After migration, a Version 2.1 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.

Note the following additional coexistence guidelines:
Related concepts
Message flow application deployment
Conditions for deploying a message flow to a Version 2.1 broker
Conditions for deploying a message set to a Version 2.1 broker
Topic-based security
Related tasks
Migrating and upgrading
Migrating publish/subscribe applications