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.
This topic contains the following sections:
You 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.
The execution group to which the SCADA flows are deployed must be the default execution group. The default execution group can be identified by inspecting the defaultExecutionGroup field in the BIP2201 message at the execution group startup. A value of true denotes the default execution group.
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 contained in the Additional Protocols drawer of the message flow node palette, and is represented in the workbench by the following icon:
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 process the message further, process errors, or send the message to an additional destination.
These values are written in WrittenDestination within the LocalEnvironment tree structure.
If you do not connect either terminal, the LocalEnvironment tree is unchanged.
When you have put an instance of the SCADAOutput node into a message flow, you can configure it. For more information, see Configuring a message flow node. The properties of the node are displayed in the Properties view. To display the properties of the node in the Properties dialog, 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.
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, SCADAOutput | 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. |
The Validation properties of the SCADAOutput node are described in the following table.
Set the validation properties if you want the MRM parser to validate the body of messages against the dictionary that is generated from the message set. If a message is propagated to the Failure terminal of the node, it is not validated.
If a message is propagated to the Failure terminal of the node, it is not validated. For more details, see Validating messages and Validation properties.
Property | M | C | Default | Description |
---|---|---|---|---|
Validate | No | Yes | Inherit | This property controls whether validation takes place. Valid values are None, Content and Value, Content, and Inherit. |
Failure action | No | No | Exception | This property controls what happens if validation fails. You can set this property only if you set Validate to Content or Content and Value. Valid values are User Trace, Local Error Log, Exception, and Exception List. |
Include all value constraints | Yes | No | Selected | You cannot edit this property. If you select this check box, basic value constraint checks are included in Content and Value validation. |
Fix | Yes | No | None | You cannot edit this property. |