About the Transaction Web Service

The Transaction Web Service provides a versioned interface for controlling one or more inner transactions on a particular data domain, inside a single outer transaction.

Each Web service request to the Oracle Endeca Server represents an inner transaction. If the request completes successfully, the transaction is automatically committed. If the request fails, the transaction is rolled back.

In addition to using these inner transactions that are sent as independent Web service requests, you can also nest inner transactions inside a single outer transaction run by the Transaction Web Service.

http://host:<port>endeca-server/ws/transaction/<DataDomain>?wsdl

where host and port represent the Oracle Endeca Server, and the DataDomain is the name of the data domain hosted on the server. The WSDL that is returned contains a version number for the service.

Using outer transactions depends on whether you want to group multiple updates (which, together with other web service requests, typically represent simple inner transactions) into a single outer transaction.

The Transaction Web Service enables you to isolate updates within a single outer transaction, while non-updating queries continue to be processed against the pre-transaction version of the data domain's index.

Although you can issue requests to the Transaction Web Service with any Web service tool, such as soapUI, you can use the Transaction RunGraph in Integrator ETL.