A batch process can lock individual records for a significant period of time, which can interfere with
SIF
access over the web.
There can be small windows of time during which
SIF
requests will be locked out. However, these should be few and limited to less than ten minutes.
The
Hub Store
needs to be sufficiently sized to support the combined resource demand load of executing batch processes and
SIF
requests concurrently.
Interoperabilty must be enabled if Batch jobs are being run together. If, you have multiple parents that attempt access to the same child (or parent) records when running different Batch jobs, one job will fail if it attempts to lock records being processed by the other batch and it holds them longer than the batch wait time. The maximum wait time is defined in C_REPOS_TABLE.