Manage Synchronous Data Loads

The main difference of synchronous run task requests from asynchronous is that the ACK message is omitted and the request is kept pending until all processing is complete and a TSR is formed. The main disadvantage of such approach is the possibility of connection timeouts in case of too long processing.

Synchronous execution was introduced as a specific feature which allows Web Service send TSR instead of ACK to the client. We do not recommend using synchronous execution other than in junction with Web Service, as it may cause unpredictable performance levels. It still can be used as a custom solution, but should be set up respectively.

Synchronous execution is supported both for load and extract, but it is disabled in EJM by default. It is controlled by the W_USE_PARALLEL_LOAD global variable in w_config_custom.inc or by the synchronousExecution element in the incoming data file. See suggested load patterns:

To understand the synchronous request (example given for extract) by the means of Web Service, please refer to this page:

EagleML Web Service - Synchronous Request