Binding Components Service Component Architecture within SOA Composite Applications

1-6 Oracle Fusion Middleware Developers Guide for Oracle SOA Suite

1.5.3 Wires

Wires enable you to graphically connect the following components in a single SOA composite application for message communication: ■ Services to service components ■ Service components to other service components ■ Service components to references

1.6 Runtime Behavior of a SOA Composite Application

Figure 1–2 shows the operability of a SOA composite application using SCA technology. In this example, an external application a .NET payment calculator initiates contact with the SOA composite application. For more information about descriptions of the tasks that services, references, service components, and wires perform in an application, see Section 1.5, Service Component Architecture within SOA Composite Applications. Figure 1–2 Runtime Behavior of SOA Composite Application The .NET payment calculator is an external application that sends a SOAP message to the SOA application to initiate contact. The Service Infrastructure picks up the SOAP message from the binding component and determines the intended component target. The BPEL process service engine receives the message from the Service Infrastructure for processing by the BPEL Loan Process application and posts the message back to the Service Infrastructure after completing the processing. Table 1–2 describes the operability of the SOA composite application shown in Figure 1–1 . BPEL Process Manager Business Rules Oracle Mediator Human Task BAM B2B JCA Adapters Loan Process APR Rule Manager Review Task EBS Customer View Service Archive: Composite deployment unit ADF BC HTTP SOAP .NET Payment Calculator UDDI MDS Sends a SOAP message to the SOA application Service Engines Containers that host the component business logic Service Infrastructure Picks up SOAP message from binding component and determines the intended component target Binding Components Connect SOA applications to the outside world Introduction to Building Applications with Oracle SOA Suite 1-7

1.6.1 Service Infrastructure

The Service Infrastructure provides the following internal message routing infrastructure capabilities for connecting components and enabling data flow: ■ Receives messages from the service providers or external partners through SOAP services or adapters ■ Sends the message to the appropriate service engine ■ Receives the message back from the service engine and sends it to any additional service engines in the composite or to a reference binding component based on the wiring Table 1–2 Introduction to a SOA Composite Application Using SCA Technologies Part Description Example of Use in Figure 1–1 See Section Binding components Establishes the connectivity between a SOA composite and the external world. There are two types: ■ Service binding components provide an entry point to the SOA composite application. ■ Reference binding components enable messages to be sent from the SOA composite application to external services. The SOAP binding component service: ■ Advertises its capabilities in the WSDL file. ■ Receives the SOAP message from the .NET application. ■ Sends the message through the policy infrastructure for security checking. ■ Translates the message to a normalized message an internal representation of the service’s WSDL contract in XML format. ■ Posts the message to the Service Infrastructure. An example of a binding component reference in Figure 1–2 is the Loan Process application. Section 1.5.1, Service Components Service Infrastructure Provides internal message transport The Service Infrastructure: ■ Receives the message from the SOAP binding component service. ■ Posts the message for processing to the BPEL process service engine first and the human task service engine second. Section 1.6.1, Service Infrastructure Service engines containers hosting service components Host the business logic or processing rules of the service components. Each service component has its own service engine. The BPEL service engine: ■ Receives the message from the Service Infrastructure for processing by the BPEL Loan Process application. ■ Posts the message to the Service Infrastructure after completing the processing. Section 1.6.2, Service Engines UDDI and MDS The MDS Metadata Service repository stores descriptions of available services. The UDDI advertises these services, and enables discovery and dynamic binding at runtime. The SOAP service used in this composite application is stored in the MDS repository and can also be published to UDDI. Oracle Fusion Middleware Getting Started with Oracle SOA Suite SOA Archive: Composite deployment unit The deployment unit that describes the composite application. The SOA archive SAR of the composite application is deployed to the Service Infrastructure. Section 1.6.3, Deployed Service Archives