DataBase Nodes and Timer Nodes
DataBase Nodes:
Database Node: These database nodes used to interact with a database in the specified ODBC data source.
Database Input node: By using Database Input node to detect events recorded in a database, and to retrieve the data affected by those events.
Database Retrieve node: We can use the Database Retrieve node to ensure that information in a message is up to date.
Database Route node: This node used to route messages using information from a database in conjunction with XPath expressions.
These are specialized form of the Database nodes, and the interaction is restricted to inserting/updating/deleting one or more rows from a table within the database.
We specify what is deleted by defining mapping statements that use the data from the input message to identify the action required.
We can set a property to control whether the update to the database is committed immediately, or deferred until the message flow completes, at which time the update is committed or rolled back, according to the overall completion status of the message flow.
Terminals:
IN: It accepts the message which should be processes by the node.
Failure: If any errors occurs such message will be routed through this terminal to process those Failures. If this terminal was not connected to the next node then no logging or processing of Such failure messages will not do.
Out: The successful output message will be propagated through this terminal.
Out1: The first alternative output terminal to which the transformed message will be routed by a PROPAGATE statement.
Out2: The second alternative output terminal to which the transformed message will be routed by a PROPAGATE statement.
Out3: The third alternative output terminal to which the transformed message will be routed by a PROPAGATE statement.
Out4: The fourth alternative output terminal to which the transformed message will be routed by a PROPAGATE statement.
Timer Nodes:
These nodes enable you to initiate flows in integration node based on time-related events, such as using the Timeout Notification node to run a message flow once an hour.
Timeout Notification node: The Timeout Notification node would be the first node in a Timer-controlled message flow. It has No In terminal.
The purpose of the Timeout Notification node is to act as an alarm clock, initiating a MessageFlow when the timer goes off. You can use it either standalone or you can Pair it with one or more Timeout Control nodes.
A property of this node is its unique identifier (1 to 12 character label).
This identifier must be globally unique within the broker instance that this node is deployed.
As a standalone mode, Generated messages are propagated to the next node according to the fixed interval timer events.
Timeout Control node:The purpose of the Timeout Control node is to dynamically set the characteristics of a Timeout Notification node, Timeout Control node also has a unique identifier property (Referred to as the UID).
The UID of the Timeout Notification node should be the same as the UID of the controlling Timeout Control node.
By using Multiple Timeout Control nodes can control the same Timeout Notification node by specifying the same UID.
Terminals:
In: It accepts the message which should be processes by the node.
Failure: If any errors occurs such message will be routed through this terminal to process those Failures. If this terminal was not connected to the next node then no logging or processing of Such failure messages will not done.
Out: the successful output message will be propagated through this terminal.
Catch: If any exceptions occurred will be detected and caught by the catch terminal.
The Timeout Notification node writes the error to the local error log (or) repeatedly tries to process the request until the problem that caused the exception is resolved.