WebSphere Message Brokers
File: ah23940_
Writer: Kate Hostler

Concept topic

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

Conditions for using migrated resources with previous versions of the Message Broker Toolkit

WebSphere Message Broker Version 6.1 can interoperate with components of previous versions. Conditions apply when you use migrated resources with previous versions of the Message Broker Toolkit.

Start of changeVersion 6.0End of change
Start of change

If you migrate from WebSphere® Message Broker Version 6.0 (or other supported Version 6.0 products), import your resources into your Version 6.1 workspace and rebuild your projects. You do not have to complete any migration tasks; some automatic resource migration for data definitions is performed by the workbench when you save or rebuild message flow projects. See Migrating a flow containing data definitions for further information. No other migrations are required.

End of change
Version 5.0

If you migrate from WebSphere Business Integration Message Broker Version 5.0 (or other supported Version 5.0 products), you must complete migration tasks for the following resources:

All other development and deployment resources, such as message flow files, message set definition files, ESQL files, XML Schema files, and broker archive files, do not have to be migrated.

After you have migrated workbench resources to Version 6.1, your use of these resources in the Version 6.0 and Version 5.0 or Version 5.1 Message Broker Toolkit is restricted:

Development resources

Resources in the Version 5.0, Version 5.1, Version 6.0, and Version 6.1 formats can coexist in the Version 6.1 workspace.

Resources remain in their original format until you save them in the Version 6.1 Message Broker Toolkit. After saving, all resources are stored in the Version 6.1 format.

You can no longer use these saved resources in earlier versions of the Message Broker Toolkit. Therefore you cannot share development resources between the Version 6.1 and previous versions of the Message Broker Toolkit.

If you expect to continue development of these resources, you must retain a Message Broker Toolkit at the version that you require.

Deployment resources
You can deploy from the Version 6.1 Message Broker Toolkit broker archive (bar) files that you created in earlier versions. You can deploy these bar files to brokers that are at previous versions, provided that the development resources referenced in the bar file do not make use of any features that are available only in Version 6.1.

You can create a new Version 6.1 bar file that includes message flows and message dictionaries that were compiled in earlier versions of the workbench.

Start of changeThe following table summarizes the support for the content of bar files. File types that are not supported are ignored by the Configuration Manager. Broker archive files that contain file types only supported by later brokers are rejected by those brokers. For example, a Version 5.0 broker rejects a bar file that contains a .xml file.End of change

Start of change
Deployable by Configuration Manager, accepted by broker? V5.0 V6.0 V6.1
Compiled message flows (.cmf) Yes Yes Yes
Message dictionaries (.dictionary) Yes Yes Yes
XSL style sheets (.xsl, .xslt, .xml) No Yes Yes
Java™ archives (.jar) No Yes Yes
WebSphere TX maps (.mar) No No Yes
XSD archives (.xsdzip) No No Yes
Inbound adapter configuration (.inadapter) No No Yes
Outbound adapter configuration (.outadapter) No No Yes
End of change

The Version 6.1 Message Broker Toolkit can coexist with the Version 6.0, Version 5.0, or Version 5.1 Message Broker Toolkit on the same computer. However, because you cannot share development resources between the Version 6.1 Message Broker Toolkit and previous versions of the Message Broker Toolkit, you might find that it is appropriate to create and maintain a different workspace for the Version 6.1 Message Broker Toolkit.

The Version 5.0 and Version 5.1 Message Broker Toolkit cannot coexist on the same computer. Both versions were available only on Windows®.

Related concepts
Coexistence with previous versions and other products
Related tasks
Migrating a flow containing data definitions
Migrating a user-defined node
Related reference
Migrating message mappings from Version 5.0
mqsimigratemfmaps command
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:42

ah23940_ This topic's URL is: