This topic contains the following sections:
The TimeoutNotification node is an input node that can be used in two ways:
The TimeoutNotification node processes timeout request messages that are sent by the TimeoutControl nodes with which it is paired, and propagates copies of the messages (or selected fragments of the messages) to the next node in the message flow.
Generated messages are propagated to the next node in the message flow at time intervals that are specified in the configuration of this node.
The TimeoutNotification 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 a particular time, or at regular intervals; for example, when you want a batch job to run every day at midnight, or you want information about currency exchange rates to be sent to banks at hourly intervals.
More than one TimeoutControl node can be used with a TimeoutNotification node. Timeout requests that are processed by those TimeoutControl nodes are all processed by the same TimeoutNotification node if the same Unique Identifier is used for the TimeoutNotification node and each of the TimeoutControl nodes.
When a TimeoutNotification node is started as a result of the broker starting, or by the message flow that contains the node starting, it scans its internal timeout store and purges any non-persistent timeout requests. Notifications are issued for any persistent timeout requests that are now past and that have the IgnoreMissed property set to False.
CREATE NEXTSIBLING OF OutputRoot.Properties DOMAIN 'MQMD'; SET OutputRoot.MQMD.StrucId = MQMD_STRUC_ID; SET OutputRoot.MQMD.Version = MQMD_CURRENT_VERSION; SET OutputRoot.MQMD.Format = 'XML';
Look at Timeout Processing sample for more details about how to use the timeout processing nodes.
When you have put an instance of the TimeoutNotification 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.
For more details, refer to Validating messages and Validation properties for messages in the MRM domain.
The terminals of the TimeoutNotification node are described in the following table.
Terminal | Description |
---|---|
Failure | The output terminal to which the message is propagated if a failure is detected during processing in this node. Nodes can be connected to this terminal to process these failures. If this terminal is not connected to another node, messages are not propagated and no logging or safe storage of data occurs. |
Out | The output terminal to which messages are propagated
after timeouts expire.
|
Catch | The output terminal to which the message is propagated
if an exception is thrown downstream. If this terminal is not connected to
another node, the following events occur:
|
The following tables describe 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 Description properties of the TimeoutNotification node are described in the following table.
Property | M | C | Default | Description |
---|---|---|---|---|
Node name | No | No | The node type | 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 Basic properties of the TimeoutNotification node are described in the following table.
Property | M | C | Default | Description |
---|---|---|---|---|
Unique Identifier | Yes | Yes | None | A value that is unique within the broker and that is the same as the identifier that is specified for the TimeoutControl nodes with which this node is paired (if there are any). The maximum length of this identifier is 12 characters. |
Transaction Mode | No | No | 'Yes' | The transaction mode for the node. Valid values are Yes, No, and Automatic. If the transaction mode is Automatic, a transaction is based on the persistence of the stored messages, which is controlled by the Request Persistence property of the TimeoutControl node with which it is paired. |
Operation Mode | No | No | 'Automatic' | This property indicates whether this node is paired with any paired TimeoutControl nodes. Valid values are Automatic and Controlled. |
Timeout Interval | No | No | 1 | The interval (in seconds) between timeout requests. This property is relevant only if Operation Mode is set to Automatic. |
The properties of the Parser Options for the TimeoutNotification node are described in the following table.
Property | M | C | Default | Description |
---|---|---|---|---|
Parse Timing | Yes | No | On Demand | This property controls when an input message is parsed.
Valid values are On Demand, Immediate, and Complete. Refer to Parsing on demand for a full description of this property. |
Use MQRFH2C Compact Parser for MQRFH2 Domain | No | No | Cleared | This property controls whether the MQRFH2C Compact Parser, instead of the MQRFH2 parser, is used for MQRFH2 headers. |
Use XMLNSC Compact Parser for XMLNS Domain | Yes | No | Cleared | This property controls whether the XMLNSC Compact Parser is used for messages in the XMLNS Domain. If you set this property, the message data appears under XMLNSC in nodes that are connected to the output terminal when the input RFH2 header or default properties Domain is XMLNS. |
Retain Mixed Content | Yes | No | None | This property controls whether the XMLNSC parser creates elements in the message tree when it encounters mixed text in an input message. If you select the check box, elements are created for mixed text. If you clear the check box, mixed text is ignored and no elements are created. |
Retain Comments | Yes | No | None | This property controls whether the XMLNSC parser creates elements in the message tree when it encounters comments in an input message. If you select the check box, elements are created for comments. If you clear the check box, comments are ignored and no elements are created. |
Retain Processing Instructions | Yes | No | None | This property controls whether the XMLNSC parser creates elements in the message tree when it encounters processing instructions in an input message. If you select the check box, elements are created for processing instructions. If you clear the check box, processing instructions are ignored and no elements are created. |
The Validation properties of the TimeoutNotification node are described in the following table.
Refer to Validation properties for messages in the MRM domain for a full description of these properties.Property | M | C | Default | Description |
---|---|---|---|---|
Validate | Yes | Yes | None | This property controls whether validation takes place. Valid values are None, Content, and Content And Value. |
Failure Action | Yes | 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. |
Notices |
Trademarks |
Downloads |
Library |
Support |
Feedback
![]() ![]() |
ac20802_ |