Oracle® Application Server Adapter for Oracle Applications User's Guide
10g Release 2 (10.1.2) B16498-02 |
|
Previous |
Next |
This chapter provides an overview of Oracle Applications and Oracle Application Server Adapter for Oracle Applications (OracleAS Adapter for Oracle Applications). It contains the following sections:
Oracle Applications is a set of integrated business applications that runs entirely on the Internet. Oracle Applications offers you the following:
Reduced costs
Increased revenue across front-office and back-office functions
Access to current, accurate, and consistent data
The applications in 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 other non-Oracle applications, you use OracleAS Adapter for Oracle Applications.
OracleAS Adapter for Oracle Applications provides comprehensive, bidirectional, multimodal, synchronous, and asynchronous connectivity to Oracle Applications. The adapter supports all modules of Oracle Applications for versions 11.5.1 to11.5.10. In addition, OracleAS Adapter for Oracle Applications provides real-time and bidirectional connectivity to Oracle Applications through interface tables, views, Application programming interfaces (APIs), concurrent programs, e-commerce Gateway, and XML Gateway.
OracleAS Adapter for Oracle Applications inserts data into Oracle Applications using interface tables, APIs, and concurrent programs. To retrieve data from Oracle Applications, OracleAS Adapter for Oracle Applications uses views. In addition, it uses XML Gateways for bidirectional integration with Oracle Applications. XML Gateways are also used to insert as well as receive Open Application Group Integration Specification (OAGIS) compliant documents from Oracle Applications.
Note: The XML Gateway feature is available in the preview mode of this release. To run the preview mode, run the following command from$ORACLE_HOME\integration\jdev\jdev\bin:
|
This section contains the following topics:
OracleAS Adapter for Oracle Applications consists of the following features:
Supports open standards, such as J2EE Connector Architecture (J2CA), Extensible Markup Language (XML), Web Service Invocation Framework (WSIF), Web Service Inspection Language (WSIL), and Web Service Definition Language (WSDL)
Uses JDeveloper based design-time tool for dynamically browsing the Oracle Applications interface and configuring the adapter metadata
Integrates applications based on open standards, such as OAGIS, by interfacing with the XML Gateway component of the Oracle Applications product
Generates adapter metadata as WSDL files with J2CA extension
OracleAS Adapter for Oracle Applications is based on J2CA 1.0 standards and deployed as a resource adapter in the same Oracle Application Server Containers for J2EE (OC4J) container as BPEL Process Manager. The architecture of OracleAS Adapter for Oracle Applications is similar to the architecture of technology adapters. Figure 1-1 illustrates the architecture of OracleAS Adapter for Oracle Applications.
Figure 1-1 OracleAS Adapter for Oracle Applications Architecture
OracleAS Adapter for Oracle Applications acts as a highly flexible integration interface for Oracle Applications. The adapter provides the following interfaces to integrate with Oracle Applications:
Interface tables: Enable you to insert or update data into Oracle Applications. The associated concurrent program should be running to move the data from the interface tables to base tables.
Views: Help you to retrieve data from Oracle Applications.
APIs: Enable you to insert and update data into Oracle Applications.
Concurrent Programs: Enables you to move data from interface tables to base tables.
e-Commerce Gateway: Provides you a common, standards-based approach for Electronic Data Interchange (EDI) integration between Oracle Applications and third party applications.
XML Gateway: Enables bidirectional integration with Oracle Applications. It helps you to insert and retrieve data from Oracle Applications. XML Gateway is a higher-level API that exposes OAGIS-formatted XML documents for commonly used Oracle Application business objects and business interfaces. XML Gateway integrates with interface tables, Business Event System (BES), and views to insert and retrieve data from Oracle Applications. It maps the underlying table data to XML and back.
This section describes the new integration interface types that have been added, and issues associated with the Oracle e-Business Suite Adapter. This section includes the following topics:
This section describes the installation of the e-Business Suite Adapter.The installation of the Oracle e-Business Suite Adapter happens out-of-the-box with the Oracle BPEL PM product. OracleAS adapter for Oracle Applications is deployed using the Oracle BPEL Process Manager (PM) in Oracle JDeveloper.
See Also: Oracle Application Server Integration Business Activity Monitoring User's Guide for more details about installing Oracle BPEL Process Manager. Refer to section, Notes on Installing Oracle BPEL Process Manager. |
This section describes the new features that have been added in 10.1.2 phase 2.
The Oracle Application Server Integration InterConnect has added the following three new integration interface types to the existing list:
The new integration interfaces are exposed as Web services, and these Web services are available for process orchestration through the Oracle BPEL Process Manager.
Concurrent Programs
A concurrent program is an instance of an execution file, along with parameter definitions and incompatibilities. Concurrent programs use concurrent program executable to locate the correct execution file. OracleAS Adapter for Applications can be configured to use the concurrent program integration interface to perform specific tasks.
XML Gateway
Oracle XML gateway is a set of services that allow easy integration with Oracle Applications to support XML messaging. OracleAS Adapter for Applications can be configured to use the XML gateway integration interface to interact for inbound or outbound transactions with third-party applications.
e-Commerce Gateway
Oracle e-commerce gateway is the Electronic Data Interchange (EDI) integration enabler between Oracle Applications and third-party applications based on a common, standards-based approach. OracleAS Adapter for Applications can be configured to use the Oracle e-Commerce Gateway integration interface to dynamically generate outbound or consume inbound flat files based on user-defined trading partner, mapping, transformation, and data validation rules.
This section describes the following issues and workarounds:
In the Oracle Applications 11.5.10 release, only concurrent programs, which have PL/SQL stored procedure as the execution method, would be supported. This is only a design time browsing functionality as provided by the IRep based browser.
For Oracle Applications 11.5.9 and lower versions, the adapter wizard shows all concurrent programs both private and public. However, from 11.5.10 onwards, only those concurrent programs that are classified as public are shown. This is the intended functionality.
Due to a known issue with the adapter wizard not being able to preserve DEFAULT clauses for PL/SQL wrappers that it generates underneath the covers, you have to adopt the following workaround when working with concurrent program and EDI interfaces to Oracle Applications. You must load SQL file (apps_cp_ecx_wrapper.sql
) once into the apps
schema (through SQL*Plus) before launching the adapter wizard to create services for either concurrent programs or EDI programs. You will find the file, apps_cp_ecx_wrapper.sql
at the following location:
ORACLE_HOME
\integration\orabpel\system\database\scripts\apps_cp_ecx_wrapper.sql
Note: Please do not modify the contents of the SQL file (XX_BPEL_FND_REQUEST_SUBMIT_REQ.sql )
|