Implementing a global common fault policy is essential when building a SOA BPEL Composites architecture. As your number of production BPEL instances grows, the risk of losing critical data due to a BPEL process crashing in production increases. Especially with large architecture where unexpected usage surge can trigger slowness and failures. Implementing a simple retry fault policy allows the faulted instances to continue once the environment returns to normal.

Implementing a global common fault policy is essential when building a SOA BPEL Composites architecture.

Below is an example of a simple retry global fault policy that will retry up to 7 days for any BPEL instances in error due to a technical issue. To do so, update those three files as follow :

Was this post helpful?

Share: