Understanding Oracle BPEL Error Handling Understanding Oracle Mediator Error Handling

24 Configuring Oracle AIA Processes for Error Handling and Trace Logging 24-1 24 Configuring Oracle AIA Processes for Error Handling and Trace Logging This chapter includes the following sections: ■ Section 24.1, Overview of Oracle BPEL and Mediator Process Error Handling ■ Section 24.2, Overview of AIA Error Handler Framework ■ Section 24.3, Enabling AIA Processes for Fault Handling ■ Section 24.4, Implementing Error Handling for the Synchronous Message Exchange Pattern ■ Section 24.5, Implementing Error Handling and Recovery for the Asynchronous Message Exchange Pattern to Ensure Guaranteed Message Delivery ■ Section 24.6, How to Configure AIA Services for Notification ■ Section 24.7.3, Describing the FaultNotification Element ■ Section 24.8, Extending Fault Messages ■ Section 24.9, Extending Error Handling ■ Section 24.10, Configuring Oracle AIA Processes for Trace Logging For more information about Oracle AIA B2B error handling, see Chapter 16, Introduction to B2B Integration Using AIA.

24.1 Overview of Oracle BPEL and Mediator Process Error Handling

This section includes the following topics: ■ Section 24.1.1, Understanding Oracle BPEL Error Handling ■ Section 24.1.2, Understanding Oracle Mediator Error Handling

24.1.1 Understanding Oracle BPEL Error Handling

The Oracle Application Integration Architecture AIA Error Handling Framework groups BPEL process errors into two categories: ■ Run-time faults ■ Business faults Run-time Faults A run-time fault can occur in one of two scenarios: 24-2 Developers Guide for Oracle Application Integration Architecture Foundation Pack ■ The partner link invocation fails. ■ The partner link receives a named fault indicating that it is a run-time fault. These faults are not user-defined and are issued by the system. Some of the situations in which a BPEL process can encounter a run-time fault include the following: ■ The process tries to use a value incorrectly. ■ A logic error occurs. ■ A SOAP fault occurs in a SOAP call. ■ An exception is issued by the server, and so forth. AIA Services built as BPEL processes should be enabled and configured to catch and handle the run-time faults. Business Faults A business fault can occur in one of two scenarios: ■ A BPEL process runs a throw activity after evaluating a condition as a fault. ■ An Invoke activity receives a named fault indicating that it is a business fault. Business faults are the application-specific faults that are generated when erroneous conditions take place when the message is being processed. These faults are specified by the BPEL process component and are defined in the WSDL. AIA Services built as BPEL processes should be enabled and configured to catch and handle the run-time, as well as business faults.

24.1.2 Understanding Oracle Mediator Error Handling

A Mediator component can handle both run-time faults and business faults. Run-time Faults These are faults that occur because of some problem in the underlying system, such as the network not being available. Business Faults These are exceptions that are returned by called Web services. These are application-specific and are explicitly defined in the services WSDL file. AIA Services built as Mediator components should be configured to catch and handle the business faults. However, fault policies are applicable to parallel routing rules only. For sequential routing rules, the fault goes back to the caller and it is the responsibility of the caller to handle the fault. We recommend the usage of sequential routing rules only. For more information about configuring the Mediator to handle business faults arising from synchronous invocations using sequential routing rules, see Section 24.4.3, Guidelines for Configuring Mediator for Handling Business Faults. Configuring Oracle AIA Processes for Error Handling and Trace Logging 24-3

24.2 Overview of AIA Error Handler Framework