See information about the latest product version
Changes to nodes in WebSphere Message Broker Version 8.0
There were changes to the nodes provided in Version 7.0 of the product. These changes included removal of the SCADA and RealTime nodes. If you are migrating from Version 6.1 to Version 8.0, these changes might affect flows that you migrate.
The Publication node has two additional terminals, Out and No Match; see Publication node for further information.
WebSphere® MQ Telemetry Transport is supported from WebSphere MQ; see the WebSphere MQ Telemetry Transport documentation for further information.
- Real-timeInput node
- Flows containing Real-timeInput nodes that have been migrated to WebSphere Message Broker Version 8.0 will not start until these nodes have been removed from the flow and the flow has been redeployed.
- Real-timeOptimizedFlow node
- Flows containing Real-timeOptimizedFlow nodes
that have been migrated to WebSphere Message
Broker Version
8.0 will
not start until these nodes have been removed from the flow and the
flow has been redeployed.
If your message flows contain only a Real-timeOptimizedFlow node, no WebSphere Message Broker flow is required after you have migrated to WebSphere Message Broker Version 8.0.
- SCADAInput node
- Flows containing SCADAInput nodes that have been migrated to WebSphere Message Broker Version 8.0 will not start until these nodes have been removed from the flow and the flow has been redeployed.
- SCADAOutput node
- Flows containing SCADAOutput nodes that have been migrated to WebSphere Message Broker Version 8.0 will fail if processing reaches the node and you receive a BIP warning message.
- MQeInput
- The MQeInput node has been removed. This node was deprecated in an earlier version of the product.
- MQeOutput
- The MQeOutput node has been removed. This node was deprecated in an earlier version of the product.
Contact your account representative for more information about support for WebSphere MQ Real-time Transport and WebSphere MQ Telemetry Transport.
Additionally, although the MQOptimizedFlow node still works, this node is redundant.