WebSphere® Message Broker Version 6.0 can coexist and interoperate with previous versions and with other products.
If you have configured your broker domain such that two or more brokers share a database schema, you must migrate all those brokers to the new version or product at the same time. Brokers that you have created at different versions, or for different products, cannot share a database schema.
WebSphere Message Broker Version 6.0 can coexist with either a Version 2.1 or a Version 5.0 product on the same computer.
When you migrate from a Version 2.1 or Version 5.0 product to WebSphere Message Broker Version 6.0, you do not need to uninstall the earlier product before you install Version 6.0. You can install WebSphere Message Broker Version 6.0 in a different location on the same computer, migrate your components and resources to Version 6.0, and uninstall the Version 2.1 or Version 5.0 product later, when you are sure that you no longer need it.
If you install more than one version on a single computer, and you create multiple components, check that sufficient memory and disk space is available.
The following table shows which Version 2.1 and Version 5.0 components can exist on the same computer as Version 6.0 components:
Can the components exist together on the same computer? | Version 6.0 Message Brokers Toolkit | Version 6.0 Configuration Manager | Version 6.0 broker | Version 6.0 User Name Server |
---|---|---|---|---|
Version 2.1 Control Center | Yes | Yes | Yes | Yes |
Version 2.1 Configuration Manager | Yes | Yes | Yes | Yes |
Version 2.1 broker | Yes | Yes | Yes | Yes |
Version 2.1 User Name Server | Yes | Yes | Yes | Yes1 |
Version 5.0 or Version 5.1 Message Brokers Toolkit | Yes | Yes | Yes | Yes |
Version 5.0 Configuration Manager | Yes | Yes | Yes | Yes |
Version 5.0 broker | Yes | Yes | Yes | Yes |
Version 5.0 User Name Server | Yes | Yes | Yes | Yes |
With some restrictions, all Version 5.0 components can participate in a Version 6.0 broker domain, and all Version 6.0 components can participate in a Version 5.0 broker domain.
A broker is the only Version 2.1 component that can take part in a Version 6.0 broker domain. WebSphere MQ Event Broker Version 2.1 components cannot operate with Version 6.0 components at all.
Because Version 6.0 components can coexist with components from Version 5.0, you do not need to migrate all of your components at the same time. You can migrate those components that can coexist with Version 6.0 components in stages that are convenient to you.
The User Name Server has not changed between Version 5.0 and Version 6.0, therefore you can choose not to migrate this component. You can use a Version 5.0 User Name Server with components that you have migrated to Version 6.0.
The following table shows which Version 2.1 and Version 5.0 components can operate with Version 6.0 components, and shows the restrictions that apply.
Can the components operate together in a domain? | Version 6.0 Message Brokers Toolkit | Version 6.0 Configuration Manager | Version 6.0 broker | Version 6.0 User Name Server |
---|---|---|---|---|
Version 2.1 Control Center | No | No | No | No |
Version 2.1 Configuration Manager | No | (Not applicable) | No | No |
Version 2.1 broker | Yes1 | Yes1 | Yes1 | Yes1 |
Version 2.1 User Name Server | (Not applicable) | No | No | (Not applicable) |
Version 5.0 or Version 5.1 Message Brokers Toolkit | Yes2 | ![]() ![]() |
Yes | Yes |
Version 5.0 Configuration Manager | ![]() ![]() |
(Not applicable) | Yes4 | Yes |
Version 5.0 broker | Yes5 | Yes | Yes | Yes |
Version 5.0 User Name Server | (Not applicable) | Yes | Yes | (Not applicable) |
You can create and operate a heterogeneous network of WebSphere MQ Publish/Subscribe brokers and WebSphere Message Broker brokers. You can also migrate WebSphere MQ Publish/Subscribe brokers to WebSphere Message Broker brokers. Follow the instructions in Migrating publish/subscribe applications.
You cannot install WebSphere Event Broker and WebSphere Message Broker as separate products on the same computer. WebSphere Message Broker, however, can perform all of the functions of WebSphere Event Broker.