The properties of the links connecting this node are described.
Property | Description |
---|---|
Runtime Tab | |
Sub Service Name | Enter a unique identifier for each asynchronous receiver. |
Initial Threads | Enter the number of threads that can process messages simultaneously.
This value must be a minimum of 1. Based on your throughput requirements,
you can increase the number of threads. The number of threads set in the configuration can be increased for a Sub Service Name dynamically from the System Management Console. |
Selector | Enter the message to be processed, using the Header Name and
Header values from the "Database
Sender Configuration Properties" table, implemented as an SQL
where clause in the of form USER_REFERENCE='<name>=value' In addition to the Header Name/Value, EOF messages get appended with MessageType=EOF in the USER_REFERENCE column. If you are using USER_REFERENCE as the selector, you need to modify the Selector criteria to include MessageType=EOF as well. Note: When specifying a selector, use only single quotes.
Note: If you configure two services to read from
the same table (and select the same records), the results may be unpredictable.
For a database, the columns that can be used are FLOW_NAME, SUB_FLOW_NAME,
USER_REFERENCE, from the YFS_EXPORT/IMPORT table.
|
Table Name | Select the table you want the message to be read from. Valid
values are YFS_IMPORT and YFS_EXPORT. Must match the table specified in the receiver link. |
Polling Frequency (seconds) | Enter the frequency in seconds to poll for messages from the
database table. Defaults to 600 seconds (10 minutes). A separate thread manages all exceptions resolved from the exception console and polls the database every 60 seconds (1 minute). The frequency of polling for exception processing cannot be modified. |
Service to Execute on EOF Message | Required if the message contains an End Of File (EOF) message
ID. Choose the Search icon to select the service to be invoked when an EOF message is received. Once the EOF message is received, the framework waits for a few minutes (configurable in the customer_overrides.properties file) before executing this service. For more information see, Enabling EOF messages in the application platform framework. |
Root Node Name of EOF Message | This need to be specified only if the message contains an EOF
message ID. Enter your custom root node name for the EOF message. By default the EOF message has a root node name as "EOF". For more information see, Enabling EOF messages in the application platform framework |
Server Tab | |
Server Name | Required. Name of the integration server instance which actually
executes the service. For more information about creating a new server, see Adding a New Server. |
Exception Tabs | See Table 1 for the receiver link exception handling properties. |
The following are the Database node's connection properties:
Connection | Node Connection Rules |
---|---|
Can be the first node after the start node | Yes, for services invoked both in a synchronous or asynchronous mode |
Can be placed before |
|
Can be placed after |
|
Passes data unchanged | Transport nodes do not modify data |