Table of Contents

Search

  1. Preface
  2. Welcome to Informatica Process Developer
  3. Using Guide Developer for the First Time
  4. Getting Started with Informatica Process Developer
  5. About Interfaces Service References and Local WSDL
  6. Planning Your BPEL Process
  7. Participants
  8. Implementing a BPMN Task or Event in BPEL
  9. Implementing a BPMN Gateway or Control Flow
  10. Using Variables
  11. Attachments
  12. Using Links
  13. Data Manipulation
  14. Compensation
  15. Correlation
  16. What is Correlation
  17. What is a Correlation Set
  18. Creating Message Properties and Property Aliases
  19. Adding a Correlation Set
  20. Deleting a Correlation Set
  21. Adding Correlations to an Activity
  22. Rules for Declaring and Using Correlation Sets
  23. Correlation Sets and Engine-Managed Correlation
  24. Event Handling
  25. Fault Handling
  26. Simulating and Debugging
  27. Deploying Your Processes
  28. BPEL Unit Testing
  29. Creating POJO and XQuery Custom Functions
  30. Custom Service Interactions
  31. Process Exception Management
  32. Creating Reports for Process Server and Central
  33. Business Event Processing
  34. Process Central Forms and Configuration
  35. Building a Process with a System Service
  36. Human Tasks
  37. BPEL Faults and Reports

2. Designer

2. Designer

What is BPEL Fault Handling

What is BPEL Fault Handling

Fault handling in a BPEL process refers to the procedures performed when an exception or unanticipated condition occurs during normal processing. The work performed restores state so that predictable results always occur. Fault handling differs from compensation handling in that fault handling happens when a fault occurs within a scope whereas compensation reverses the work of a successfully completed scope. This means that the fault handler has access to information contained within the scope.
A fault can occur for the following reasons:
  • A web service operation cannot complete successfully, and the service returns a fault
  • An internal process error occurs, and a standard BPEL fault is thrown. Refer to the list of
    BPEL Standard Faults
    in the
    Process Developer Help
    for more information.
  • A
    <throw>
    or
    <rethrow>
    activity throws a fault
  • A platform-specific fault, such as a communication failure, occurs in a BPEL process instance
Fault handling can be global or local: you can add fault handlers to the process as a whole or to a scope within the process.
When a fault occurs, normal processing is terminated, and control is transferred to the corresponding fault handler, as defined in the
<faultHandlers>
section of the process or scope.
Note that the process does not enable compensation for a scope in which a fault handler is invoked.
Fault handlers do not rely on state to determine which nested scopes have completed successfully.
For a discussion of fault handling and compensation handling for a scope, see
Lifecycle of a Scope
.


Updated March 30, 2020