Resolving migration problems when developing message flows
This topic contains advice for dealing
with some common migration problems that can arise during message flow development.
You do not know whether you need to migrate the Version 2.1 IBM
primitives
- Scenario: You do not know whether you need to migrate the
message flow IBM® primitives.
- Explanation: You do not need to migrate these primitives.
The Version 2.1 primitives are supplied with WebSphere® Event
Broker Version 6.0.
The Version 2.1 export file does not contain IBM primitives.
An error message is issued when you save a message flow that contains
MQe nodes
- Scenario: An error message is issued when you save a message
flow that contains WebSphere MQ Everyplace® nodes.
- Explanation: Do not use message flows that contain MQeInput and MQeOutput nodes in WebSphere Event Broker Version 6.0.
You can continue to use them to deploy from Version 6.0 to
previous versions.
- Solution: Override the error and save the message flow. When you deploy the message flow to a previous version of the
broker, it works as before. When you deploy the message flow to a Version 6.0 broker,
create a suitable configuration to deal with it, as described in Configuring after MQe message flow deployment.