Control-Send
Use the Control-Send node to connect App Connect Enterprise applications to an OPC UA server.
Using Control-Send node in a message flow
The Control-Send node is an input node.
If you have more than one integration nodes for your message flows, you can route this data by using the nodes that are in the Toolkit palette. For example, you can publish the data by using a MQTTPublish node, and then subscribe to the data by using a MQTTSubsribe node.
Terminals
The Control-Send node terminals are described in the following table.
| Terminal | Description |
|---|---|
| Failure | The output terminal to which a message is routed if an error occurs during processing. |
| Out | The output terminal to which a message is routed if the record is written successfully. |
| Catch | The output terminal to which the message is routed if an exception is thrown downstream and caught by this node. Exceptions are caught only if this terminal is attached. |
Properties
The following tables describe the properties for the Control-Send node.
Note: A
mandatoryproperty is marked with an asterisk and a
configurableproperty allows you to edit when you add the message flow to the broker archive (BAR) file.
Basic tab properties
| Field | Description | Control-Send | Mandatory | Configurable |
|---|---|---|---|---|
| Connector Keep Alive Interval | The time interval in milliseconds between connector keep alive messages. | ✓ | Yes | Yes |