Introduction to the Order of Precedence for Audit Level Settings

Introduction and Concepts 1-15 For more information, see the following sections: ■ Chapter 3, Configuring the SOA Infrastructure ■ Section 11.1, Configuring BPEL Process Service Engine Properties ■ Section 11.5, Setting the Audit Level at the BPEL Process Service Component Level No property Inherit Development Production Service engine. The audit level is set to Development . The payload is shown in the assign activity. The SOA Infrastructure audit level does not take effect. No property Inherit Inherit Production SOA Infrastructure. The audit level is set to Production . No property Inherit Production Development OffInherit Off The overall audit is not shown. The composite inherits the audit level from the SOA Infrastructure. The payload is shown in the assign activity based on the service engine audit level setting. Development Off Production Development Composite. Since the composite audit level is set to Off, the overall audit is not shown. The service engine audit level is shown, but the Development setting for the component takes precedence. The payload is shown in the assign activity based on the component audit level setting of Development . Inherit Off Production Development Composite. Since the composite audit level is set to Off, the overall audit is not shown. The service engine audit level is not shown because Off is inherited from the composite. Notes: ■ When the composite audit level is set to Off, there is no audit trail generated for this composite and all service engines used within the composite. ■ When the composite audit level is set to Inherit, it always inherits the settings of the SOA Infrastructure. ■ When the composite audit level is set to Off, the component inherits the service engine settings. Table 1–1 Cont. Examples of Order of Precedence Component Composite Service Engine SOA Infrastructure Which Setting Takes Precedence? 1-16 Oracle Fusion Middleware Administrators Guide for Oracle SOA Suite and Oracle BPM Suite ■ Chapter 19, Configuring Human Workflow Service Components and Engines ■ Chapter 33, Configuring Service and Reference Binding Components ■ Section 36.1, Configuring BPMN Process Service Engine Properties

1.4.2 Monitoring of Oracle SOA Suite and Oracle BPM Suite

You can perform Oracle SOA Suite and Oracle BPM Suite monitoring tasks in Oracle Enterprise Manager Fusion Middleware Control, including monitoring the following: ■ Instances, faults, and rejected messages in the SOA Infrastructure, SOA composite applications, service components, service engines, and service and reference binding components ■ Service engine, service infrastructure, and binding component processing request performance ■ Service and reference binding component message processing totals and average processing times ■ Audit trail and process flow behavior in service components. For BPMN processes, the entire BPMN process flow is displayed, and the path taken by the process instance is highlighted. ■ Service engine request and thread states in BPEL processes, BPMN processes, and human workflows

1.4.3 Management of Oracle SOA Suite and Oracle BPM Suite

You can perform Oracle SOA Suite and Oracle BPM Suite management tasks in Oracle Enterprise Manager Fusion Middleware Control, including managing the following: ■ Creation and deletion of partitions. Once you create partitions, you can deploy a composite to the appropriate partition. This action enables you to logically group SOA composite applications into partitions. This is similar to the concept of domains in the 10.1.x releases of Oracle BPEL Process Manager. ■ Composite state activating, retiring, starting, stopping, and setting the default composite version ■ Deletion and termination of composite instances ■ Deployment, undeployment, and redeployment actions for SOA composite applications ■ Export of a running SOA composite application to a JAR file. ■ Manual initiation of SOA composite application test instances from the Test Web Service page ■ Recovery from faults in SOA composite applications, service components, service engines, and business events ■ Manual recovery of failed messages in BPEL processes ■ Automated unit testing of SOA composite applications ■ Attachment of policies to SOA composite applications, service components, and binding components ■ Incoming and outgoing notification messages in human workflow ■ Subscriptions to business events and testing of event publications Introduction and Concepts 1-17 ■ Publication of web services to the Universal Description, Discovery, and Integration UDDI registry ■ Disabling of business monitors BPEL sensors, BPEL monitors, and BPMN measurements The following sections provide a more specific overview of several management tasks: ■ Section 1.4.3.1, Introduction to Fault Recovery ■ Section 1.4.3.2, Introduction to Policies ■ Section 1.4.3.3, Introduction to the Lifecycle State of SOA Composite Applications ■ Section 1.4.3.4, Introduction to SOA Composite Application Automated Testing ■ Section 1.4.3.5, Introduction to Partitioning of the SOA Infrastructure

1.4.3.1 Introduction to Fault Recovery

You can perform fault recovery actions on BPEL process, BPMN process, Oracle Mediator, human workflow, and business event subscription faults which include database and component subscription faults identified as recoverable in Oracle Enterprise Manager Fusion Middleware Control. The following types of fault recovery are supported: ■ Recovery from individual faults, where you have access to the most granular recovery options specific to each type of fault ■ Recovery from multiple bulk faults, where you select multiple faults for recovery You can perform individual and bulk recovery actions on recoverable faults at the following levels: ■ Faults occurring in all SOA composite applications in the SOA Infrastructure ■ Faults occurring in an individual SOA composite application ■ Faults occurring in service components ■ Faults occurring in service engines ■ Faults occurring in business events You perform fault recovery on faults identified as recoverable in Oracle Enterprise Manager Fusion Middleware Control. 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. A BPEL component fault can be recovered in only this case. If no fault policy is defined as part of the composite, then a recoverable BPEL process fault is not possible. You define a fault recovery policy in the fault-policies.xml and fault-bindings.xml files outside of Oracle Enterprise Manager Fusion Middleware Control. These files are packaged with the SOA composite application that you deploy to the SOA Infrastructure and administer in Oracle Enterprise Manager Fusion Middleware Control. Oracle Mediator and human workflow faults do not have the same behavior; they can create recoverable faults without any fault policy. For errors in human task service Note: Backup and recovery of Oracle SOA Suite is described in Oracle Fusion Middleware Administrators Guide.