Standard Batch Process – Execution & Connection
Version 6.0 and Version 6.1 (In Development)
Overview
The following explains the type and mode of batch executions.
Transaction Type
A Govern batch process can run synchronously or asynchronously.
Synch
In synchronous batch processing, transactions are processed one after another in a sequence.
If there are multiple steps in the process, one step is completed before the next begins.
Asynch
In asynchronous processing, multiple operations are started and run at the same time. As soon as one finishes, the next begins.
Multiple steps can run at the same time; for example, steps one, two, three, and four can all begin at the same time.
For long batch processes, using asynchronous batch processing can speed up the transaction time, because multiple computer operations or threads are processed at the same time compared to synchronous batch processing, where one operation has to finish before the next can begin.
IMPORTANT: If a batch process has multiple steps that need to be performed in order; for example, if the results of the first step are required for a calculation in the second step, use synchronous batch processing. |
Connection Pool
You can define a Maximum Connection Pool Size for asynchronous batch processing in the addition to the general Connection Pool Size. You can also set a Connection time out for batch processes.
These parameters are defined on the Connection Key General Parameters Management form in GNA.
The Connection Pool is the number of connections that can be open on the server at the same time. Connections are required for the asynchronous batch processes. They are used by the threads to perform operations for batch processing. They are also required for all other Govern operations from all deployments in your organization.
The Connection Time Out refers to the length of time that a batch process executes a query before a time out occurs. The default is zero (0). This means that there is no time out.
Transaction Mode
Select one of the following transaction modes for the process.
Break If One Transaction Failed
The process terminates when the transaction fails.
Roll Back If One Transaction Failed
The process terminates when a transaction fails. All the transactions that were completed are cancelled. All the computations are returned to the starting point.
IMPORTANT: The roll back can take a long time to execute if the error occurred at the end of the process. |
Continue If One Transaction Failed
The process continues to run even if a transaction fails.
100-bp-Execution