By Phil Coulthard

Well-designed external and Advanced Integration services have modeled faults for business exceptions such as “insufficient funds” and often have unmodeled faults for technical exceptions such as “network failure” issues. When you are invoking services from a process, design your process to deal with both types of faults. Typically, a business exception can be handled in the process flow, such as by returning to a previous step or engaging the user, whereas a system fault might result in retrying the service or engaging a process administrator.

To learn more about how to model fault handling in Business Process Modeling Notation (BPMN), search the IBM® Business Process Manager (BPM) documentation for your release for “Handling errors in services”.

Also, see the following resources:

• WebSphere Lombardi exception handling and logging
• “Introduction to enhanced error handling and termination handling” presentation

To learn more about how to model fault handling in Business Process Execution Language (BPEL), search the IBM BPM documentation for your release for “Fault handling in BPEL“.

Also, see these developerWorks articles:

• Error handling in WebSphere Process Server, Part 1: Developing an error handling strategy
• Implementing tracing, logging, and error handling in mediation modules using WebSphere Integration Developer and WebSphere ESB V7, Part 1
• Tracing, logging, and error handling in mediation modules using IBM Integration Designer, WebSphere ESB, WebSphere Process Server, and Business Process Manager Advanced Edition, Part 2
• Configuring error handling for Advanced Integration Services in IBM Business Process Manager Advanced V8

Applicable editions: Express, Standard, and Advanced

Applicable releases: All

Source: IBM