Without appropriate Error-Handling logic, the first fault thrown by a service invocation within any one of the Split-Join's threads will re-raise in the Split-Join and halt the entire message flow.
In order to prevent this, Catch clauses need to be added to the scope of each thread as shown next.
- Right-click on the loop's scope and select Add Catch.
- Select the new Catch block,
labelit with the name of the fault you wish to catch and then review the Properties tab. - Click on <Soap Fault Variable Name> and assign any name you like (the default is simply
soapFaultwhich should be fine). - Repeat this step for each expected Soap Fault.
- Select Define Fault and enter the fault name and namespace of the fault you expect to catch.
- Drag in a new Scope below the Catch and add any mitigation actions as necessary to resolve the fault. It may be appropriate to do nothing. Simply log the error, or perhaps aggregate a default value into the total. All variables available within the normal scope are also available to you within the Catch block.
- Optionally, add a
Catch Allclause to the loop to capture any unexpected faults.
Fault handling within a Split-Join in OSB is very similar to fault handling in proxy services. One simply has to define a Catch block for the appropriate scope and mitigate each fault appropriately.
By handling faults within the For loop, we ensure that each of the individual threads is managed separately, without impacting the rest of the batch.
..................Content has been hidden....................
You can't read the all page of ebook, please click here login for view all page.