This topic contains the following sections:
Use the SCADAOutput node to send a message to a client that connects to the broker using the MQIsdp protocol across the WebSphere MQ Telemetry Transport. You would typically use the Publication node to send output to a SCADA client. The SCADAOutput node lets you write your own Publication node.
If you include a SCADAOutput node in a message flow, also include a SCADAInput node, regardless of the source of the messages, because the SCADAInput node provides the connectivity information that is required by the SCADAOutput node.
When you deploy message flows that contain SCADA nodes to a broker, deploy them to a single execution group, regardless of the number of message flows.
You cannot use the SCADAOutput node to change the transactional characteristics of the message flow. The transactional characteristics that are set by the message flow's input node determine the transactional behavior of the flow.
You cannot use SCADAOutput nodes in message flows that you
deploy to z/OS systems.
If you create a message flow to use as a subflow, you cannot use a standard output node; use an instance of the Output node to create an out terminal for the subflow through which the message can be propagated.
If you do not want your message flow to send messages to a SCADA device, choose another supported output node.
The SCADAOutput node is represented in the workbench by the following icon:
Use the Publication node to publish messages for SCADA devices. Use this node to process the publication messages in a particular way for these devices.
When you have put an instance of the SCADAOutput node into a message flow, you can configure it. To display its properties, either double-click the node, or right-click the node and click Properties. All mandatory properties for which you must enter a value (those that do not have a default value defined) are marked with an asterisk.
Configure the SCADAOutput node as follows:
Connect the In terminal to the node from which messages that are bound for SCADA destinations are routed.
Connect the Out or Failure terminal of this node to another node in this message flow to send the message to an additional destination.
The SCADAOutput node terminals are described in the following table.
Terminal | Description |
---|---|
In | The input terminal that accepts a message for processing by the node. |
Failure | The output terminal to which the message is routed if a failure is detected when the message is put to the output queue. |
Out | The output terminal to which the message is routed if it has been successfully put to the output queue, and if further processing is required within this message flow. |
The following table describes the node properties. The column headed M indicates whether the property is mandatory (marked with an asterisk if you must enter a value when no default is defined); the column headed C indicates whether the property is configurable (you can change the value when you add the message flow to the bar file to deploy it).
The SCADAOutput node Description properties are described in the following table.
Property | M | C | Default | Description |
---|---|---|---|---|
Node name | No | No | The node type, e.g. Input | The name of the node. |
Short Description | No | No | A brief description of the node. | |
Long Description | No | No | Text that describes the purpose of the node in the message flow. |
Notices |
Trademarks |
Downloads |
Library |
Support |
Feedback
![]() ![]() |
ac04630_ |