Deploying an MQe message flow

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 (this topic)
  4. Configuring after MQe message flow deployment
The following table describes the deployment possibilities of a message flow that contains MQeInput and MQeOutput nodes.
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.
Deploy from Deploy to Result
Previous version Previous version Works as before
Previous version Version 6.0 Not possible - instead you must import your old message flow into your Version 6.0 Message Brokers Toolkit and then deploy from there.1
Version 6.0 Previous version Works as before.2
Version 6.0 Version 6.0 Works when you set up an appropriately configured MQe gateway. When the broker receives the bar file, the MQeInput and MQeOutput nodes in the message flow are converted into MQInput and MQOutput nodes that are re-configured as described below.
Notes:
  1. When you save the flow in Version 6.0 you see an error message saying that the use of MQe nodes is now deprecated. You can override the error and continue to save and deploy.
  2. The bar files generated by Version 6.0 contain XML that is exactly the same as previous versions.

The following list describes what happens to all the MQe node attributes when the node is converted into an MQ node. (For a summary of the key attributes, see the next topic in this set, Configuring after MQe message flow deployment).

MQeInput and MQeOutput node properties panels Converted MQ node properties
General panel attributes
  • Trace
  • Trace Filename
  • Use Config File
  • Config Filename
  • Queue Manager Name
  • Queue Name
All discarded except:
  • Queue Manager Name
  • Queue Name

Do your tracing in the normal way for WebSphere Event Broker, as described in the Using trace topic. When this flow is traced, the MQ nodes are seen, not the MQe nodes in the message flow in the deployed bar file that have been converted.

Registry panel attributes
  • Registry type
  • Directory
  • PIN
  • Certificate Request PIN
  • Keyring Password
  • Certificate Host
  • Certificate Port

All discarded

These attributes concern MQe registry and security, and you configure that on your MQe gateway.

Listener panel attributes
  • Listener Type
  • Host Name
  • Port
  • Time Interval

All discarded

You configure these attributes on your MQe gateway and your broker queue manager.

To use such a deployment, create a suitable configuration on the broker queue manager for the converted nodes to work, as described in the next topic, Configuring after MQe message flow deployment.

For help with configuring WebSphere MQ Everyplace, see the documentation supplied with that product.

Related tasks
Using trace
Related reference
Migrating a message flow that contains WebSphere MQ Everyplace nodes
Designing MQe connections
Configuring after MQe message flow deployment
MQeInput node
MQeOutput node