11 Monitoring BPEL Process Service Components and Engines

11.1 Viewing the Audit Trail and Process Flow of a BPEL Process Service Component

This section describes how to view the audit trail and process flow of a BPEL process service component in a SOA composite application instance.

To view the audit trail and process flow of a BPEL process service component:

1. Access this page through one of the following options:

   From the SOA Infrastructure Menu...	From the SOA Folder in the Navigator...
   Select Home. Select the Deployed Composites tab. In the Composite section, select a specific SOA composite application.	Under soa-infra, select a specific SOA composite application.

   
   

   The Dashboard page for the selected composite application appears.

2. Use one of the following methods to select an instance of the application:

   • For recent instances of this application, click the instance number of an instance in the Instance ID column of the Recent Instances section.

   • For all instances of this application, click the Instances tab, then click a specific instance in the Instance ID list.

   The Flow Trace page displays the following details:

   • The Faults section shows the faults occurring in the services, service components, and references that comprise the SOA composite application. Sensors enable you to monitor BPEL process activities, variables, and faults during run time. Selecting a fault highlights the row in the Trace section in which the fault occurred. Closing the fault clears the selection in the Trace section.

   • The Sensors section displays details about composite sensors included in the service and reference binding components of the SOA composite application. The total number of sensors is shown in the section header. Composite sensors can be added to service and reference binding components during design time in Oracle JDeveloper. You cannot add composite sensors to service components. Selecting a composite sensor in this section highlights the service or reference in the Trace section in which composite sensor data was collected. Closing the sensor clears the selection in the Trace section.

     Note:

     Expand the Faults or Sensors sections one at a time. The fault or sensor information only displays for viewing in this way.

   • The Trace section shows the sequence of the message flow through the services, service components, and references that comprise the SOA composite application.

   The flow trace is a run-time trail of a message flow identified by an execution context ID (ECID) that displays in the upper right corner of the page. An ECID enables you to track a message flow that crosses instances of different composites. The flow trace lists all services, references, components across composites participating in the flow.

   
   Description of the illustration bp_compsensor3.gif
   
   

   For the flow example in the Trace section, the service binding component, Oracle Mediator service component, and reference binding component involved in the flow have successfully received and processed messages.

   Note the following restrictions with ECIDs:

   • A separate ECID displays 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.

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.

   
   Description of the illustration bp_compsensor1.gif
   
   

6. Select a sensor in the Sensors section.

   This highlights the row in the Trace section in which the composite sensor data was collected.

7. 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.

   
   Description of the illustration bpel_comp_audittrail.gif
   
   

   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 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 only displays 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 tab displays execution details about the activities in the BPEL process.

8. 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. This audit trail shows a fault in a BPEL process activity.

9. 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.

   
   Description of the illustration bpel_comp_flow1.gif
   
   

10. Click an activity to view the flow of the payload through the process.

    Note:

    If using Internet Explorer, you can click Copy details to clipboard to copy the activity details to the clipboard. If using Mozilla Firefox, this link does not appear. Instead, you must manually select the text and copy and paste it to a file.

11. Scroll through the flow diagram to check for errors and click the highlighted activity to view error messages.

    
    Description of the illustration bpel_comp_flow2.gif
    
    

12. Close the window.

13. Click the Faults tab.

    This tab shows the error message, whether you can recover from the fault, the time at which the fault occurred, and the activity in which the fault occurred. This page displays the faults in the BPEL component instance (but not the faults that occurred in a service or reference binding component).

    You can recover from instance faults identified as recoverable. This page lists all instance faults, recoverable or not. The component instance faults that occurred in a service or reference are not listed here.

    This page enables you to target individual faults from which to recover, and provides a degree of fault recovery granularity not available on other pages.

    
    Description of the illustration bpel_instancedetails_faults.gif
    
    

    However, you cannot perform bulk fault recoveries on this page. To perform bulk fault recovery, use one of the following pages:

    • Faults and Rejected Messages page of a specific SOA composite application or of the SOA Infrastructure

    • Faults page of the BPEL process service engine or of a specific BPEL process service component

14. Select a fault for recovery that has been identified as recoverable through one of the following methods. The page refreshes to display a fault recovery section at the bottom of the page.

    • If you click a fault in the Error Message column, a popup message displays details about the fault, including the fault ID, fault time, fault location, fault type, and complete error message text. If the fault is identified as recoverable, a Recover Now button displays that you can click.

    • You click a fault identified as recoverable in the Recovery column.

15. Select an action from the Recovery Action list.

    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	Aborts the entire instance.
    Replay	Replays the entire scope 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 faulting activity as a success).

    
    

    Your selection causes additional fields to appear. For example, the following fields display if you select Rethrow.

    
    Description of the illustration bpel_instancefaultrec2.gif
    
    

16. Use the After Successful Retry list to select defined actions to invoke after a successful retry. If you select a variable in the Variable list, you can edit the value in the Value text box.

17. Click the Back button of your browser to exit the flow diagram.

11.2 Monitoring BPEL Process Service Component Instances and Faults

You can monitor BPEL process service component recent instances and faults. Each service component in a SOA composite application has its own instance ID. These IDs are different from the overall instance ID of the SOA composite application of which each service component is a part.

To monitor BPEL process service component instances and faults:

1. Access this page through one of the following options:

   From the SOA Infrastructure Menu...	From the SOA Folder in the Navigator...
   Select Home. Select the Deployed Composites tab. In the Composite section, select a specific SOA composite application.	Under soa-infra, select a specific SOA composite application.

   
   

2. In the Component Metrics section, select the BPEL process service component.

3. Click Dashboard.

   The upper part of the Dashboard page displays the following details:

   • Recent instances of the BPEL process service component, including the instance ID, the state of the instance (for example, completed successfully or faulted), the start time, the last modification time, and logs describing the instance.

   • Recent faults in the BPEL process service component, including the error message, whether you can recover from the fault, the time at which the fault occurred, the instance ID of the BPEL service component, the BPEL activity in which the fault occurred, and logs describing the fault.

   • The average processing time for each activity in the BPEL process service component.

   
   Description of the illustration bpel_comp_dash_upper.gif
   
   

4. In the Recent Instances section, perform the following tasks:

   1. In the Instance ID column, click an instance ID for a service component to view its audit trail, process flow, sensor values, and faults.

   2. In the Logs column, click a specific log to access the Log Messages page with filtered messages specific to that instance.

   3. Click Show All below the section to access the Instances page of the service component.

5. In the Recent Faults section, perform the following tasks:

   1. In the Error Message column, click an error message to display complete information about the fault. If the fault is identified as recoverable, click the Recover Now link to perform fault recovery.

   2. In the Recovery column, click a fault identified as Recoverable to perform fault recovery at the component instance level.

   3. In the Logs column, click a specific log to access the Log Messages page with filtered messages specific to that instance.

   4. Click Show All below the section to access the Faults page of the service component.

   The lower part of the Dashboard page displays the following details:

   • A graphical representation of the number of successful, faulted, and incoming (pending) instances of the BPEL process service component over a specific time range.

   • The number of faults and message processed by any reference binding component with which this BPEL process service component communicated.

   
   Description of the illustration bpel_comp_dash_lower.gif
   
   

For more information, see Section 1.2.3, "Understanding SOA Composite Application Instances" and Oracle Fusion Middleware Administrator's Guide for details about viewing and searching log files.

11.3 Monitoring BPEL Process Service Component Instances

You can monitor BPEL process service component instances. Each service component has its own unique instance ID. This ID is in addition to the instance ID of the overall SOA composite application of which this service component is a part.

To monitor BPEL process service component instances:

1. Access this page through one of the following options:

   From the SOA Infrastructure Menu...	From the SOA Folder in the Navigator...
   Select Home. Select the Deployed Composites tab. In the Composite section, select a specific SOA composite application.	Under soa-infra, select a specific SOA composite application.

   
   

2. Select the BPEL process service component in the Component Metrics section.

3. Click Instances.

   The Instances page displays the following details:

   • A utility for searching for a specific BPEL service component instance by specifying a criteria and clicking Search.

   • BPEL process service component instances, including the instance ID, instance state (for example, completed or faulted), instance start time, last instance modification time, and log files describing the instance.

   
   Description of the illustration bpel_com_dash_instances.gif
   
   

4. In the Instance ID column, click an instance ID for a service component to view its audit trail, process flow, sensor values, and faults.

5. In the Logs column, click a specific log to access the Log Messages page with filtered messages specific to that instance.

For more information, see Section 1.2.3, "Understanding SOA Composite Application Instances."

11.4 Monitoring Sensor Data and Values in BPEL Process Service Components

You can view the fault, activity, and variable sensor data of a BPEL process service component. You design sensors in BPEL processes and trackable fields in Oracle JDeveloper. Sensors enable you to monitor BPEL process activities, variables, and faults during run time.

To monitor sensor data and values in BPEL process service components:

1. Access this page through one of the following options:

   From the SOA Infrastructure Menu...	From the SOA Folder in the Navigator...
   Select Home. Select the Deployed Composites tab. In the Composite section, select a specific SOA composite application.	Under soa-infra, select a specific SOA composite application.

   
   

2. Use one of the following methods to select an instance of the application:

   • For recent instances of this application, click the instance number of an instance in the Instance ID column of the Recent Instances section.

   • For all instances of this application, click the Instances tab, then click a specific instance in the Instance ID column.

   The Flow Trace page appears.

3. Click a specific BPEL process service component in the Instance column of the Trace section.

4. Click the Sensor Values tab.

5. Select a sensor to view details.

   If you created JMS sensors in your BPEL process, JMS sensor values do not display in Oracle Enterprise Manager Fusion Middleware Control Console. Only sensor values in which the sensor action is to store the values in the database appear (for example, database sensor values).

   
   Description of the illustration bpel_comp_sen.gif
   
   

   For more information about sensors, see Oracle Fusion Middleware Developer's Guide for Oracle SOA Suite.

11.5 Monitoring BPEL Process Service Engine Instances and Faults

You can monitor instances and faults of all BPEL process service components running in the BPEL process service engine. These BPEL process service components can be part of separate SOA composite applications.

To monitor BPEL process service engine instances and faults:

1. Access this page through one of the following options:

   From the SOA Infrastructure Menu...	From the SOA Folder in the Navigator...
   Select Service Engines > BPEL.	Right-click soa-infra. Select Service Engines > BPEL.

   
   

2. Click Dashboard.

   The upper part of the Dashboard page displays recent instances of all BPEL process service components running in the BPEL process service engine, including the instance ID of the service component, the service component name, the SOA composite application of which the service component is a part, the state of the instance (for example, completed successfully or faulted), the instance start time, the last modification time, and logs describing the instance.

   
   Description of the illustration bpel_dashboard_upper.gif
   
   

3. In the Recent Instances section, perform the following monitoring tasks:

   1. In the Instance ID column, click an instance ID for a service component to view its audit trail, process flow, sensor values, and faults.

   2. In the Component column, click a specific service component to access its home page.

   3. In the Composite column, click a specific SOA composite application to access its home page.

   4. In the Logs column, click a specific log to access the Log Messages page with filtered messages specific to that instance.

   5. Click Show All below the section to access the Instances page of the service engine.

   The lower part of the Dashboard page displays the following details:

   • The service components running in the service engine, the SOA composite applications of the service components, the state of the applications (for example, running), and the total, running, and faulted instances in the service engine.

   • The recent faults in the service engine, including the error message, whether you can recover from the fault, the time at which the fault occurred, the SOA composite application in which the fault occurred, the service component, the instance ID of the service component, the activity in which the fault occurred, and log files describing the fault.

   
   Description of the illustration bpel_dashboard_low.gif
   
   

4. In the Components section, perform the following tasks:

   1. In the Name column, click a specific service component to access its home page.

   2. In the Composite column, click a specific SOA composite application to access its home page.

   3. Click Show All below the section to access the Deployed Components page of the service engine.

5. In the Recent Faults section, perform the following tasks:

   1. In the Error Message column, click an error message to display complete information about the fault. If the fault is identified as recoverable, click the Recover Now link to perform fault recovery.

   2. In the Recovery column, click a fault identified as Recoverable to perform fault recovery at the component instance level.

   3. In the Composite column, click a specific SOA composite application to access its home page.

   4. In the Component column, click a specific service component to access its home page.

   5. In the Component Instance ID column, click an instance ID for a service component to view its audit trail, process flow, sensor values, and faults.

   6. In the Logs column, click a specific log to access the Log Messages page with filtered messages specific to that fault.

For more information, see Section 1.2.4, "Understanding Service Components and Service Component Instances."

11.6 Monitoring BPEL Process Service Engine Request and Thread Statistics

You can monitor request and thread statistics for all BPEL process service components running in the service engine.

To monitor BPEL process service engine request and thread statistics:

1. Access this page through one of the following options:

   From the SOA Infrastructure Menu...	From the SOA Folder in the Navigator...
   Select Service Engines > BPEL.	Right-click soa-infra. Select Service Engines > BPEL.

   
   

2. Click Statistics.

   The upper part of the Statistics page displays the following details. Click the Help icon for additional details.

   • Pending requests in the service engine

   • Active requests in the service engine

   • Thread statistics for the service engine

   
   Description of the illustration bpel_stats_upper.gif
   
   

   The lower part of the Statistics page displays details about the count and minimum, maximum, and average request processing times.

   
   Description of the illustration bpel_stats_lower.gif
   
   

11.7 Monitoring BPEL Process Service Engine Instances

You can monitor all BPEL process service component instances running in the service engine. These BPEL process service components can be part of separate SOA composite applications.

To monitor BPEL process service engine instances:

1. Access this page through one of the following options:

   From the SOA Infrastructure Menu...	From the SOA Folder in the Navigator...
   Select Service Engines > BPEL.	Right-click soa-infra. Select Service Engines > BPEL.

   
   

2. Click Instances.

   The Instances page displays the following details:

   • A utility for searching for a specific instance by specifying a criteria and clicking Search.

   • Instances, including the instance ID of the service component, the service component name, the SOA composite application name, the state of the instance (for example, completed successfully, running, or faulted), the instance start time, the last modification time, and log files describing the instance.

   
   Description of the illustration bpel_instances.gif
   
   

3. In the Instances section, perform the following monitoring tasks:

   1. In the Instance ID column, click an instance ID for a service component to view its audit trail, process flow, sensor values, and faults.

   2. In the Component column, click a specific service component to access its home page.

   3. In the Composite column, click a specific SOA composite application to access its home page.

   4. In the Logs column, click a specific log to access the Log Messages page with filtered messages specific to that instance.

For more information, see Section 1.2.4, "Understanding Service Components and Service Component Instances."

11.8 Monitoring Deployed BPEL Processes in the Service Engine

You can monitor all deployed SOA composite applications with BPEL process service components running in the service engine.

To monitor deployed BPEL processes in service engines:

1. Access this page through one of the following options:

   From the SOA Infrastructure Menu...	From the SOA Folder in the Navigator...
   Select Service Engines > BPEL.	Right-click soa-infra. Select Service Engines > BPEL.

   
   

2. Click Deployed Components.

   The Deployed Components page displays the following details:

   • A utility for searching for a specific deployed SOA composite application by specifying a criteria and clicking Search.

   • Details about deployed SOA composite applications with BPEL process service components running in this service engine, including the service component name, the SOA composite application, the current status, and the total, running, and faulted instances in the service engine.

   
   Description of the illustration bpel_se_deployedcomps.gif
   
   

3. In the Name column, click a specific service component to access its home page.

4. In the Composite column, click a specific SOA composite application to access its home page.