IBM BPM, V8.0.1, All platforms > Authoring services in Integration Designer > Services and service-related functions > Access external services with adapters > Configure and using adapters > IBM WebSphere Adapters > Adapter Toolkit > Implementing code from the IBM WebSphere Adapter Toolkit > Problem determination > Fault handling support
How to support fault handling
Understand the following concepts for implementing fault handling into your adapter.
Before you define faults, review adapter processing to determine which error conditions can be categorized as faults, rather than as exceptions. You will likely be able to apply at least one of the faults provided in the Adapter Foundation Classes. Some unique conditions might be categorized as faults, but fault classes in the Adapter Foundation Classes might not be provided for the conditions. Error conditions from which you can recover might be candidates for fault handling. IT exceptions, such as one time configuration issues (wrong password, incorrect directory permissions, etc.) are not candidates for fault handling.
When naming a fault, ensure that the name describes the condition and is independent of the technology or adapter you are using.
For example, the fault class name for an SAP IDoc record not found condition should be RecordNotFoundFault, not SAPIDOCRecordNotfoundFault. Additionally, you might not need to define new faults if the same semantic meaning can apply to multiple conditions (for example, RecordNotFoundFault, FileNotFoundFault, and ObjectNotfoundFault).
Related concepts:
Configuration for fault handling
Related reference: