WebSphere Message Brokers
File: ah23930_
Writer: Kate Hostler

Concept topic

This build: July 31, 2007 21:30:41

Coexistence with previous versions and other products

The topics in this section explain the extent to which WebSphere Message Broker Version 6.1 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.1 can coexist with a Version 5.0 product, a Version 6.0 product, or both, on the same computer.

  • You cannot install more than one instance of a Version 5.0 product on a single computer.
  • Component names must be unique on the computer, regardless of version.

When you migrate from a Version 5.0 or Version 6.0 product to WebSphere Message Broker Version 6.1, you do not have to uninstall the Version 5.0 or Version 6.0 product before installing Version 6.1. You can install WebSphere Message Broker Version 6.1 in a different location on the same computer, migrate your components and resources to Version 6.1, and uninstall the Version 5.0 or Version 6.0 product later, when you are sure that you no longer need it.

The following table shows which Version 5.0 and Version 6.0 components can exist on the same computer as Version 6.1 components:

Can the components exist together on the same computer? Version 6.1 Message Broker Toolkit Version 6.1 Configuration Manager Version 6.1 broker Version 6.1 User Name Server
Version 5.0, Version 5.1, or Version 6.0 Message Broker Toolkit Yes Yes Yes Yes
Version 5.0 or Version 6.0 Configuration Manager Yes Yes Yes Yes
Version 5.0 or Version 6.0 broker Yes Yes Yes Yes
Version 5.0 or Version 6.0 User Name Server Yes Yes Yes Yes1
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.1 components with components from previous versions

With some restrictions, all Version 5.0 components can participate in a Version 6.1 broker domain, and all Version 6.1 components can participate in a Version 5.0 broker domain.

Coexistence of Version 6.1 components with components from previous versions means that you do not have to migrate all of your components at the same time. You can migrate those components in stages that are convenient to you.

Because the User Name Server has not changed between versions, you can choose not to migrate this component. You can use a previous version of this component with components that you have migrated to Version 6.1.

The following table shows which Version 5.0 and Version 6.0 components can operate with Version 6.1 components, and shows the restrictions that apply:

Can the components operate together in a domain? Version 6.1 Message Broker Toolkit Version 6.1 Configuration Manager Version 6.1 broker
Version 5.0, Version 5.1, or Version 6.0 Message Broker Toolkit Yes1 Yes Yes2
Version 5.0 or Version 6.0 Configuration Manager Yes (Not applicable) Yes
Version 5.0 or Version 6.0 broker Yes3 Yes Yes
Restrictions:
Start of change
  1. If applicable, you must migrate Version 5.0 maps (.mfmap files) using the mqsimigratemfmaps command. All other resources that you have created using the Version 5.0, Version 5.1, or Version 6.0 toolkit can be accessed unchanged in the Version 6.1 toolkit.

    If you subsequently edit and save resources in the Version 6.1 toolkit, you can continue to access them in the Version 6.0 toolkit but not in the Version 5.0 or Version 5.1 toolkit.

  2. You can use message flow debugging only between like versions (Version 6.1 toolkit and Version 6.1 broker). You cannot debug message flows on a Version 6.1 broker from a Version 6.0 toolkit. However, you can deploy all resources from a Version 6.0 toolkit to a Version 6.1 broker.
  3. All operations controlled through the CMP continue to work with both Version 5.0 and Version 6.0 brokers, including starting, stopping, deleting, and monitoring of deployed resources.

    Most resources that you create in the Version 6.1 toolkit cannot be deployed to Version 5.0 or Version 6.0 brokers; message flows and message sets that you edit and save in the Version 6.1 toolkit you can deploy only to Version 6.1 brokers.

    You can deploy bar files that you have not changed, or for which you have changed only the deployment descriptor or any included XSLT files, from the Version 6.1 toolkit to brokers at previous versions.

    Because of these restrictions, you must retain a Version 5.0, Version 5.1, or Version 6.0 toolkit to maintain brokers that are at Version 5.0 or Version 6.0.

    This change is effected at message flow/message set compilation time, which means that the act of deployment does not change; Configuration Manager Proxy applications will continue to attempt to deploy any bar file to any version of broker.

End of change

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.

Related reference
Supported migration paths
Notices | Trademarks | Downloads | Library | Support | Feedback

Copyright IBM Corporation 1999, 2007Copyright IBM Corporation 1999, 2007. All Rights Reserved.
This build: July 31, 2007 21:30:41

ah23930_ This topic's URL is: