Message flow node terminals

A terminal is the point at which one node in a message flow is connected to another node.

Use terminals to control the route that a message takes, depending on whether the operation that is performed by a node on that message is successful. Terminals are wired to other node terminals by using message flow node connections to indicate the flow of control.

Every built-in node has a number of terminals to which you can connect other nodes. Input nodes (for example, MQInput) do not have input terminals; all other nodes have at least one input terminal through which to receive messages to be processed.

Most built-in nodes have failure terminals that you can use to manage the handling of errors in the message flow. Use the failure terminal to handle errors within the node itself.

Most built-in nodes have a catch terminal. These nodes are typically at the start of a transaction, where an uncaught exception would cause a rollback. In these nodes, the catch terminal behaves as though a TryCatch node were wired directly to the Out terminal. Use the catch terminal to handle any exceptions that are thrown beyond the message flow node.

Most nodes have output terminals through which the message can flow to a subsequent node.

If you have any user-defined nodes, these might also have terminals that you can connect to other built-in or user-defined node terminals.

Dynamic terminals are terminals that you can add to certain nodes after you have added them to a message flow in the Message Flow editor. For example, you can add dynamic output terminals to the Route, and DatabaseRoute nodes, or you can add dynamic input terminals to the Collector node. You can also delete and rename dynamic terminals. If a node has five or more terminals, they are displayed in a group. For example, the following example shows a node with more than four output terminals.