Configuration Guide

10.3 HotFix 3
- 10.5 HotFix 2
- 10.5
- 10.4 HotFix 3
- 10.4 HotFix 2
- 10.4 HotFix 1
- 10.4
- 10.3 HotFix 2
- 10.3 HotFix 1
- 10.3

Back Next

Interactions When API Batch Interoperability is Enabled

The following table shows the interactions between the API and batch processes when row-level locking is enabled.

Existing Lock / New Incoming Call	Batch – Exclusive Lock	Batch – Shared Lock	API Row-level Lock
Batch – Exclusive Lock	Immediately display an error message	Immediately display An error message	Wait for Batch_Lock_Wait_Seconds checking the lock existence. Display an error message if the lock is not cleared by the wait time. Called for each table to be locked.
Batch – Shared Lock	Immediately display an error message	Immediately display An error message	Wait for Batch_Lock_Wait_Seconds to apply a row-level lock using FOR UPDATE SELECT. If the table does not manage the lock, display an error message. Called for each table to be locked.
API - Row level lock	Immediately display an error message	Wait for API_Lock_Wait_Seconds to apply a row-level lock using FOR UPDATE SELECT. If table does not manage the lock, display An error message.	Wait for API_Lock_Wait_Seconds to apply a row-level lock using FOR UPDATE SELECT. If the table does not manage the lock, display an error message. Called for each table to be locked.

When executing Approve tasks, custom index on INTERACTION_ID column of XREF table helps improve the performance on the service side, but the trade off is that it has a negative performance impact on large batch processes, particularly Load and Auto Merge.

Rename Saved Search

Table of Contents

Configuration Guide

Configuration Guide

Interactions When API Batch Interoperability is Enabled

Interactions When API Batch Interoperability is Enabled