WebSphere MQ Telemetry Transport is a lightweight publish/subscribe protocol flowing over TCP/IP for remote sensors and control devices through low bandwidth communications.
This protocol is used by specialized applications on small footprint devices that require a low bandwidth communication, typically for remote data acquisition and process control. A typical system might comprise several hundred client devices communicating with a single WebSphere Business Integration Message Broker, where each client is identified by a unique ID.
WebSphere Business Integration Message Broker uses the SCADAInput node to receive messages from WebSphere MQ Telemetry Transport client applications.
SCADAInput nodes are available on all platforms except z/OS.
WebSphere MQ Telemetry Transport messages arrive and leave using a port rather than a queue. You start and stop a WebSphere MQ Telemetry Transport listener using a publish message with a specific topic. You can do this for every port, or for a single port identified in the message.
Output is typically returned to the client application using a Publication node which embeds a SCADAOutput node. The Publication node filters and sends output from a message flow to subscribers who have registered an interest in a particular set of topics. If an application is using WebSphere MQ, the Publication node puts the message to the WebSphere MQ queue on the queue manager. For WebSphere MQ Telemetry Transport applications, the embedded SCADAOutput node routes the message to a subscribing WebSphere MQ Telemetry Transport client using TCP/IP.
It is unlikely that you will use the SCADAOutput node directly, unless you write your own publication node for advanced applications.
SCADAInput and SCADAOutput nodes must reside within a single execution group within a broker. If an execution group contains a message flow which has a SCADAOutput node embedded within a Publication, the execution group must also contain a message flow with a SCADAInput node.
Unlike WebSphere MQ and WebSphere MQ Everyplace, WebSphere MQ Telemetry Transport does not provide any security, although you can encrypt data, if required.
You can specify a maximum Quality of Service (QoS) in a WebSphere MQ Telemetry Transport subscription message. QoS is similar to persistence in WebSphere MQ. There are three levels of QoS:
For further information about QoS see Quality of Service levels and flows
Related concepts
Publish/Subscribe
Related tasks
Deciding which nodes to use
Related reference
SCADAInput node
Publication node
SCADAOutput node
Notices |
Trademarks |
Downloads |
Library |
Support |
Feedback
![]() ![]() |
ac00470_ |