Taking Care – Error Handling - Applied SOA Patterns on the Oracle Platform - page 511

ref=" ora-human-intervention "/>
</condition>
</faultName>
</Conditions>
<Actions>
<Action id=" ora-human-intervention ">
<humanIntervention/>
</Action>
</Actions>
</faultPolicy>
</faultPolicies>
In the second file, we performed the binding for the policy ID SendOrder-
Faults :
<faultPolicyBindings version="2.0.1"
xmlns="http://schemas.oracle.com/
bpel/faultpolicy"
xmlns:xsi="http://www.w3.org/
2001/XMLSchema-instance">
<component faultPolicy="SendOrderFaults">
<name> SendOrderToFile </name>
</component>
</faultPolicyBindings>
5. Go to the Mediator and change routing to Parallel . Now we have to redeploy and
test the application again.
6. Fix the error's cause (chmod 777 or modify message element in Trace Flow). Go
to Enterprise Manager and Fault and Rejected Messages and see that the Re-
covery Actions options are available now. Select Retry for the process with the
Recovery Needed status and confirm your choice. Open the Trace Flow after its
completion and see that the problem is as good as gone.
Well, we did a Retry operation manually; so much for automation you say! This is be-
cause for this action, we selected ora-human-intervention . Guess what ora-
retry would do? You will have plenty of additional parameters to set: Retry count,
Retry interval, and what would be the next action if a Retry fails/succeeds (action chain-
ing)?