Coexistence with previous versions and other products

The topics in this section explain the extent to which WebSphere Message Broker Version 6.0 can coexist with previous versions and other products. This topic contains advice for the following scenarios:

Coexistence with previous versions of the product installed on the same computer

WebSphere Message Broker Version 6.0 can coexist with either a Version 2.1 or a Version 5.0 product on the same computer.

You cannot install both a Version 2.1 and a Version 5.0 product on the same computer, and you cannot install several instances of either Version 2.1 or Version 5.0 products on a single 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 Version 2.1 or Version 5.0 product before installing 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.

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
Restriction:
  1. On distributed systems, only one User Name Server can exist on a single computer. If you need another User Name Server, start one on a remote system.

Coexistence of Version 6.0 components with components from previous versions

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 Version 2.1 broker is the only Version 2.1 component that can take part in a Version 6.0 broker domain.

Coexistence of Version 6.0 components with components from previous versions means that you do not have to migrate all of your components at the same time. Instead migrate those components that can coexist with Version 6.0 components in stages.

The following table shows which Version 2.1 and Version 5.0 components can operate with Version 6.0 components, and shows when restrictions 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 Yes3 Yes Yes
Version 5.0 Configuration Manager Yes (Not applicable) Yes Yes
Version 5.0 broker Yes4 Yes Yes Yes
Version 5.0 User Name Server (Not applicable) Yes Yes (Not applicable)
Restrictions:
  1. There are restrictions on how a Version 2.1 broker can participate in a Version 6.0 domain. For full details, see Conditions for a Version 2.1 broker participating in a Version 6.0 broker domain.
  2. There are restrictions on sharing resources between Message Brokers Toolkit Version 6.0 and Message Brokers Toolkit Version 5.0 or Version 5.1. For full details, see Conditions for using migrated resources with previous versions of the Message Brokers Toolkit
  3. Start of changeYou cannot use a Version 5.0 or Version 5.1 Message Brokers Toolkit to connect to a Version 6.0 Configuration Manager with a domain user ID.End of change
  4. If you want to use a Version 6.0 Message Brokers Toolkit and a Version 5.0 Configuration Manager to deploy to a Version 5.0 broker that is part of a WebSphere Business Integration Message Broker Version 5.0 installation at service level Fix Pack 3 or earlier, apply Fix Pack 5 to the WebSphere Business Integration Message Broker Version 5.0 installation of which the Version 5.0 Configuration Manager is part.

Coexistence with other products

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.