Service Components Service Component Architecture within SOA Composite Applications

Introduction to Building Applications with Oracle SOA Suite 1-5 ■ Business rules enable you to design a business decision based on rules. ■ Human tasks provide workflow modeling that describes the tasks for users or groups to perform as part of an end-to-end business process flow. ■ Mediators route events messages between different components ■ Spring enables you to integrate Java interfaces into SOA composite applications

1.5.2 Binding Components

Binding components establish a connection between a SOA composite and the external world. There are two types of binding components: ■ 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. These capabilities are used for contacting the SOA composite application components. The binding connectivity of the service describes the protocols that can communicate with the service, for example, SOAPHTTP or a JCA adapter. ■ References enable messages to be sent from the SOA composite application to external services in the outside world. Table 1–1 lists and describes the binding components provided by Oracle SOA Suite. Table 1–1 Binding Components Provided by Oracle SOA Suite Binding Components Description Web service SOAP over HTTP Use for connecting to standards-based services using SOAP over HTTP. JCA adapters Use for integrating services and references with technologies for example, databases, file systems, FTP servers, messaging: JMS, IBM WebSphere MQ, and so on and applications Oracle E-Business Suite, PeopleSoft, and so on. This includes the AQ adapter, database adapter, file adapter, FTP adapter, JMS adapter, MQ adapter, and Socket adapter. B2B binding component Use for browsing B2B metadata in the MDS repository and selecting document definitions. ADF-BC service Use for connecting Oracle Application Development Framework ADF applications using SDO with the SOA platform. Oracle Applications Use for integrating the Oracle Applications adapter with Oracle applications. BAM adapter Use for integrating Java EE applications with Oracle BAM Server to send data, and also use as a reference binding component in a SOA composite application. EJB service Use for integrating SDO parameters or Java interfaces with Enterprise JavaBeans. Direct binding service Use to invoke a SOA composite application and exchange messages over a remote method invocation RMI in the inbound direction and to invoke an Oracle Service Bus OSB flow or another SOA composite application in the outbound direction. HTTP binding Use to integrate SOA composite applications with HTTP binding. 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