WebSphere Business Integration Message Broker Version 5.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 5.0 broker domain.
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.
If you want to preserve a broker at the Version 2.1 level of code during a migration, and the broker is running on a system where you need to install Version 5.0 product code, you must move the Version 2.1 broker to another system before you start the migration.
On z/OS, you can install Version 5.0 product code if there is Version 2.1 product code on the system. This means that you can run a Version 2.1 broker and a Version 5.0 broker on the same system.
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.