Important note. 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 unexpected workflow performance. Any custom solutions are possible, but should be treated respectfully.
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:
- About Data Loading Patterns
- Pattern #1 - Loading Many Individual Small Data Messages (non-compressed, non-encoded, order doesn't matter)
- Pattern #2 - Loading Accumulated Messages (non-compressed, non-encoded)
- Pattern #3 - Loading Messages in the Encoded Archive (compressed, encoded)
- Pattern #4 - Loading Messages as an Archive (compressed, non-encoded) in Sequential Mode
To understand the synchronous request by the means of Web Service, please refer to this page: