The rollBackOuterTransaction operation is useful in operational environments that use outer transactions. In case a running outer transaction fails, this operation lets you roll back to the previously committed version of the data files and commit the transaction.
You can run this operation directly using a tool such as soapUI, or in Integrator, using one of the two options: either through the Transaction RunGraph component and its rollback option, or by using the WebServiceClient component in Integrator, by configuring it to access the Transaction Web Service on the particular data store, and specifying the rollBackOuterTransaction operation to it.
http://localhost:<port>/ws/transaction/<DataStore>?wsdlUse this operation only if an outer transaction has been started on the node, referencing a transaction ID in the OuterTransactionIdToRollBack element, as in the following example:
<rollBackOuterTransaction> <OuterTransactionIdToRollBack>myID</OuterTransactionIdToRollBack> </rollBackOuterTransaction>
If you have updating requests sent to the server that didn't specify the outer transaction ID, these requests wait for the outer transaction to finish (be committed or rolled back). If you roll back the outer transaction, these requests start being processed by the server based on the published version of the data files that is available after the rollback operation.
Once the operation completes, it stops the outer transaction, and the leader resumes serving queries on the last version of the data files available before the start of the outer transaction.