Introduction to Oracle E-Business Suite Adapter


Oracle E-Business Suite is a set of integrated business applications that runs entirely on the Internet. Oracle E-Business Suite offers you the following:

Oracle E-Business Suite are built on a unified information architecture that consolidates data from Oracle and non-Oracle applications and enables a consistent definition of customers, suppliers, partners, and employees across the entire enterprise. This results in a suite of applications that can give you information, such as current performance metrics, financial ratios, profit and loss summaries. To connect Oracle E-Business Suite to non-Oracle applications, you use Oracle Fusion Middleware Oracle E-Business Suite Adapter.

Oracle E-Business Suite Adapter (formerly known as Adapter for Oracle Applications) not only provides comprehensive, bidirectional, multimodal, synchronous, and asynchronous connectivity to Oracle E-Business Suite, but also supports for all modules of Oracle E-Business Suite in Release 12 and Release 11.5.10 including custom integration interfaces in various versions of Oracle E-Business Suite.

Important: The support for various versions of Oracle E-Business Suite has the following conditions:

Major Features

Oracle E-Business Suite Adapter provides the following features:


Oracle E-Business Suite Adapter is based on JCA 1.5 standards and deployed as a resource adapter within the Oracle WebLogic Server container. The architecture of Oracle E-Business Suite Adapter is similar to the architecture of technology adapters.

Oracle E-Business Suite Adapter Architecture

the picture is described in the document text

For more information on technology adapters, see Oracle Fusion Middleware Understanding Technology Adapters.

Installing Oracle E-Business Suite Adapter

Oracle E-Business Suite Adapter and Oracle JCA Adapters are available as part of the Oracle Fusion Middleware install. In addition, these adapters support both Oracle WebLogic Server and middle tier deployments.

For more information, see Oracle Fusion Middleware Installing and Configuring Oracle SOA Suite and Oracle Business Process Management.

Integration with Oracle Fusion Middleware

Oracle E-Business Suite Adapter integrates with the JCA Binding Component of the Oracle Fusion Middleware platform; therefore, it integrates with service engines, such as Oracle BPEL Process Manager (Oracle BPEL PM) and Oracle Mediator.

Oracle E-Business Suite Adapter can easily expose public integration interface within Oracle E-Business Suite as standard Web services. These services can be created and configured in the Oracle JDeveloper at design time while integrating with Oracle BPEL PM and Oracle Mediator. At run time, Oracle E-Business Suite integration flows are deployed in the Oracle WebLogic Server for execution of the services to complete the integration.

Design Time

While integrating with Oracle BPEL PM and Oracle Mediator, Oracle E-Business Suite Adapter uses Oracle JDeveloper as the design-time tool to create SOA Composite applications and generate WSDL and JCA files for the Web services.

When you create a partner link in Oracle JDeveloper BPEL Designer, the Adapter Configuration Wizard starts and allows you to select and configure Oracle E-Business Suite Adapter or other adapters. With proper database and service connection setups, you are presented with a functionally organized list of inbound and outbound interfaces available in your Oracle E-Business Suite instance for which you select the one that fulfill your requirements. When configuration is complete, the wizard generates a WSDL file corresponding to the XML schema for the partner link.

Additional process activities are added to the BPEL process if necessary to assign parameters and invoke the service.

Run Time

Oracle E-Business Suite Adapter is based on the JCA 1.5 specification. A Composite application including the BPEL processes, Mediator services, and partner link definitions generated at design time is deployed to the Oracle WebLogic Server. A JCA Binding Component acts as the glue layer that integrates the standard JCA 1.5 resource adapter with the Oracle BPEL Process Manager during run time. The JCA Binding Component acts as a pseudo JCA 1.5 container.

Note: Only the JCA 1.5 integration allows the BPEL PM to receive inbound events (from EIS to J2EE/BPEL PM). The Oracle BPEL Process Manager acts as a pseudo JCA 1.5 container and implements the JCA 1.5-specific System Contracts. The JCA 1.5 resource adapter and the BPEL PM instance must be deployed in the same Oracle WebLogic Server container.

The Web service invocation launched by the BPEL Invoke activity contained in the SOA Composite is converted to a JCA CCI (Common Client Interface) outbound interaction, and the JCA response is converted back to a Web service response. This end-to-end invocation is synchronous.

Testing the SOA Composite Application at Run Time

After deploying the SOA Composite application, you should validate the design by testing the BPEL process contained in the deployed SOA Composite application to test the interface integration.

For detailed design-time and run-time tasks for each integration interface, see the individual interface chapter explained later in this book.

Integration with Oracle WebLogic Server

Oracle WebLogic Server is a scalable, enterprise-ready Java Platform, Enterprise Edition (Java EE) application server. Its infrastructure enables enterprises to deploy mission-critical applications in a robust, secure, highly available, and scalable environment and is an ideal foundation for building applications based on service-oriented architectures (SOA). SOA is a design methodology aimed at maximizing the reuse of application services.

In addition, Oracle WebLogic Server consists of a JCA container for hosting JCA resource adapters. JCA defines standard Java interfaces for simplifying the integration of a J2EE server with various back-end applications. All client applications run within the Oracle WebLogic Server environment.

Design Time

Oracle JDeveloper is used to create Web services represented in WSDL files and XML Schema Definition (XSD) files for the adapter request-response service.

The Oracle WebLogic Server clients use these XSD files during run time for calling the JCA outbound interaction.

Run Time

Oracle E-Business Suite Adapter is based on the JCA 1.5 specification and is deployed as resource adapter within the Oracle WebLogic Server container. The JCA 1.5 specification addresses the life-cycle management, message-inflow (for Adapter Event publish), and work management contracts.

For more information about using Oracle WebLogic Server with Oracle JDeveloper, see the Using WebLogic Server with Oracle JDeveloper section, Oracle Fusion Middleware Installing Oracle JDeveloper.