Introduction to SOA Composite Applications

Introduction and Concepts 1-5 interfaces into SOA composite applications, and decision services for working with business rules. ■ Binding components services and references for connecting SOA composite applications to external services, applications, and technologies. These components are assembled into a single SOA composite application. Having the components assembled into one unit of deployment the application greatly simplifies the management and lifecycle of SOA applications. Figure 1–4 provides an example of a SOA composite application in the SOA Composite Editor in Oracle JDeveloper. Service binding components such as orderprocessor_client_ep advertise their capabilities to external consumers. The service exposes a public interface of the SOA composite application OrderBookingComposite consisting of BPEL process, Oracle Mediator, human task, and decision service components. A wire connects the service to a specific component or reference in the composite. Reference binding components such as CreditCardAuthorizationService and PartnerSupplierService enable messages to be sent from the SOA composite application to external services. The service binding components, service components, and reference binding components are wired connected for communication. 1-6 Oracle Fusion Middleware Administrators Guide for Oracle SOA Suite and Oracle BPM Suite Figure 1–4 SOA Composite Application Introduction and Concepts 1-7 The service components and binding components included in a SOA composite application appear in the lower part of an application home page, as shown in Figure 1–3 and Figure 1–5 . The example in Figure 1–5 shows two service components in the Component Metrics section and three binding components in the Services and References section. You can click a specific service component or binding component to access its home page. Figure 1–5 Service Components and Binding Components of a SOA Composite Application For more information, see the following documentation: ■ Section 1.2.4, Introduction to Service Components and Service Component Instances ■ Section 1.2.5, Introduction to Binding Components ■ Part IV, Administering SOA Composite Applications ■ Oracle Fusion Middleware Developers Guide for Oracle SOA Suite

1.2.3 Introduction to SOA Composite Application Instances

When a SOA composite application is invoked, a new composite instance is created. This instance is identified by a unique instance ID that is displayed in pages of Oracle Enterprise Manager Fusion Middleware Control. For example, Figure 1–6 shows instance IDs displayed for SOA composite applications in the Instances page of the SOA Infrastructure. You can click these IDs to access more specific details about the state of SOA composite application instances. From the Instances page, you can also monitor the state of SOA composite application instances. Instances that you create as unit tests from the Test Runs page are distinguished from those created automatically or created manually from the Test Web Service page by a little yellow box. This box is displayed to the left of the instance ID, as shown in Figure 1–6 . This box is visible in both the Instances page and in the Recent Instances table of the Dashboard page of the SOA Infrastructure and SOA composite application. For some SOA composite applications, conversation IDs are also generated. Conversation IDs provide another method for distinctly identifying a set of generated instances. As shown in Figure 1–6 , conversation IDs are not automatically displayed for all instances. To see a conversation ID generated, perform one of the following tasks: ■ Programatically invoke the service and pass a unique ID through a WS-Addressing header messageId. 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