Request processing in the presence of transactions

This topic describes how requests sent from various Web services, administration URL requests, and the Bulk Load Interface are treated by the Oracle Endeca Server, in the presence of outer transactions.

Requests from the Oracle Endeca Server interfaces can be updating and non-updating (read-only).

For read-only requests, if the correct outer transaction ID is specified as the first element in the request, they run inside the outer transaction against the most recent version of the index. If no transaction ID is specified, the requests run against the pre-transaction version.

For updating requests, if the correct ID is specified as the first element in the request, the requests run; otherwise, the requests wait until the outer transaction is committed (or rolled back), and are computed based on the published version of the index that becomes available at that time.

An incorrect ID in any request results in a SOAP fault.