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

Configuration for fault handling

Adapter Foundation Classes fault names and the corresponding fault binding names are used in the fault configuration.

A fault name is defined within each fault class. The base fault binding is configured unless attributes are unique.

The following table includes examples of situations when an adapter might throw each type of fault. These are examples only.

Fault name and configured fault binding
Fault Name Configured Fault Binding

DUPLICATE_RECORD

com.ibm.j2ca.extension.emd.runtime.WBIFaultDataBindingImpl

The adapter throws this fault when processing an outbound Create operation when an error occurs because the specified file already exists in the specified directory path.

INVALID_REQUEST

com.ibm.j2ca.extension.emd.runtime.WBIFaultDataBindingImpl

When input to the operation does not have the required characteristics, the adapter throws this fault. Specific errors that can result include the following:

  • For a Create operation:

    • A ChangeSummary is provided but the required child business objects are not marked as created (per strict conventions)

    • A business object is marked as deleted in the ChangeSummary (assertion optional)

    • The input business object specifies key values, but the server supports only auto-creation

    • The input business object does not contain key values, but the server requires them

  • For a Delete operation:

    • A ChangeSummary is provided but the required child business objects are not marked as deleted (per strict conventions)

    • A business object is marked as created in the ChangeSummary (assertion optional)

MATCHES_EXCEEDED_LIMIT

com.ibm.j2ca.extension.emd.runtime.MatchingFaultDataBinding

When processing a RetrieveAll operation, the adapter throws this fault if the number of records returned from a database query exceed the maximum number of records property in the interaction specification.

MISSING_DATA

com.ibm.j2ca.extension.emd.runtime.WBIFaultDataBindingImpl

If the business object that is passed to the outbound operation does not have all the required attributes, the adapter throws this fault.

MULTIPLE_MATCHING_RECORDS

com.ibm.j2ca.extension.emd.runtime.MatchingFaultDataBinding

When processing a Retrieve operation, the adapter throws this fault if the query returns more than one record for the specified keys.

RECORD_NOT_FOUND

com.ibm.j2ca.extension.emd.runtime.WBIFaultDataBindingImpl

When processing a data retrieval operation, the adapter throws this fault if the record is not found in the database for the keys specified. This fault can occur for the Delete, Update, Retrieve, and RetrieveAll operations.

Fault handling support


Related concepts:

How to support fault handling

Implementing faults

Defining custom faults


Related reference:

Fault artifacts