Configuring after MQe message flow deployment

This topic is part of a set of related topics that are best read in total and in sequence:

  1. Migrating a message flow that contains WebSphere MQ Everyplace nodes
  2. Designing MQe connections
  3. Deploying an MQe message flow
  4. 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 (for full details see Deploying an MQe message flow).
Attention: The use of message flows that contain MQeInput and MQeOutput nodes in WebSphere Message Broker 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 the MQe nodes are converted into MQ nodes at deployment time, the queue manager name and queue name attributes are preserved, and you must create a configuration on the broker queue manager to handle them.

For example, suppose you have a message flow like this simplified one that contains MQeInput and MQeOutput nodes:

The diagram shows two nodes, an MQeInput node with Queue Manager Name = A, and Queue Name = B, connected to an MQeOutput node with Queue Manager Name = C, and Queue Name = D.

The following diagram shows this message flow connected directly to MQe devices, as it would be used on a previous version broker:

The diagram shows an MQe Device with queue manager A and queue B, connected to an MQeInput node (on the broker) with the attributes Queue Manager Name A and Queue Name B. Below that on the broker is an MQeOutput node with the attributes Queue Manager Name C and Queue Name D, connected to an MQe Device with queue manager C and queue D.

When you deploy this message flow to a Version 6.0 broker, create a configuration as shown here:

The diagram is described in the following text

Configuration details:
  1. 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.
  2. 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.

Related reference
Migrating a message flow that contains WebSphere MQ Everyplace nodes
Designing MQe connections
Deploying an MQe message flow
MQeInput node
MQeOutput node