Setting the Audit Level at the BPEL Process Service Component Level

Monitoring BPEL Process Service Components and Engines 12-3 For the flow example in the Trace section, the service binding component, service components, and reference binding component involved in the flow have successfully received and processed messages.

3. Select a fault in the Faults section.

This highlights the row in the Trace section in which the fault occurred. 4. Close the fault to clear the selection in the Trace section. 5. Expand the Sensors section to display composite sensors.

6. Select a sensor in the Sensors section.

This highlights the row in the Trace section in which the composite sensor data was collected. If there are BPEL process messages that require recovery from the Recovery page of the BPEL process service engine, a BPEL Message Recovery Required inline warning message and recovery icon are displayed. 12-4 Oracle Fusion Middleware Administrators Guide for Oracle SOA Suite and Oracle BPM Suite

7. Click Show Details or the recovery icon to display a Warning dialog with the

following recovery details: ■ The number of invoke, callback, and activity recoverable message types ■ The ECID value Use this information for creating search criteria for filtering the recoverable messages on the Recovery page of the BPEL process service engine. You can copy the ECID number from the Warning dialog, paste it into the ECID field, and select the recoverable message type from the Type list. For more information about creating search criteria with the ECID number in the Recovery page, Section 13.4, Performing BPEL Process Service Engine Message Recovery. The display of this message recovery information on the Flow Trace page is controlled by the AuditConfig property in the System MBean Browser. By default, this property is set to All, which enables this information to be displayed. To prevent this information from displaying on the Flow Trace page, set the bpelRecoveryStatus key to Off for the AuditConfig property in the More SOA Infra Advanced Configuration Properties section of the SOA Infrastructure Common Properties page. For more information, see Section 3.1, Configuring SOA Infrastructure Properties. Note the following restrictions with ECIDs: ■ A separate ECID is displayed for each instance of a composite application and not for the composite level ECID that can track the complete flow of any instances for the composite application. ■ To get complete flow information, you must find the composite level ECID in the log files. Use that value to get all information for a particular composite and therefore all its executed instances. ■ ECIDs are not propagated through business events. This can limit the amount of logging information that is collected. For example, if you publish an event that is subscribed to in the same composite application, limited logging information is available. Monitoring BPEL Process Service Components and Engines 12-5

8. In the Instance column of the Trace section, click a specific BPEL process service

component instance. Service component instances can be accessed from this section; services and references cannot be accessed. The Instance page appears. Use these four pages to view the audit trail, flow, sensor values, and faults of a BPEL process service component instance. The following links provide additional details about the instance: ■ Flow Trace link: Click the breadcrumbs in the upper left-hand corner of the page to access the flow trace for the ECID composite instance that contains this BPEL component instance. ■ Information icon : Click the information icon to the right of the name of the BPEL component in the page title to see biographical information about this BPEL instance. This information includes a summary of the instance, including instance ID, ECID, instance startup time or last modification time, instance state for example, running, and number of faults. This icon is only displayed on the Audit Trail pages of BPEL processes and Oracle Mediators, and not on the pages of human tasks and business rules. ■ Audit Level Settings : Click to display information details, such as the audit level used by this instance. ■ View Raw XML : Click to display the raw XML of the audit trail. The Audit Trail page displays execution details about the activities in the BPEL process. 12-6 Oracle Fusion Middleware Administrators Guide for Oracle SOA Suite and Oracle BPM Suite 9. Scroll through the audit trail to check for errors and expand the payload links to view their contents at a given point in the flow.

10. Click the Flow tab.

A flow diagram of the BPEL process activities appears. This flow diagram shows a fault highlighted in a BPEL process activity. Notes: ■ Canceled onMessage branches of pick or scope activities that did not execute are displayed in the audit trail. However, the flow diagram does not show these same canceled onMessage branches. This is the expected behavior. ■ The following error message appears when a transaction is displayed as rolled back in the Audit Trail page: The transaction was rolled back. The work performed for bpel instance instance_ number was rolled back to the previous dehydration point, but the audit trail has been saved. You can recover the instance from the recovery console by resubmitting the callback message or activity for execution This message does not specifically state whether recovery should happen on either the activity or the callback. This is the intended behavior. Oracle recommends that you do not recover each instance through the audit messages. Instead, set up automatic recovery to recover these instances.