This topic is part of a set of related topics that are best read in total and in sequence:
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. |
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 | |
|
All discarded except:
Do your tracing in the normal way for WebSphere Message 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 | |
|
All discarded These attributes concern MQe registry and security, and you configure that on your MQe gateway. |
Listener panel attributes | |
|
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.
Notices |
Trademarks |
Downloads |
Library |
Support |
Feedback
![]() ![]() |
ac34720_ |