Before we discuss the essential steps in exception handling in an agnostic composition controller implemented in the CTU SOA farm, we will mention the importance of clear and consistent identification of all fault messages related to certain process instances. You could use a standard Ora ECID for this purpose in addition to the initial Java-based labeling process instance at the beginning of every BPEL:
Go to the Receive activity tab at the top and select Edit after a right-click.
In the Properties tab, click on the green cross and select tracking.ecid from the drop-down list. Assign it to the variable of your choice. Use it within your Message Tracking Records Object.
We will start with recalling the structure of the composition controller (async Service Broker). Basically, it has two parts (if we omit the standard initialization): acquiring the execution plan and looping through EPs elements. Thus, we should have three exception scopes: sequentially, one for master...