Starting and Stopping a Managed Oracle WebLogic Server

Managing SOA Composite Applications 8-19

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

the instance of the SOA composite application revision is contained.

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

10. In the Instances table, perform the following additional tasks:

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

flow through the various service components and binding components. If an instance ID is listed as unavailable, you can click the Unavailable link for details.

b. In the State column, if an instance state is marked as Unknown, click it to

display more details.

c. If the Composite Sensors column is available, click a sensor icon to display

details about composite sensors included in the instance, such as name, location, and value.

d. In the Logs column, click a specific log to access the Log Messages page with

filtered messages specific to that instance. Delete With Options Prompts you to first specify criteria for deleting the selected instance directly from the database: ■ Common Delete Options : Select a preset range of instances to delete from a list for example, older than 24 hours. ■ Delete All Instances Of This Composite : Select to delete all instances of the composite. This option deletes the rejected messages associated and all component, service, and reference instances associated with the composite, including those not associated with any composite instance ID. Note: If this composite has thousands of instances to delete, do not use this option. Instead, use the purge script described in Section 9.3, Deleting Large Numbers of Instances with the Purge Scripts. ■ Delete All Instances That Match These Criteria : Specify criteria for deleting instances, including the start and stop times, and instance state. Any selections you may have made in the Instances page such as specifying and executing a search criteria are ignored for this operation. To monitor the progress of instance deletion, you must check the log files. For information about log files, see Section 3.4, Configuring Log Files. Abort Terminates the selected instance. However, instance details are still available for review. Note: Multiple revisions of a SOA composite application that includes inbound JCA adapters are displayed as running. However, only the most recent revision the default version is considered active. All previous revisions are not considered active. This is because for inbound JCA adapters, there can only be one active revision of a SOA composite application at any time. The JCA adapter end points in all previous revisions are de-activated. Action Description 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