This topic summarizes the changes, and the subsequent
topics describe the situation in more detail:
- Migrating an MQe message flow (this topic)
- Designing MQe connections
- Deploying an MQe message flow
- Configuring after MQe message flow deployment
- Version 5.0 configuration
- You can use either of these connection configurations:
- MQe device client <--connects to --> MQe gateway <--connects
to --> broker (using MQInput and MQOutput nodes)
- MQe device client <--connects to --> broker (using MQeInput and MQeOutput nodes)
- The MQe code level in the MQe nodes in the broker is at a fixed
version, and you cannot update it independently.
- Version 6.0 configuration
- 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.
- You must install WebSphere MQ Everyplace separately.
The WebSphere MQ Everyplace code is now all contained
in that separate installation and it can be upgraded independently
to newer versions.
- The MQeInput and MQeOutput nodes are in the workbench for compatibility only, and
are not implemented within the broker component.
- You can use only this connection configuration:
- MQe device client <--connects to --> MQe gateway <--connects
to --> broker (using MQInput and MQOutput nodes)
- You can migrate your existing MQe message flows unchanged to Version 6.0, but you must
configure the MQe gateway according to the modified implementation:
- The BAR file generated is identical to that created in Version 5.0.
- When you deploy to a Version 5.0 broker,
the flow works just as before.
- When you deploy to a Version 6.0 broker, the broker interprets the BAR file
differently, and changes the MQeInput and MQeOutput nodes internally
into MQInput and MQOutput nodes. The broker
also ignores some MQe node properties, and reinterprets others.
- 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, and then redeploy
the modified flows. You can use the Message Brokers Toolkit at either Version 6.0, or at Version 5.0 (or Version 5.1) to perform the redeployment.
If you want to use WebSphere MQ Everyplace connections
with 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.