Oracle SOA Composite Overview

Adapter Integration with Oracle Application Server Components 3-13 ■ Binding Components The binding component establishes the connectivity between a SOA composite and the external world. There are two types of binding components: – Service Binding Components Provide the outside world with an entry point to the SOA composite application. The WSDL file of the service informs external applications of its capabilities. 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, Oracle JCA adapter. – Reference Binding Components Enable messages to be sent from the SOA composite application to external services in the outside world. The Oracle SOA Suite provides Web Services, such as Oracle JCA adapters 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 Oracle AQ Adapter, Oracle Database Adapter, Oracle File Adapter, Oracle FTP Adapter, Oracle JMS Adapter, Oracle MQ Series Adapter, and Oracle Socket Adapter. ■ Service Infrastructure Provides internal message transport. For example, receives the message from an inbound adapter and posts the message for processing to the BPEL process service engine. ■ 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. For example, an Oracle BPEL process engine or an Oracle Mediator Component. For more information about adapter integration with service engines, see Section 3.2, Adapter Integration with Oracle Fusion Middleware. ■ UDDI and MDS The MDS Metadata Service repository stores descriptions of available services. The UDDI advertises these services and enables discovery as well as dynamic binding at run time. ■ SOA Archive: Composite The deployment unit that describes the composite application. A composite is an assembly of services for example, inbound adapters, service components, wires, and references for example, outbound adapters designed and deployed together in a single application. The composite processes the information described in the messages. A composite.xml file is automatically created when you create a SOA project. This file describes the entire composite assembly of services, service components, references, and wires. The composite.xml file describes the entire SOA composite. The following is a sample composite.xml file: Composite.xml JCA Bindings?xml version=1.0 encoding=UTF-8 ? -- Generated by Oracle SOA Modeler version 1.0 at [22309 3:02 PM]. -- composite name=MediatorFlatStructure revision=1.0