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

WebSphere Message Broker Version 6.0 can coexist with previous versions and other products. This topic explains the conditions that apply when you use a Version 2.1 broker in a Version 6.0 broker domain.

If you preserve a broker at the Version 2.1 level when migrating 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 2.1 broker can be from either of the following products:

No other components of these products, or any previous releases of these products, can participate in a Version 6.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.

It is not possible to preserve a WebSphere MQ Event Broker broker at the Version 2.1 level when you migrate a WebSphere MQ Event Broker Version 2.1 broker domain to a Version 6.0 broker domain.

There are some conditions for a Version 2.1 broker to participate in a WebSphere Message Broker Version 6.0 broker domain:
Configuration data Can it be deployed to a Version 2.1 broker? Conditions
Message flows Yes See Conditions for deploying a message flow to a Version 2.1 broker.
Message sets Yes See Conditions for deploying a message set to a Version 2.1 broker.
Topology Yes There are no conditions.
Topics Yes A Version 2.1 broker uses only the access control list for the topic and ignores any multicast or quality of protection (QoP) settings for the topic.
Broker properties No Cannot be deployed to a Version 2.1 broker.

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.

Related concepts
Conditions for deploying a message flow to a Version 2.1 broker
Conditions for deploying a message set to a Version 2.1 broker
Coexistence with previous versions and other products
Deployment overview
Topic-based security
Related tasks
Migrating and upgrading
Migrating publish/subscribe applications