Subscriber Options Tab

You can specify the following values on the Subscriber Options tab:

Subscription Service: Subscriber Options Tab

Field

Description

Exceptions Table

Name of the exception table to which data is written if the adapter cannot write the data to the subscriber table. This table holds messages that caused an exception. If the table does not exist, Subscription Service creates one by itself. For details, see Exception Table.

The exception table cannot contain any user-created columns where the column name starts with ADB_. These characters are reserved for use by the adapter.

Note: For the parent-child relationship, this is the parent exception table. If you does not set the parent exception table, the child exception table is invalid.

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 in the opaque exceptions table if Subscription Service fails to generate records in the destination table or the adapter fails to insert a message into an exception table.

For DB2 OS390 databases, you must create a LOB table space before using the opaque exceptions table.

Opaque Exceptions Table

Specifies the name for the opaque exceptions table.

Pre Commit Stored Procedure

The value entered here represents the name of a stored procedure the subscriber will call after the database insert, update, or delete operation and before the commit.

Reply Sender Quality Of Service

If the subscriber must send a reply to the sender, this value identifies the quality of service or delivery mode to be used when sending the reply. See Quality of Service and Delivery Mode for a description of these fields.

• Reliable (TIBCO Rendezvous transport type only)
• Certified (TIBCO Rendezvous transport type only)
• Persistent (JMS transport type only)
• Non-Persistent (JMS transport type only)

Bulk Insert Size

All incoming messages to be inserted are stored until this size is reached. Then, a bulk insert operation is performed on the destination table. The default value is 1.

Note:

In the parent-child relationship situation, you have to note the following conditions:

• Bulk Insert is valid if you enable group messaging and only send the data to the parent table.
• Bulk Insert is invalid if you send the data to the parent table and child table.
• Increasing the bulk insert size does not significantly improve the adapter Subscription Service performance.
• If you want to use JDBC driver options to improve the adapter Subscription Service performance, it is good practice to set the batchPerformanceWorkaround=true property instead of the EnableBulkLoad and BulkLoadBatchSize properties in the TRA file.

Batch Commit Size

The number of messages to be batched before invoking a commit operation. The default value is 0. This field is displayed only when the Use Separate Session check box is selected in the Configuration tab.

Note:

• If you use the default value in the Batch Commit Size field, the adapter will take the value 1 as the batch commit size when running Subscription Service.
• The Batch Commit option is not supported with the RVCMQ transport. The RVCMQ scheduler requires a message to be confirmed before dispatching the next message, which prevents the adapter from operating in batch mode.
• When you use the default session for Subscription Service, if you set the Batch Commit Size and Batch Commit Timeout (milliseconds) fields in TIBCO Designer and then upgrade the adapter from an earlier version to the current version, the configurations of these fields in TIBCO Designer 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.

Batch Commit Timeout (milliseconds)

Specifies the longest interval between two batch commits. When the specified timeout expires, the adapter 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 only when the Use Separate Session check box is selected in the Configuration tab.

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 Designer and then upgrade the adapter from an earlier version to the current version, the configurations of these fields in TIBCO Designer 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 from overflowing if the publisher is too fast.

Note: If the value of this field is set to be smaller than the actual number of messages in the event queue, only the allowable number of messages can be sent and the subsequent messages are lost.