11g (11.1.1.1.0)
Part Number E10537-01
Contents
Previous
Next
| Oracle Fusion Middleware Adapter for Oracle Applications User's Guide 11g (11.1.1.1.0) Part Number E10537-01 | 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 provides comprehensive, bidirectional, multimodal, synchronous, and asynchronous connectivity to Oracle Applications. The Adapter supports for all modules of Oracle Applications in Release 12 and Release 11i including selecting custom integration interface types based on the version 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 E-Business Suite Connectivity using J2EE Data Sources" feature, the minimum requirement for Oracle E-Business Suite Release 11i is FND Rollup 6 and for Oracle E-Business Suite Release 12 is 12.0.4 release.
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 is 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 Applications 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.
With the integration with BPEL PM, Adapter for Oracle Applications can easily expose each interface or integration endpoint within Oracle E-Business Suite as a Web service. It can be achieved through a proper configuration using a BPEL language from Oracle JDeveloper at design time. At run time, this BPEL process can be deployed to Oracle BPEL server for further service execution.
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
Before deploying the BPEL process to Oracle BPEL server, necessary run-time parameters, system settings, and application setup must be properly configured for a successful deployment and service integrations.
Note: Agent Listeners should also be up and running if needed for certain interface types used in Oracle E-Business Suite.
While deploying the BPEL process, the WSIF Provider converts the Web service invocation from BPEL PM Invoke activity to an outbound interaction call and performs the reverse conversion in the other direction as a Web service response for a synchronous request-response message pattern. The WSIF Provider also supports the one-way asynchronous outbound interaction invocation such as integration with XML Gateway outbound message maps and outbound business events.
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 representing 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
Although Adapter for Oracle Applications is physically deployed as J2CA 1.5 resource adapters, the logical deployment of the Adapter involves creating the connection entries for the J2CA 1.0 resource adapter within the Oracle WebLogic Server container in this release.
The J2CA 1.0 specification addresses the request-response service also known as outbound interaction and does not address the asynchronous publication of back-end events by the adapter. 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.1.0).
Header variables are used to provide applications context information required in a BPEL process or to populate mandatory header variables for XML Gateway inbound transactions to complete successfully. To provide header support and simplify the design time tasks, Adapter for Oracle Applications now normalizes the header values by setting each individual message property directly through the Properties tab of the Invoke activity without using an Assign activity.
Note: In earlier releases, these header values were defined in the Adapter tab of an Invoke activity and then passed through an Assign activity to set the parameters for message propagation.
For example, in this release XML Gateway header variables such as TransactionType, TransactionSubtype, PartySiteId, DocumentNumber, MessageType, and MessageStandard are no longer passed in ECXMSG object as a whole in the header. Instead, each individual field within the ECXMSG object is now normalized and becomes an individual message property as listed below. You can simply set the message properties directly in the Properties tab of an Invoke activity.
jca.apps.ecx.TransactionType
jca.apps.ecx.TransactionSubtype
jca.apps.ecx.PartySiteId
jca.apps.ecx.MessageType
jca.apps.ecx.MessageStandard
jca.apps.ecx.DocumentNumber
Adapter for Oracle Applications can now accept the following three new header properties for setting application context correctly:
jca.apps.RespApplication: Responsibility Application Key which needs to be used to set the context.
jca.apps.SecurityGroup: Security Group Key which defaults to 'STANDARD' if not passed.
jca.apps.NLSLanguage: It is the language code for the request. NLS context would be set to the language code that is passed if valid. It would default to 'US' if not passed.
Note: Existing header property jca.apps.Responsibility used in earlier releases can now take Responsibility Key as well as Responsibility Name as input. If the header property jca.apps.NLSLanguage is set, and Responsibility Name is passed, the value passed for jca.apps.Responsibility is expected to be in the same language. However, Responsibility Key as well as all other header properties are language independent.
All these header properties would be used together to set the application context. Alternatively, passing just the Username and Responsibility would work as it did in the earlier releases.
For more message normalization information, see Supporting for Normalized Message Properties.
Copyright © 2005, 2009, Oracle and/or its affiliates. All rights reserved.