The DatabaseInput node
terminals are described in the following table.
Terminal |
Description |
Failure |
The output terminal to which a message is routed
if an error occurs before a message is propagated to the Out terminal. |
Out |
If no errors occur within the input node, a
message received from an external resource is always sent to the Out
terminal first. |
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. |
The following tables describe the node properties that
you can set on a specified tab. The column headed M indicates
whether the property is mandatory (marked in the IBM Integration Toolkit 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).
Description properties:
Property |
M |
C |
Default Value |
Description |
Node Name |
Yes |
No |
Database Input |
The name of the node. |
Short Description |
No |
No |
None |
A brief description of the node. |
Long Description |
No |
No |
None |
Text that describes the purpose of the node in the message
flow. |
Basic properties:
Property |
M |
C |
Default |
Description |
mqsiapplybaroverride command property |
Data Source |
Yes |
Yes |
None |
The ODBC data source name of the
database that contains the tables to which you refer in the ESQL file
that is associated with this message flow (identified by the ESQL Module property). You can specify
only one data source for the node. |
dataSource |
ESQL Module |
Yes |
No |
None |
The name of the DATABASEEVENT module
in the ESQL file that contains the statements to run against the database
and output messages. |
|
Polling properties:
Property |
M |
C |
Default |
Description |
mqsiapplybaroverride command property |
Polling interval (seconds) |
Yes |
Yes |
5 |
The polling interval in seconds. |
waitInterval |
Retry properties:
Property |
M |
C |
Default |
Description |
mqsiapplybaroverride command property |
Retry mechanism |
Yes |
No |
Failure |
How the node handles a flow failure.
Valid options are:
- Failure
- Short retry
- Short and long retry
|
|
Retry threshold |
Yes |
Yes |
0 |
The number of times to try the
flow transaction again when the Retry
mechanism property value is Short
retry or Short and long
retry. |
retryThreshold |
Short retry interval |
No |
Yes |
0 |
The interval, in seconds, between
each retry if Retry threshold property
is not zero. |
shortRetryInterval |
Long retry interval |
No |
Yes |
300 |
The interval between retries, if Retry mechanism property is Short and long retry and the
retry threshold has been exhausted. |
longRetryInterval |
Transactions properties:
Property |
M |
Read Only |
C |
Default |
Description |
mqsiapplybaroverride command property |
Transaction mode |
No |
Yes |
No |
Yes |
The transaction mode of Yes on this input node determines
that the interactions between this node and the database are under
transactional control. It also determines that the rest of the nodes
in the flow are executed under sync point if those downstream nodes
are configured with automatic transaction (that is, if Transaction mode property is Automatic). It is not possible
to make the database interactions non-transactional. |
|
Instances properties:
Property |
M |
C |
Default |
Description |
mqsiapplybaroverride command property |
Additional instances pool |
No |
Yes |
Use
Pool Associated with Message Flow |
The pool from which additional
instances are obtained.
- If you select Use Pool Associated
with Message Flow, additional instances are obtained from
the message flow pool.
- If you select Use Pool Associated
with Node, additional instances are allocated from the additional
instances of the node based on the number specified in the Additional instances property.
|
componentLevel |
Additional instances |
No |
Yes |
0 |
The number of additional instances
that the node can start if the Additional
instances pool property is set to Use Pool Associated with Node. |
additionalInstances |
For a full description of the Instances properties,
see Configurable properties in a BAR file.
The
Monitoring properties of the node are described in the following table.
Property |
M |
C |
Default |
Description |
Events |
No |
No |
None |
Events that you have defined for the node are
displayed on this tab. By default, no monitoring events are defined
on any node in a message flow. Use Add, Edit,
and Delete to create, change or delete monitoring
events for the node; see Configuring monitoring event sources by using monitoring properties for details. You
can enable and disable events that are shown here by selecting or
clearing the Enabled check box.
|