Introduction to SOA Composite Application Instances

1-8 Oracle Fusion Middleware Administrators Guide for Oracle SOA Suite and Oracle BPM Suite ■ Create an instance using the Test Web Service page. The only exception to this is when the Enable Stress Test checkbox of the Additional Test Options section of the Test Web Service page is selected. In that case, a conversation ID is not created for the instance. Figure 1–6 SOA Composite Application Instance IDs For more information, see the following sections: ■ Section 1.2.4, Introduction to Service Components and Service Component Instances ■ Part IV, Administering SOA Composite Applications ■ Section 8.1, Initiating a SOA Composite Application Test Instance

1.2.4 Introduction to Service Components and Service Component Instances

SOA composite applications include service components. Service components are the basic building blocks of SOA composite applications. Service components implement a part of the overall business logic of the SOA composite application. The following service components can be used in a SOA composite application: ■ BPEL process: For process orchestration of synchronous and asynchronous processes ■ BPMN process if Oracle BPM Suite is installed: For creating and modeling business processes using Business Process Management Notation and Modeling BPMN ■ Oracle Mediator: For content transformation and routing events messages between service producers and consumers ■ Human task: For modeling a human task for example, manual order approval that describes the tasks for users or groups to perform as part of an end-to-end business process flow ■ Spring: For integrating Java interfaces into SOA composite applications Introduction and Concepts 1-9 ■ Decision service: For making a decision or for processing based on business rules From the service component home page in Oracle Enterprise Manager Fusion Middleware Control, you can perform administration tasks such as monitoring instances, recovering from faults, and attaching policies. As described in Section 1.2.3, Introduction to SOA Composite Application Instances, each application instance has its own instance ID. Each service component instance included in a SOA composite application instance also has its own instance ID that is displayed in Oracle Enterprise Manager Fusion Middleware Control. Figure 1–7 shows an instance ID workflow:200000 displayed in the Instance ID column for the VacationRequestTask human task service component of the VacationRequest SOA composite application. You can monitor the state of that service component instance from the Instances page. You can also click this instance to access more specific details about the service component. Figure 1–7 Service Component Instance IDs For more information about administering service components, see the following sections: ■ Part V, Administering BPEL Process Service Components and Engines ■ Part VI, Administering Oracle Mediator Service Components and Engines ■ Part VII, Administering Decision Service Components and Business Rules Service Engines Note: Oracle SOA Suite provides support for the spring service component. Note the following details about spring support in Oracle Enterprise Manager Fusion Middleware Control: ■ There are no spring service engine management pages. ■ A spring composite is displayed in the flow trace, but there is no audit trail for it. ■ Spring composite metrics are shown in the composite application home page for example, in the Component Metrics section of the Dashboard page.