Coexistence with previous versions and other products

WebSphere® Event Broker Version 6.0 can coexist and interoperate with previous versions and with other products.

This topic contains advice for the following scenarios:

Start of changeIf 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.End of change

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

WebSphere Event Broker Version 6.0 can coexist with either WebSphere MQ Event Broker Version 2.1 or WebSphere Business Integration Event Broker Version 5.0 on the same computer.

  • You cannot install both WebSphere MQ Event Broker Version 2.1 and WebSphere Business Integration Event Broker Version 5.0 on the same computer.
  • You cannot install more than one instance of either WebSphere MQ Event Broker Version 2.1 or WebSphere Business Integration Event Broker Version 5.0 on a single computer.
  • Component names must be unique on the computer, regardless of version.

When you migrate from WebSphere MQ Event Broker Version 2.1 or WebSphere Business Integration Event Broker Version 5.0 to WebSphere Event Broker Version 6.0, you do not need to uninstall the earlier product before you install Version 6.0. You can install WebSphere Event Broker Version 6.0 in a different location on the same computer, migrate your components and resources to Version 6.0, and uninstall WebSphere MQ Event Broker Version 2.1 or WebSphere Business Integration Event Broker Version 5.0 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
Restriction:
  1. On distributed systems, only one User Name Server can exist on a single computer.

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.

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 Start of changeYes3End of change Yes Yes
Version 5.0 Configuration Manager Start of changeYes3End of change (Not applicable) Yes4 Yes
Version 5.0 broker Yes5 Yes Yes Yes
Version 5.0 User Name Server (Not applicable) Yes Yes (Not applicable)
Restrictions:
  1. Use of a Version 2.1 broker in a Version 6.0 domain is subject to some restrictions. For full details, see Conditions for a Version 2.1 broker participating in a Version 6.0 broker domain.
  2. Sharing resources between Message Brokers Toolkit Version 6.0 and Message Brokers Toolkit Version 5.0 or Version 5.1 is subject to some restrictions. For full details, see Conditions for using migrated resources with previous versions of the Message Brokers Toolkit
  3. Start of changeYou cannot use a domain user ID to connect a Version 5.0 or Version 5.1 Message Brokers Toolkit to a Version 6.0 Configuration Manager, nor to connect a Version 6.0 Message Brokers Toolkit to a Version 5.0 Configuration Manager.End of change
  4. If you deploy through a Version 5.0 Configuration Manager, only message flows and dictionaries are extracted from the broker archive (BAR) file.
  5. 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 Event Broker Version 5.0 installation at service level Fix Pack 3 or earlier, apply Fix Pack 5 to the WebSphere Business Integration Event 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 Event Broker brokers. You can also migrate WebSphere MQ Publish/Subscribe brokers to WebSphere Event Broker brokers. Follow the instructions in Migrating publish/subscribe applications.

Notices | Trademarks | Downloads | Library | Support | Feedback

Copyright IBM Corporation 1999, 2009Copyright IBM Corporation 1999, 2009. All Rights Reserved.
Last updated : 2009-01-07 15:40:37

ah23930_