Subscription Options Tab
In Subscription Service, you can use the Subscription Options tab to specify an exceptions table and an opaque exceptions table and perform other configurations. The adapter uses the exceptions table to store error messages from database operation failures.
The following table lists and describes the fields, which are grouped in two panels.
Name | Description |
---|---|
Subscription Service Base Information Panel | |
Use Separate Session | The
Use Separate Session check box is used with Subscription Service multithreading. When you select this check box, the following options are displayed:
After you set a value in the Number of Subscription Service Threads field, the multiple threads can share the same session and dispatcher. By default, the Use Separate Session check box is not selected. |
useSerial | This check box is displayed when the
Use Separate Session check box is selected.
This option is designed to ensure that all messages are processed in order. Note: Note the following conditions about this option:
|
Number of Subscription Service Threads | This field is displayed when the
Use Separate Session check box is selected.
Threads are allocated on demand. The valid values range from 1 through n. The number of threads you set in Subscription Service indicates the number of subscription threads that will connect to the database. For more information, see Multithreading and Session in Subscription Service. |
Subscription Service Option Information Panel | |
Exceptions Table | Name of the exceptions table to which data is written if the adapter cannot write the data to the destination table. This table holds messages that caused an exception. If a table does not exist, Subscription Service creates one such table. For details, see
Exceptions Table.
The exceptions table cannot contain any user-created columns in which the column name starts with ADB_. These characters are reserved for use by the adapter. |
Use Opaque Exceptions Table | Select this check box to use an opaque exceptions table. The table records each message entirely into a column, along with the error message.
A message is logged into the exceptions table if Subscription Service fails to generate records in the destination table or the adapter fails to insert a message into an exceptions table. For details, see Opaque Exceptions Table. For DB2/390 databases, you must create a LOB table space before using the opaque exceptions table, which uses the LOB table space. |
Opaque Exceptions Table | Name of the opaque exceptions table. For details, see Opaque Exceptions Table. |
Pre Commit Stored Procedure | Name of a stored procedure Subscription Service calls after the database insert, update, or delete operation and before the commit. |
Reply Sender Quality of Service | If Subscription Service must send a reply to the sender, this value identifies the quality of service or delivery mode to be used to send the reply. |
Bulk Insert Size | When configured for batch processing, the adapter stores incoming subscription requests in a batch. All incoming messages to be inserted are stored until this size is reached. Then, a bulk insert operation is performed on the destination table by using a single processing.
This number must be less than or equal to the value in Batch Commit Size. The default value is 1. The batch is emptied when the batch size is reached. Note: When using a parent-child relationship, you must note the following conditions:
|
Batch Commit Size | The number of messages to be batched before a commit operation is invoked. The default value is
0. This field is displayed when the
Use Separate Session check box is selected.
Note the following conditions regarding the
Batch Commit Size field:
For more information about batch commit, see Configuring Batch Commit for Subscription Service. |
Batch Commit Timeout(milliseconds) | Specifies the longest interval between two batch commits. When the specified timeout expires, Subscription Service commits all the received messages even if the number does not reach the
Batch Commit Size value. The default value is
10,000 milliseconds. This field is displayed when the
Use Separate Session check box is selected.
The batch commit feature does not commit all received messages if the adapter configuration terminates before the batch commit value or time-out value is met. If RVCMQ is enabled, when the batch commit size is greater than 1, batch commit times out after each operation (insert, update, or delete). Note: When you use the default session for Subscription Service, if you set the
Batch Commit Size and
Batch Commit Timeout(milliseconds) fields in TIBCO Business Studio and then upgrade the adapter from an earlier version to the current version, the configurations of these fields in TIBCO Business Studio are lost and you have to reset the corresponding properties in the
adbagent.tra file.
For more information about batch commit, see Configuring Batch Commit for Subscription Service. |
Rendezvous Maximum Queue Size | Maximum number of messages that can be put in the TIBCO Rendezvous event queue. The default value is
0, which indicates that no limit is placed on the event queue size.
Use this option to prevent the memory of a subscriber endpoint from overflowing if the publisher endpoint is too fast. |