Maintaining the Core – Service Repository - Applied SOA Patterns on the Oracle Platform - page 355

The rule of thumb is simple: rollback tasks can be implemented in the same execution
plan. Complex compensation activities shall be combined in a separate execution plan and
the master Service Broker will delegate the execution to the subcontroller (another in-
stance of the Service Broker). These operations are controlled by the error handler, which
also communicates with the Service Repository to find the error resolution:
<?xml version = '1.0' encoding = 'UTF-8'?>
<phs:ExecutionPlan
xmlns:phs="urn:com:telco:ctu:la:processheader:v01">
<phs:taskList>
<phs:task>
<phs:invoke taskDomain="OrderFulfillment"
taskName="changeStatus" mep="sync">
<phs:serviceTask>
<phs:taskSteps flow="request"
technology="OSB">
<phs:transform location="Fusion/Xquery/
transformation/ChangeOrderRequest" type="OSB-Resource"/>
<phs:invoke protocol="HTTP"
endpoint="http://<physical_address>"/>
</phs:taskSteps>
<phs:taskSteps flow="response"
technology="OSB">
<phs:transform location=" Fusion/Xquery/
transformation/ChangeOrderResponse" type="OSB-Resource"/>
</phs:taskSteps>
</phs:serviceTask>
</phs:invoke>
</phs:task>
</phs:taskList>
</phs:ExecutionPlan>
The physical implementation of the Execution Plan is presented in the following figure: