Recovering from BPEL Process Service Component Faults

13-6 Oracle Fusion Middleware Administrators Guide for Oracle SOA Suite and Oracle BPM Suite 1. Access this page through one of the following options:

2. Click Faults.

The Faults page displays the following details: ■ A utility for searching for a specific fault by specifying criteria and clicking Search . Click the Help icon for details. ■ Faults that occurred in the service engine, including the fault ID, error message, whether you can recover from the fault, the time at which the fault occurred, the SOA composite application and service component in which the fault occurred, and the service component instance ID. BPEL process service engine faults identified as recoverable can be recovered. 3. Select faults for recovery using one of the following options. As with fault recovery at the SOA Infrastructure level, SOA composite application level, and Oracle Mediator service component level, you can perform single fault recovery, bulk fault recovery, and recovery of all faults. See Step 4 of Section 13.1, Recovering from BPEL Process Service Component Faults for instructions on selecting faults to perform these types of recovery. From the SOA Infrastructure Menu... From the SOA Folder in the Navigator... 1. Select Service Engines BPEL. 1. Right-click soa-infra. 2. Select Service Engines BPEL. Managing BPEL Process Service Components and Engines 13-7

4. Select an action from the Recovery Action list.

5. Perform the following additional monitoring tasks from within the faults table:

a. Click the Show only recoverable faults checkbox to only display faults from

which you can recover.

b. From the Fault Type list, select to display all faults, system faults, business

faults, or OWSM faults in the faults table. Click the Help icon for a description of these fault types.

c. From the View list, select Columns Fault ID to display the fault IDs for each

error message. The fault ID is automatically generated and uniquely identifies a fault. The fault ID is also displayed when you click an error message.

d. In the Composite column, click a specific SOA composite application to access

its home page.

e. In the Component column, click a specific service component to access its

home page.

f. In the Component Instance ID column, click a specific service component ID

to access task details about the instance for example, the current state of a task. Note that rejected messages do not have a component instance ID. For more information, see the following sections: ■ Section 1.4.3.1, Introduction to Fault Recovery for conceptual details about faults ■ Section 8.5.1, Examples of Fault Recovery for BPEL Processes

13.4 Performing BPEL Process Service Engine Message Recovery

You can perform a manual recovery of undelivered invoke or callback messages due to a transaction rollback in the process instance. Recovery of invoke messages applies to asynchronous BPEL processes only. Synchronous BPEL processes return an error to Note: In most cases, fault policy actions are automatically executed. The only exception is if you defined a fault policy that uses the action ora-human-intervention. This action creates a recoverable fault that can be recovered from Oracle Enterprise Manager Fusion Middleware Control. Action Description Retry Retries the instance with an option to provide a retry success action. An example of a scenario in which to use this recovery action is when the fault occurred because the service provider was not reachable due to a network error. The network error is now resolved. Abort Terminates the entire instance. Replay Replays the entire scope activity again in which the fault occurred. Rethrow Rethrows the current fault. BPEL fault handlers catch branches are used to handle the fault. By default, all exceptions are caught by the fault management framework unless an explicit rethrow fault policy is provided. Continue Ignores the fault and continues processing marks the faulted activity as a success. 13-8 Oracle Fusion Middleware Administrators Guide for Oracle SOA Suite and Oracle BPM Suite the calling client and are not recoverable from the Recovery page. Recoverable activities are activities that failed and can be recovered. For example, if you are using the file adapter to initiate an asynchronous BPEL process and your system fails while the instance is processing, you can manually perform recovery when the server restarts to ensure that all message records are recovered. You can also manage messages that have failed automatic recovery attempts by the BPEL process service engine. To ensure that automatic recovery of these messages is not attempted multiple times, these messages are placed in the exhausted state. You can then perform one of the following actions on these messages: ■ Return them to the automatic recovery queue ■ Never attempt a recovery on them again ■ Attempt to recover them immediately For example, assume you have a BPEL process that writes to a database adapter. If the database is down, these messages are sent to a recovery queue. Automatic recovery of these messages fails while the database is down. Such messages are marked with the exhausted state so that automatic recovery is not attempted on them again. When the database begins running again, you can reset these messages return them to the automatic recovery queue so that an automatic recovery is attempted on them again. To perform BPEL process service engine message recovery: 1. Access this page through one of the following options:

2. Click Recovery.

The Recovery page displays the following details: ■ A Refresh Alarm Table button for resynchronizing lost, in-memory, Quartz-scheduled jobs in the database. For example, assume a timer on a wait activity or on an onAlarm branch of a pick activity was initiated, but the transaction was rolled back. You can resynchronize these jobs with the BPEL instances residing in the wait activityonAlarm branch in the database. ■ A utility for searching for a specific message failure by specifying criteria and clicking Search. Click the Help icon for details. You can enter the execution context ID ECID value in the ECID field. The ECID value enables you to track a message flow that crosses instances of different composite applications. If there are BPEL process messages requiring recovery and the AuditConfig property in the System MBean Browser is set to All the default value, the following message is displayed in the Trace table of the Flow Trace page: BPEL Message Recovery Required Clicking Show Details or the recovery icon that appears next to this message displays a Warning dialog with information about the number of invoke, callback, and activity recoverable message types and the ECID value. You can copy the ECID value from the Warning dialog, paste it into the ECID field, and select the recoverable message type from the Type list as part of creating your search criteria on the Recovery page. From the SOA Infrastructure Menu... From the SOA Folder in the Navigator... 1. Select Service Engines BPEL. 1. Right-click soa-infra. 2. Select Service Engines BPEL.