DCS 6.2 database receiver

The properties of the links connecting this node are described.

Configuration properties

Table 1. DCS 6.2 database receiver configuration properties
Property Description
Runtime Tab
Sub Service Name Enter a unique identifier for each asynchronous receiver.
Node Enter the ship node associated with the service.
Selector Optional. This field can be used for selecting a specific remote host ID.
Note: When specifying a selector, use only single quotes.
Table Type Select either UPLD or DNLD for the upload or download interface tables. The interface table names are derived from this and the value entered in the Node field. The default value for the receiver is DNLD.
Table Name This field is not editable. The table name is automatically entered once the Table Type is selected and is appended with the entered ship node.

The table name is YFS_INFC_UPLD_TAB1_Node1 for UPLD and YFS_INFC_DNLD_TAB1_Node1 for DNLD table types with the ship node as Node1.
Interface Type The interface type in which the records are processed.
Polling Frequency (seconds) Enter the frequency in seconds to poll for messages from the database table. Defaults to 600 seconds (10 minutes).
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.

Connection properties

The following are the DCS 6.2 Database node's connection properties:

Table 2. DCS 6.2 database connection properties
Connection Node Connection Rules
Can be the first node after the start node Yes, for services invoked both in synchronous or asynchronous mode.
Can be placed before
  • Text Translator component node
  • End node
Can be placed after
  • Start node
  • Text Translator component node
Passes data unchanged Transport nodes do not modify data