Migrating a message flow that contains WebSphere MQ Everyplace nodes

The support for connecting WebSphere MQ Everyplace device clients to WebSphere Message Broker has changed in WebSphere Message Broker Version 6.0.

This topic summarizes the changes, and the subsequent topics describe the situation in more detail:

  1. Migrating an MQe message flow (this topic)
  2. Designing MQe connections
  3. Deploying an MQe message flow
  4. Configuring after MQe message flow deployment
Previous versions
  • You can use either of these connection configurations:
    1. MQe device client <--connects to--> MQe gateway <--connects to--> Broker (using MQInput and MQOutput nodes)
    2. MQe device client <--connects to--> Broker (using MQeInput and MQeOutput nodes)
  • The MQe code level contained within the MQe nodes in the broker is at a fixed version, and you can not update it independently.
Version 6.0
  • The MQeInput and MQeOutput nodes do not exist (the broker has no MQe code within it).
  • You can use only this connection configuration:
    1. MQe device client <--connects to--> MQe gateway <--connects to--> Broker (using MQInput and MQOutput nodes)
  • You must install WebSphere MQ Everyplace separately. The MQe code is now all contained in that separate installation and it can be upgraded independently to newer versions.
  • You can still import or create a message flow with MQe nodes in it, and save it and deploy it to a broker:
    • The bar files generated will be exactly the same as before.
    • When you deploy to a previous version broker, the flow will work just as before.
    • When you deploy to a Version 6.0 broker, the broker run time interprets the bar file differently, changing the MQeInput and MQeOutput nodes into MQInput and MQOutput nodes, ignoring some MQe node attributes and reinterpreting others.
    This way, you can migrate your existing MQe message flows unchanged to WebSphere Message Broker Version 6.0 (you must configure the MQe gateway according to the reinterpreted attributes).
    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.
  • If you are using MQeOutput nodes with the Destination Mode property set to Destination List, when you migrate your MQe flows to a Version 6.0 broker, change the Destination Mode property to Reply to Queue then redeploy the modified flows. You can use either the Version 6.0 or previous version of the Message Brokers Toolkit to perform the redeployment.

If you want to use MQe connections with WebSphere Message Broker Version 6.0 see the subsequent topics for more details, starting with Designing MQe connections.

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

Related reference
Designing MQe connections
Deploying an MQe message flow
Configuring after MQe message flow deployment
MQeInput node
MQeOutput node