This topic contains the following sections:
The TimeoutControl node receives an input message that contains a timeout request. See Timeout request message for a description of the timeout request message. The node validates the request, stores the message, and propagates the message (unchanged) to the next node in the message flow.
The TimeoutControl node is represented in the workbench by the following icon:
Use a TimeoutControl node and a TimeoutNotification node together in a message flow for an application that requires events to occur at particular times, or at regular intervals.
More than one TimeoutControl node can be paired with a TimeoutNotification node. Timeout requests that are processed by those TimeoutControl nodes are all processed by the same TimeoutNotification node. This happens if the same Unique Identifier is used for the TimeoutNotification node and each of the TimeoutControl nodes.
Look at Timeout Processing sample for more details about how to use the timeout processing nodes.
When you have put an instance of the TimeoutControl node into a message flow, you can configure it.
Right-click the node in the editor view and click Properties. The node's Basic properties are displayed.
Unique Identifier is the only mandatory property. It does not have a default value.
Configure the Basic properties of the node by doing the following:
Now configure the Message properties of the node:
Leave Message Set blank for XML, XMLNS, XMLNSC, JMS, MIME, and BLOB parsers.
Leave Message Type blank for XML, XMLNS, XMLNSC, JMS, IDOC, MIME, and BLOB parsers.
Leave Message Format blank for XML, XMLNS, XMLNSC, JMS, MIME, and BLOB parsers.
When you have completed your configuration, click Apply. This makes the changes to the TimeoutControl node without closing the properties dialog. Click OK to apply the changes and close the properties dialog. Click Cancel to close the dialog and discard all the changes that you have made to the properties.
The TimeoutControl node terminals are described in the following table.
Terminal | Description |
---|---|
In | The input terminal that accepts a message tree for processing (which includes validating the timeout request specified in the message tree at Request Location). and adds it to the control queue. |
Failure | The output terminal to which the input message is propagated if a failure is detected during processing in this node. If this terminal is not connected to another node, error information is passed back to the previous node in the message flow. |
Out | The output terminal to which incoming messages are propagated, unchanged, after successful timeout request processing. If this terminal is not connected to another node, no propagation occurs. If propagation of the message fails, the message is propagated to the Failure terminal. |
The following tables describe the node properties; the column headed M indicates whether the property is mandatory (marked with an asterisk on the properties dialog 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 Basic properties of the TimeoutControl node are described in the following table.
Property | M | C | Default | Description |
---|---|---|---|---|
Unique Identifier | Yes | Yes | None | This is the only mandatory property for the node. Its value must be unique within the broker. The equivalent property of the TimeoutNotification node with which it is paired must have the same value. The maximum length of this identifier is 12 characters. |
Request Location | No | No | None | This property describes where to find the timeout request information. This must be a valid location in the message tree. This is validated at runtime. If no request location is specified, LocalEnvironment.TimeoutRequest is assumed. See Timeout request message for a description of the timeout request message. |
Request Persistence | No | No | Automatic | This property determines whether an incoming timeout request survives a broker or message flow restart. The value of this property can be Automatic, Yes, or No. If the value is Automatic, the Persistence setting in the Properties folder of the incoming message is used. |
The Message properties of the TimeoutControl node are described in the following table.
Property | M | C | Default | Description |
---|---|---|---|---|
Stored Message Location | No | No | None | The location of the part of the request message that you want to store for propagation by the TimeoutNotification node with which this node is paired. |
Message Domain | No | No | None | The domain that will be used to parse the stored timeout request message by the TimeoutNotification node. |
Message Set | No | No | None | The name or identifier of the message set in which the stored timeout request message is defined. |
Message Type | No | No | None | The name of the stored timeout request message. |
Message Format | No | No | None | The name of the physical format of the stored timeout request message. |
The Description properties of the TimeoutControl node are described in the following table.
Property | M | C | Default | Description |
---|---|---|---|---|
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
![]() ![]() |
ac20800_ |