11g Release 1 (11.1.1.4.0)
Part Number E10537-03
Contents
Previous
Next
| Oracle Fusion Middleware Adapter for Oracle Applications User's Guide 11g Release 1 (11.1.1.4.0) Part Number E10537-03 | Contents | Previous | Next |
This chapter covers the following topics:
Oracle Applications is a set of integrated business applications that runs entirely on the Internet. Oracle Applications offers you the following:
Reduced costs
Increased value across front-office and back-office functions
Access to current, accurate, and consistent data
Oracle Applications 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 Applications to non-Oracle applications, you use Oracle Fusion Middleware Adapter for Oracle Applications.
Adapter for Oracle Applications not only provides comprehensive, bidirectional, multimodal, synchronous, and asynchronous connectivity to Oracle Applications, but also supports for all modules of Oracle Applications in Release 12 and Release 11i including custom integration interfaces in various versions of Oracle E-Business Suite.
Important: Please note that Adapter for Oracle Applications is also informally known as Oracle E-Business Suite Adapter.
The support for various versions of Oracle E-Business Suite has the following conditions:
Adapter for Oracle Applications supports only those versions of Oracle E-Business Suite Release 11i which work with OWF.G.Rollup 7 applied.
Adapter for Oracle Applications version 10.1.3.3 onwards supports Oracle E-Business Suite Release 12.0.
To enable the native Oracle E-Business Suite connectivity using J2EE data sources feature, the minimum requirement for Oracle E-Business Suite Release 11i is 11i.ATG_PF.H.Delta.6 (RUP6) and for Oracle E-Business Suite Release 12 is Release 12.0.4.
See "Oracle Fusion Middleware Adapter for Oracle Applications, Release 11g", My Oracle Support (formerly OracleMetaLink) Knowledge Document 787637.1 for details.
Adapter for Oracle Applications provides the following features:
It leverages the Integration Repository to provide the information from the source of truth on integration.
It supports the widest range of integration interface types. They are PL/SQL APIs, Business Events, Open Interface Tables, Concurrent Programs, XML Gateway Interfaces, e-Commerce Gateway Interface, and Interface Views.
It generates adapter metadata as WSDL files with J2CA extension.
Note: For more information, see Oracle Fusion Middleware User's Guide for Technology Adapters.
It works under the securely configured connection between Oracle Applications and Oracle Fusion Middleware using just the FND User name and password for authentication.
It leverages and supports Oracle User Management function security feature to allow only authorized users to access and execute APIs that they are exposed as Web services to update Oracle Applications.
It implicitly takes care of application context without bothering about the complexities of invoking the same explicitly.
It supports multiple languages and multiple organization access control (MOAC) setups based on the concept of applications context.
It uses a JDeveloper based design-time tool for dynamically browsing the Oracle Applications interface and configuring the adapter metadata. The design-time tasks are wizard driven, user-friendly, and intuitive providing superior user experiences.
It provides the global transaction control support implementing two-phase commit by leveraging the underlying JCA standards compliant framework.
It supports multiple versions of Oracle E-Business Suite from the same instance of Adapter at design time.
Adapter for Oracle Applications is based on J2CA 1.0 standards and deployed as a resource adapter within the Oracle WebLogic Server container. The architecture of Adapter for Oracle Applications is similar to the architecture of technology adapters.
Adapter for Oracle Applications Architecture
For more information on technology adapters, see Oracle Fusion Middleware User's Guide for Technology Adapters.
Adapter for Oracle Applications 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 Installation Guide for Oracle SOA Suite.
Based on the service-oriented architecture (SOA), Oracle BPEL Process Manager (BPEL PM) provides a comprehensive solution for creating, deploying, and managing Oracle BPEL Process Manager business processes.
Adapter for Oracle Applications 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 using BPEL Designer. 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
The Oracle JDeveloper BPEL Designer, a graphical drag and drop environment, is used to design BPEL-based process flows and Web services orchestration.
When you create a partner link in JDeveloper BPEL Designer, the Adapter Configuration Wizard starts which enables you to select and configure the Adapters for Oracle Applications or other adapters. With proper database and service connection setups, you can select an interface in or out from Oracle E-Business Suite and add the XML schema. 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 Adapter for Oracle Applications is based on the J2CA 1.5 specification, and a BPEL process is deployed on the 11g run time on the Oracle WebLogic Server. A JCA Binding Component acts as the glue layer that integrates the standard J2CA 1.5 resource adapter with the Oracle BPEL Process Manager during run time. The JCA Binding Component acts as a pseudo J2CA 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 is converted to a J2CA CCI (Common Client Interface) outbound interaction, and the J2CA response is converted back to a Web service response. This end-to-end invocation is synchronous.
Testing the BPEL Process at Run Time
After deploying the BPEL process, you should validate the design by testing the deployed BPEL process 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.
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 J2CA container for hosting J2CA resource adapters. J2CA 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 J2CA outbound interaction.
Run Time
Oracle Adapter for Oracle Applications is based on the J2CA 1.5 specification, but is deployed as the J2CA 1.5 resource adapter within the Oracle WebLogic Server container. The J2CA 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 Installation Guide for Oracle JDeveloper.
This section describes the new features that have been added in Oracle Fusion Middleware Adapter for Oracle Applications 11g Release 1 (11.1.1.4.0).
Oracle Fusion Middleware Adapter for Oracle Applications implements the Oracle SOA Suite's logging framework to write the diagnostic log files in text format. Therefore, whenever the Oracle E-Business Suite services are invoked using Oracle Adapter for Oracle Applications, the log messages are recorded which can be accessed by system administrator. This enriches the problem identification mechanism to track any issues during service invocations at run time for Oracle Adapter for Oracle Applications.
With proper log-level configuration in Oracle Enterprise Manager Fusion Middleware Control Console, you can view Oracle Diagnostic Logging (ODL) level log files written to a single file at run time for Oracle Adapter for Oracle Applications.
For more information on viewing adapter logs, see Logging.
Copyright © 2005, 2010, Oracle and/or its affiliates. All rights reserved.