In the Component Instance ID column, click a specific service component ID In the Logs column, click a link to access the Log Messages page with filtered Managing BPEL Process Service Component Policies

Managing BPEL Process Service Components and Engines 13-9 For more information, see Section 12.1, Viewing the Audit Trail and Process Flow of a BPEL Process Service Component. ■ Message failures in the service engine, including the conversation ID, whether you can recover from the message failure, the service component and composite application in which the failure occurred, and the time at which the fault occurred. Depending on the state, you can recover these messages immediately, cancel these messages, or reset these messages for automatic recovery. Note: Oracle recommends that you add an index on the DLV_ MESSAGE.ECID column of the DLV_MESSAGE table to improve SQL query performance when searching messages for a specific ECID value. This is because if there are too many entries in the DLV_ MESSAGE table, the search query may be slow and may also overload the database. For information on adding an index, see Chapter Creating Indexes of the Oracle Database Administrator’s Guide. 13-10 Oracle Fusion Middleware Administrators Guide for Oracle SOA Suite and Oracle BPM Suite 3. Select a fault in the table. 4. Select one of the following options: Notes: ■ You can recover callback messages in resolved and undelivered states. These messages can be displayed for recovery when you execute search criteria in which you select Callback from the Type list and either Resolved or Undelivered from the Message State list. When a callback message first enters the BPEL process service engine, its state is undelivered. When this message is resolved to the target BPEL process instance either through matching a conversation ID or a correlation, the state is switched to resolved. In both of these states, the messages have not yet been consumed. Messages in these two states can be recovered redelivered into the BPEL process service engine for consumption. In other situations, the callback messages can become stranded in both of these states. Messages in these states can also be recovered. However, there is no guarantee that stranded callback messages always remain in an undelivered state. ■ If you select Invoke from the Type list and Undelivered from the Message State list, and then click Recover, a recovery is performed. However, the Last Modified Date column remains empty for this instance on the Dashboard page of the Oracle BPEL Process Manager service component or service engine. This is the expected behavior. The last modified date is not displayed because the initial Oracle BPEL Process Manager instance for example, bpel:70004 is created by the first invocation that is, it is created, but has not yet been modified. The recovery of the undelivered invocation message always creates a new instance for example, bpel:70005. The previously created instance bpel:70004 is not used and remains permanently in the same status the Last Modified Date column is empty. This information is provided for auditing purposes only. ■ The Message States list is applicable only to callback and invoke message type recovery, and not for activity message type recovery.