Configuring Batch Commit for Subscription Service
In TIBCO ActiveMatrix Adapter for Database 7.1.0 hotfix 004, the adb.<default_session_name>.subBatchCommitTimeout and adb.<default_session_name>.subBatchCommitSize properties were added to configure batch commit for Subscription Service without using separate sessions.
These two properties help resolve a specific issue in the adapter version 7.1.0 hotfix 004, that is, in an adapter instance configured with multiple services of Subscription Service, if you perform the following configurations in TIBCO Designer:
| • | The services are configured with the same transport type. |
| • | The Use Separate Session check box in the Configuration tab is not selected. |
| • | A parent-child table relationship is used for one of the services. |
| • | The subBatchCommitTimeout and subBatchCommitSize options are configured in the Subscriber Options tab. |
In a specific commit transaction Subscription Service occasionally commits and confirms only the parent-table data of a message; in the subsequent commit transaction, Subscription Service commits the child-table data of this message.
This issue results from the use of a timer for each service.
To resolve this issue, you can set the following properties in the adbagent.tra file:
| • | adb.<default_session_name>.subBatchCommitTimeout
|
| • | adb.<default_session_name>.subBatchCommitSize
|
After the properties are set, all services of Subscription Service, which are configured with the same transport type, share one batch commit timer and one batch commit size.
|
Note |
If you want to use batch commit without using separate sessions, you can set either of the following properties in the
|
For details about these properties, see Adapter Properties.