Monitoring Deployed BPEL Processes in the Service Engine

Managing BPEL Process Service Components and Engines 13-3

5. Select an action from the Recovery Action list.

6. Perform the following additional monitoring tasks from within the faults table:

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

which you can recover.

b. From the Fault Type list, select to display all faults, system faults, business

faults, or Oracle Web Services Manager 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. Bulk fault recovery There are two options from which to choose for bulk-fault recovery: 1. Use Shift+Click or Control+Click to select specific faults in the rows. or 2. From the Select menu, choose Select All Recoverable. Then use Shift+Click or Control+Click to deselect the faults to not include in the recovery operation. Then: 3. Select an action from the Recovery Action list, as described in Step 5. Note: Only the actions applicable to all selected faults are available. Recovery of all faults 1. From the Select menu, choose Select All Recoverable. 2. Select an action from the Recovery Action list, as described in Step 5. Note: Only the actions applicable to all selected faults are available. Note: In most cases, fault policy actions are automatically executed. The only exception is if you defined a fault policy that uses the action ora-human-intervention. This action creates a recoverable fault that can be recovered from Oracle Enterprise Manager Fusion Middleware Control. Action Description Retry Retries the instance directly. 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 Terminates the entire instance. Replay Replays the entire scope activity 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 faulted activity as a success. For... Then... 13-4 Oracle Fusion Middleware Administrators Guide for Oracle SOA Suite and Oracle BPM Suite

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

e. In the Logs column, click a link to access the Log Messages page with filtered

messages specific to that instance. For more information, see the following documentation: ■ Section 1.4.3.1, Introduction to Fault Recovery ■ Section 8.5.1, Examples of Fault Recovery for BPEL Processes ■ Oracle Fusion Middleware Developers Guide for Oracle SOA Suite ■ Oracle Fusion Middleware Administrators Guide for details about viewing and searching log files

13.2 Managing BPEL Process Service Component Policies

You can attach and detach policies to and from BPEL process service components in currently deployed SOA composite applications. Policies apply security to the delivery of messages. Oracle Fusion Middleware uses a policy-based model to manage web services. To manage BPEL process service component policies: 1. Access this page through one of the following options:

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

3. Click Policies.

The Policies page enables you to attach and detach policies to and from BPEL process service components. The Policies section displays the attached policy name, the policy reference status enabled or disabled that you can toggle, the category Management, Reliable Messaging, MTOM Attachment, Security, or WS-Addressing, the violations, and the authentication, authorization, confidentiality, and integrity failures since the SOA Infrastructure was last restarted. Note: Before attaching policies, see Oracle Fusion Middleware Security and Administrators Guide for Web Services for definitions of available policies and details about which ones to use in your environment. From the SOA Infrastructure Menu... From the SOA Folder in the Navigator... 1. Select Home. 2. Select the Deployed Composites tab. 3. In the Composite section, select a specific SOA composite application. 1. Under soa-infra, select a specific SOA composite application. Managing BPEL Process Service Components and Engines 13-5

4. Click AttachDetach.

If multiple components are available, you are prompted to select the service or component for which to perform the attachment or detachment. 5. Select the service or component to which to attach or detach a policy. This invokes a dialog for attaching or detaching policies. Policies currently attached appear in the Attached Policies section. Additional policies available for attachment appear in the Available Policies section. 6. Select to attach policies appropriate to your environment.

7. Click Attach.

8. When you are finished attaching policies, click Validate.

9. If an error message appears, make the necessary corrections until you no longer have any validation errors.

10. Click OK.

The attached policy is displayed in the policies table. For more information, see the following documentation: ■ Section 1.4.3.2, Introduction to Policies ■ Section 8.8, Managing SOA Composite Application Policies for the dialogs that are displayed during policy attachment ■ Oracle Fusion Middleware Security and Administrators Guide for Web Services for definitions of available policies and details about which ones to use for your environment

13.3 Recovering from BPEL Process Service Engine Faults

You can monitor and perform individual and bulk recoveries of faults occurring in BPEL process service engines that are identified as recoverable. All BPEL process service component faults, regardless of the SOA composite application instance of which they are a part, can be viewed in the BPEL process service engine. For BPEL process faults to be identified as recoverable, there must be a fault policy defined that is bound to the fault through the fault-bindings.xml file and which triggers the action ora-human-intervention. However, without defining any fault policies, the fault takes its standard course as either a recoverable or nonrecoverable fault. To recover from BPEL process service engine faults: 13-6 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 Faults.

The Faults page displays the following details: ■ A utility for searching for a specific fault by specifying criteria and clicking Search . Click the Help icon for details. ■ Faults that occurred in the service engine, including the fault ID, error message, whether you can recover from the fault, the time at which the fault occurred, the SOA composite application and service component in which the fault occurred, and the service component instance ID. BPEL process service engine faults identified as recoverable can be recovered. 3. Select faults for recovery using one of the following options. As with fault recovery at the SOA Infrastructure level, SOA composite application level, and Oracle Mediator service component level, you can perform single fault recovery, bulk fault recovery, and recovery of all faults. See Step 4 of Section 13.1, Recovering from BPEL Process Service Component Faults