Read the concept topic about conditions for a Version 5.0 broker participating in a Version 6.0 broker domain.
You can migrate the message flows that you have created in your Version 2.1 product (WebSphere MQ Event Broker, WebSphere MQ Integrator Broker, or WebSphere MQ Integrator) and use them in WebSphere Message Broker Version 6.0.
If you are migrating from WebSphere MQ Event Broker Version 2.1, all information in this topic that refers to user-defined plug-ins and ESQL does not apply: these facilities are not available on WebSphere MQ Event Broker Version 2.1.
If you have migrated from WebSphere MQ Integrator Broker Version 2.1, you might have written message flows that handle XML messages that use XML namespaces. In Version 2.1, such XML messages are parsed in a different way to that used by WebSphere Message Broker Version 6.0. While such message flows will continue to work correctly when hosted by Version 6.0, it is better to upgrade them to become namespace aware by following the steps in Making a message flow namespace aware.
You might want to change the message flows that you migrate to take advantage of the new nodes and features that are available in Version 6.0. For example, you might want to replace a user-defined node that receives web services requests with the built-in HTTPInput node.
For more information about changes in this release, see What's new in Version 6.0?.
You can migrate more than one message flow at one time if you want them to be defined in the same message flow project. You must migrate subflows and user-defined nodes with the message flows in which they are included to ensure consistent references.
If you have defined more than one message flow with the same name, or the message flow has been exported into more than one export file, the migration task overwrites any existing message flow with the next flow that it finds of the same name without warning. Therefore be careful to avoid conflicts, and to ensure that the most recent version of a multiply-defined message flow is the last one to be migrated.
If you have multiple versions of the same message flow, which you use as a subflow in other flows in the same migration directory, the results of the import are unpredictable.
To migrate a message flow:
Notices |
Trademarks |
Downloads |
Library |
Support |
Feedback
![]() ![]() |
ac02355_ |