Create a configuration on the broker queue manager to handle the MQe message flows that you have migrated from Version 5.0 to Version 6.0.
This topic describes one in a sequence of migration tasks; complete these tasks in the order shown:
Using message flows that contain MQeInput and MQeOutput nodes in Version 6.0 is deprecated. The behavior that is described here is intended only for when you are deploying from Version 6.0 to a previous version, and to provide a route for migration. Redesign your flows to remove the MQe nodes and replace them with MQ nodes that are configured to your own specifications and coordinated with your MQe gateway configuration.
When you deploy a message flow that contains MQeInput and MQeOutput nodes on WebSphere Message Broker Version 6.0 the nodes are converted to MQInput and MQOutput nodes (as described in Deploying an MQe message flow).
When the MQe nodes are converted into MQ nodes at deployment time, the node properties Queue Manager Name and Queue Name are retained, and you must create a configuration on the broker queue manager to handle these nodes.
For example, suppose you have a message flow like this simplified one that contains MQeInput and MQeOutput nodes:
The following diagram shows this message flow connected directly to MQe devices, as it would be used on a Version 5.0 broker:
When you deploy this message flow to a Version 6.0 broker, create a configuration as shown below:
For help with configuring WebSphere MQ Everyplace, see the documentation supplied with that product.