Resolving migration problems when developing message flows
This topic contains advice for dealing
with some common migration problems that can arise when developing message
flows:
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 MQe nodes.
- Explanation: You should not use message flows that contain
MQeInput and MQeOutput nodes in WebSphere Message 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.