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

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.