Application Programming Interfaces (APIs) are stored procedures that enable you to insert and update data in Oracle Applications. For example, using APIs, you can insert a customer record in Oracle Applications. The Oracle AS Adapter for Oracle Applications exposes the Oracle Applications API as a Service via WSDL with JCA binding. This tutorial describes how to invoke Oracle Application API interface and insert a customer record. The File Adapter read operation is used to read the customer record from a delimited file and trigger the BPEL process which inturn calls the create customer API in Oracle Applications.

This tutorial describes the steps needed to integrate the BPEL Process Manager with CICS through the Oracle AS Adapter for CICS. The Adapter uses EXCI (EXternal Call Interface) to invoke CICS transactions and uses COMMAREA transactions to exchange message buffers. The Adapter creates a metadata schema for CICS by importing COBOL copybooks and transforming them into mapping definitions for Oracle Connect for CICS on the OS/390 machine and by associating the data structures with specific physical files. The Adapter is also capable of receiving events from CICS. These steps are not covered as part of this tutorial.

The Oracle AS Adapter for SAP exposes the SAP BAPIs and RFCs as a Service via WSDL with JCA binding. This tutorial describes how to invoke a SAP BAPI interface and query the inverntory given Material ID. The BPEL process is a synchronous request-response service that invokes the SAP BAPI_MATPHYSINV_GETDETAIL API.

The Oracle AS Adapter for SAP exposes the SAP IDOC events as a Service via WSDL with JCA binding. This tutorial describes how to receive a SAP DEBMAS IDOC within a BPEL process. The BPEL process is an asynchronous service that is triggered by the arrival of a SAP DEBMAS event.

The Oracle AS Adapter for Siebel exposes the Siebel Business Object and Services as a Service via WSDL with JCA binding. This tutorial describes how to invoke a Siebel Account Business Object interface through a synchronous BPEL process.

The Oracle AS Adapter for Siebel exposes the Siebel events - Integration Objects as a Service. The Service is expressed as WSDL with JCA binding. This tutorial describes how to receive a Siebel Integration Object within a BPEL process. The BPEL process is an asynchronous service that is triggered by the arrival of a Siebel Integration Object.

The Oracle AS Adapter for Peoplesoft exposes the Peoplesoft Business Object and Services and RFCs as a Web Service via WSDL with JCA binding. This tutorial describes how to invoke a Peoplesoft Account Business Object interface through a synchronous BPEL process.

The Oracle AS Adapter for AQ interfaces with the Business Event System to receive Oracle Applications events in real-time. The Oracle AS Adapter for Database can invoke any stored procedure or function. The Oracle AS Adapter for Siebel interfaces with Siebel Business Objects and Services to post and query Siebel data. This tutorial shows the integration of Oracle Applications with Siebel using the AQ, Database and Siebel adapters. The business process is triggered by the arrival of Oracle Applications business event and it inturn invokes Peoplesoft CustAccount Insert Business Object interface.

The Oracle Adapter for JMS provides standards based connectivity to various enterprise messaging software and provides comprehensive support for the JMS specification. This example showcases MQSeries Queue to Queue integration.

The Oracle Adapter for JMS provides standards based connectivity to various enterprise messaging software and provides comprehensive support for the JMS specification. This example showcases MQSeries Queue to Topic integration.

The Oracle Adapter for Databases is used for invoking stored procedures and performing data manipulation operations and queries and does not require coding. It supports a rich set of databases – Oracle, DB2, Microsoft SQL, Sybase, Informix and can support any standard JDBC 1.x, 2.0 compliant database. The Oracle Adapter for Files rapidly integrates information stored in a variety of formats and supports both File Read and Write operations.

The Oracle Adapter for Databases is used for invoking stored procedures and performing data manipulation operations and queries and does not require coding. It supports a rich set of databases – Oracle, DB2, Microsoft SQL, Sybase, Informix and can support any standard JDBC 1.x, 2.0 compliant database. The Oracle Adapter for Files rapidly integrates information stored in a variety of formats and supports both File Read and Write operations.

The Oracle Adapter for Files rapidly integrates information stored in a variety of formats and supports both File Read and Write operations. Correlation sets are a BPEL mechanism that provides for the correlation of asynchronous messages based on message body contents. When an asynchronous service is initiated with the invoke activity, a correlation ID unique to the client request is sent (using WS Addressing) and the response received is mapped to the appropriate request by the Oracle BPEL Server based on the correlation id. The correlation between request and response is automatically taken care of by WS Addressing by the BPEL server and no extra step is required. However, correlation sets needs to be defined when the interactions are not simple invoke-receive activities. This example illustrates how to use BPEL correlation sets for a process having mid-process receive activity and no associated invoke activity.