Introduction to Service Components and Service Component Instances

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. 1-10 Oracle Fusion Middleware Administrators Guide for Oracle SOA Suite and Oracle BPM Suite ■ Part VIII, Administering Human Task Service Components and Human Workflow Service Engines ■ Part XV, Administering Oracle BPMN Process Service Components and Engines

1.2.5 Introduction to Binding Components

Binding components connect SOA composite applications to external services, applications, and technologies such as messaging systems or databases. Binding components are organized into two groups: ■ Services: Provide the outside world with an entry point to the SOA composite application. The WSDL file of the service advertises its capabilities to external applications. The service bindings define how a SOA composite service can be invoked for example, through SOAP. ■ References: Enable messages to be sent from the SOA composite application to external services for example, the same functionality that partner links provide for BPEL processes, but at the higher SOA composite application level. In Oracle Enterprise Manager Fusion Middleware Control, you can perform binding component administration tasks such as attaching policies, monitoring rejected messages, and setting binding component properties. Figure 1–8 shows the home page of a service binding component in this example, a JCA adapter. Figure 1–8 Binding Components For more information, see Section XIV, Administering Binding Components.

1.2.6 Introduction to Service Engines

The SOA Infrastructure includes a set of service engines BPEL process, human workflow, decision service, Oracle mediator, and spring that execute the business logic of their respective components within the SOA composite application for Introduction and Concepts 1-11 example, a BPEL process. If Oracle BPM Suite is installed, the SOA Infrastructure also includes the BPMN process service engine. Figure 1–9 provides an example in Oracle Enterprise Manager Fusion Middleware Control of the BPEL process service engine. In this service engine, the Calling, LoanService , and CreditRatingService BPEL process service components run. Note the multiple instance IDs for LoanService and CreditRatingService. The BPEL process service components are included in two separate SOA composite applications: ■ Calling is included in the Calling SOA composite application. ■ LoanService and CreditRatingService are included in the CompositeTest SOA composite application. However, each BPEL process service component runs in the same BPEL process service engine. You can click the links on the page to see more details about each BPEL process service component instance, the service component itself, or the SOA composite application in which it is included. Figure 1–9 Service Components Running in a Service Engine In Oracle Enterprise Manager Fusion Middleware Control, you can perform service engine administration tasks such as monitoring instances, recovering from faults, manually recovering BPEL failed messages, and configuring properties specific to a service engine. These configuration properties impact all service components that execute in the service engine, no matter the SOA composite application in which the service components are included. The service engine pages also include service engine-specific statistics and performance metrics. For more information about administering service engines, 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 ■ Part VIII, Administering Human Task Service Components and Human Workflow Service Engines ■ Part XV, Administering Oracle BPMN Process Service Components and Engines