Monitoring BPMN Process Service Component Instances and Faults

Managing Oracle BPMN Service Components and Engines 38-7 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.2, Examples of Fault Recovery for BPMN Processes

38.4 Performing BPMN 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 BPMN processes only. Synchronous BPMN processes return an error to the calling client and are not recoverable from this page. Recoverable activities are activities that failed and can be recovered. For example, if you are using the file adapter to initiate an asynchronous BPMN process and your system crashes while the instance is processing, you can manually perform recovery when the server restarts to ensure that all message records are recovered. To perform BPMN process service engine message recovery: Rethrow Rethrows the current fault. BPMN 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 faulting activity as a success. Note: If you encounter the error message ORA-01000: maximum open cursors exceeded, then do the following: 1. Shut down the Oracle database. 2. Increase the value of OPEN_CURSORS to 1500. 3. Restart the Oracle database. Action Description 38-8 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 Recovery.

The Recovery page displays the following details: ■ A utility for searching for a specific message failure by specifying criteria and clicking Search. Click the Help icon for details. ■ Message failure 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.

3. Select a fault in the table.

4. Select one of the following options:

Once a message is submitted for recovery, the BPMN process service engine may take time to complete the action. This typically takes less than several seconds. During this time, the message remains visible in the Recovery page. Duplicate attempts to recover the same message in that period are ignored. Refresh the page every few seconds to receive the latest recovery status. From the SOA Infrastructure Menu... From the SOA Folder in the Navigator... 1. Select Service Engines BPMN. 1. Right-click soa-infra. 2. Select Service Engines BPMN. Action Description Recover Retries the message in which the fault occurred. If an asynchronous BPMN process encounters a transaction rollback scenario because of any underlying exception error, it rolls back to the last dehydration activity. If this is a new instance, and a receive activity was the first dehydration activity, the BPMN process service engine creates a recoverable invoke. When you click Recover to recover the invoke, the service engine creates a new instance. This instance may run to completion with no exception error. However, you continue to see the older instance identified as faulted. Mark Cancelled Marks the message so it is never delivered. Part XVI Appendixes This part includes the following appendixes: ■ Appendix A, Demo User Community ■ Appendix B, Troubleshooting Oracle SOA Suite ■ Appendix C, Oracle Enterprise Manager Roles