Composite services use native interfaces as building blocks to construct the sequence of business flows. Basically, this interface type orchestrates the invocation sequence of Web services into a meaningful end-to-end business process through a Web service composition language BPEL (business process execution language). For example, use BPEL component in Oracle JDeveloper to integrate the Order to Receipt business process that contains sales order entry, item availability check, pack and ship, and invoice to Accounts Receivable subprocesses handled by various applications. This approach effectively tightens up the control of each individual process and makes the entire business flow more efficiently.
A composite service has its own WSDL definition and service endpoints allowing external Web service clients to invoke the services at run time.
Please note that in Oracle SOA Suite 11g, BPEL process is managed and deployed together with the associated SOA composite application. In Oracle SOA Suite 10g, it is developed and deployed as a separate component. Integration Repository displays 'Composite Services - BPEL' of Oracle SOA Suite 10g as catalogue in this release.
For information on how to create and administer composite services - BPEL, see the Oracle E-Business Suite Integrated SOA Gateway Developer's Guide and the Oracle E-Business Suite Integrated SOA Gateway Implementation Guide for details.
Additional Information: Since composite interfaces can be designed and created in Oracle JDeveloper and Oracle Eclipse, based on the different creation methods, composite interfaces can have various composite types such as BPEL, ESB (enterprise service bus), or SCA (service component architecture) types. However, composite - BPEL is the only composite interface type supported in this release.