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.1.
This topic describes one in a sequence of migration tasks; complete
these tasks in the order shown:
- Migrating a message flow that contains WebSphere MQ Everyplace nodes
- Designing MQe connections
- Deploying an MQe message flow
- Configuring after MQe message flow deployment (this topic)
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).
Attention: The use of message flows that contain MQeInput and MQeOutput
nodes in Version 6.1 is deprecated. The behavior that is described here
is intended only for when you are deploying from Version 6.1 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
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.1. broker, create a
configuration as shown below:

Configuration details:
- Configure your broker queue manager with the following parameters:
- A local queue named B.
- A remote queue definition R with these attributes:
- Remote Queue Manager = C
- Remote Queue = none (leave blank)
- Transmission Queue = T
This remote queue definition will match all messages that are destined
for any queue on queue manager C and put them to the transmission queue.
- Configure your MQe gateway with the following parameters:
- Provision for accepting messages from an MQe device with queue manager
A and queue B, transforming the format from MQe to MQ, and putting them onto
a bridge queue.
- A bridge queue that puts messages to queue B on the broker queue manager.
- A listener that reads messages from transmission queue T on the broker
queue manager.
- Provision for transforming the message format of the messages on queue
T from MQ to MQe format, and sending them to the MQe device with queue manager
C and queue D.
For
help with configuring WebSphere MQ Everyplace, see the documentation
supplied with that product.