Monitoring and Deleting SOA Composite Application Instances from the Application Home Page

8-20 Oracle Fusion Middleware Administrators Guide for Oracle SOA Suite and Oracle BPM Suite For more information, see the following sections: ■ Section 1.2.3, Introduction to SOA Composite Application Instances ■ Section 1.4.3.3, Introduction to the Lifecycle State of SOA Composite Applications ■ Section 8.1, Initiating a SOA Composite Application Test Instance ■ Oracle Fusion Middleware Administrators Guide for details about viewing and searching log files 8.3.1 Mismatch Between the Number of SOA Composite Application Instances and Service Component Instances The number of SOA composite application instances may not always match the number of service component instances displayed in Oracle Enterprise Manager Fusion Middleware Control. A SOA composite application instance is first created when the composite is invoked. When the service components within the composite receive a subsequent invocation, a corresponding service component instance is created that refers to the composite instance ID previously created. There can be scenarios under which the composite instance is created, but the underlining service component instance is not created. For example: ■ The composite instance is created, but the invocation has not yet reached the service component due to a system failure. ■ The composite instance is created, but the invocation fails payload validation and is rejected. In this case, invocation does not reach the underlining service components. You can also have orphaned service component instances for which no SOA composite application instance has been created.

8.3.2 Instance States of Service Components and SOA Composite Applications

Assume you have a SOA composite application with multiple service components for example, two BPEL process service components. If these service components are marked with the following instance states: ■ Instance state of one BPEL process is marked as completed. ■ Instance state of the other BPEL process is marked as faulted. This results in the overall composite instance state being marked as faulted. This behavior differs from 11g Release 1 11.1.1.2, in which the same scenario resulted in the overall composite instance state being marked as completed. Assume you have a parent SOA composite application that calls a child SOA composite application, and a fault occurs in the child composite and is handled by the parent composite. This results in the following instance states: ■ The instance state of the child composite is marked as faulted. ■ The instance state of the parent composite is marked as completed.

8.3.3 Setting the Composite Instance Name at Design Time

You can set the instance name of a SOA composite application during design time in Oracle Mediator and Oracle BPEL Process Manager. The instance name appears in the Managing SOA Composite Applications 8-21 Name column on the Instances page of a SOA composite application. When you specify a search criteria on the Instances page of a SOA composite application or the SOA Infrastructure, you can specify this name in the Name field.

8.3.3.1 Setting the Composite Instance Name in Oracle Mediator

To set the composite instance name in Oracle Mediator:

1. Set the composite instance name through one of the following options:

■ Use the setCompositeInstanceTitletitle XPath expression function as the source and tracking.compositeInstanceTitle as the target property name in the Assign Value dialog. ■ Use the setCompositeInstanceTitletitle XPath expression function in the XSLT Mapper.

8.3.3.2 Setting the Composite Instance Name in a BPEL Process

To set the composite instance name in a BPEL process:

1. Use the Java BPEL exec extension bpelx:exec. This extension includes the

built-in method setCompositeInstanceTitleString titlefor setting the instance name. 8-22 Oracle Fusion Middleware Administrators Guide for Oracle SOA Suite and Oracle BPM Suite For more information, see Oracle Fusion Middleware Developers Guide for Oracle SOA Suite.

8.4 Monitoring and Deleting SOA Composite Application Instances at the SOA Infrastructure Level

Section 8.2, Managing the State of Deployed SOA Composite Applications described how to manage the lifecycle state of all instances of a specific SOA composite application. You can also monitor and delete any number of instances across all deployed SOA composite applications by using the Instances page of the SOA Infrastructure home page. This page lists all SOA composite application instances deployed to the SOA Infrastructure. To monitor and delete SOA composite application instances at the SOA infrastructure level: 1. Access this page through one of the following options:

2. Click the Instances tab.

The Instances page displays the following details: ■ A utility for searching for a specific instance by specifying criteria and clicking Search . ■ All SOA composite application instances in the SOA Infrastructure, including instance and conversation IDs, composite name and revision, SOA composite application instance state, and instance start time. You can also terminate and delete instances from this page. From the SOA Infrastructure Menu... From the SOA Folder in the Navigator... From the SOA Composite Menu... 1. Select Home. 1. Click soa-infra. 1. Select SOA infrastructure. Managing SOA Composite Applications 8-23

3. Select a specific instance by clicking a row in the Instances table. To select multiple

instances, press Ctrl-Click or Shift-Click for the rows you want to select. 4. Select a specific action to perform.

5. From the View list, select Columns Partition to display the partition in which

the instance of the SOA composite application revision is contained.

6. From the View list, select Columns ECID to display execution context IDs

ECIDs. An ECID enables you to track a message flow that crosses instances of different composites.

7. In the Instance ID column, click a specific instance ID to show the message flow