Search from 700 + Posts

Sep 29, 2010

Oracle Application Adapter (Oracle AS Adapter) in BPEL ( JDeveloper) Part -1

This post is about Oracle Application Adapter (Oracle AS Adapter) available in BPEL.Oracle Applications is also informally known as Oracle E-Business Suite Adapter.

Oracle Applications is a set of integrated business applications that runs entirely on the Internet.It is 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.

Oracle application Adapter for Oracle Applications provides comprehensive, bidirectional, multimodal, synchronous, and asynchronous connectivity to Oracle Applications. Theses Adapter supports for all modules of Oracle Applications in Release 12 and Release 11i.

Advantages of Oracle Application Adapter are customer  can use there existing Oracle Application Infrastructure and expose Integration Interface/APIs as Webservices by means of Leveraging Oracle Integration repository and,  that is one more Step to Oracle Fusion.
SOA is all about providing /Consuming Services and abstracting Interfaces(by means of exposing them as Web Services).

Service Oriented Architecture of Adapter


EBS Adapter Architecture


OracleAS Adapter for Oracle Applications provides the following features:

  1. It supports open standards, including J2EE Connector Architecture (J2CA),Extensible Markup Language (XML), Web Service Invocation Framework (WSIF),Web Service Inspection Language (WSIL), and Web Service Definition Language(WSDL).
  2. It supports the widest range of integration interface types. They are
    1. PL/SQL APIs,
    2. Business Events,
    3. Open Interface Tables,
    4. Concurrent Programs,
    5. XML Gateway Interfaces,
    6. e-Commerce Gateway Interface, and
    7. Interface Views.
  3. It generates adapter metadata as WSDL files with J2CA extension.
  4. It works under the securely configured connection between Oracle Applications and Oracle Application Server using FND username and password (conceptof Oracle Applications username and password) for authentication.
  5. 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.
  6. It implicitly takes care of application context without bothering about the complexities of invoking the same explicitly.
  7. It supports multiple languages and MOAC setups based on the concept of applications context.
  8. 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.
  9. It provides the global transaction control support implementing two-phase commit by leveraging the underlying JCA standards compliant framework. 
  10. It supports multiple versions of Oracle Applications from the same instance of
 Adapter at design time.

Oracle BPEL (part of SOA Suite) provides a comprehensive solution for creating, deploying, and managing Oracle BPEL business processes.With the integration with BPEL PM, OracleAS Adapter for Oracle Applications can easily expose interface or integration endpoint within Oracle E-Business Suite as a
Web service.
Design Time 
During design time, Web services are exposed as WSDL files and consumed during configuration of the Partner Link activity of BPEL processes. 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 OracleAS Adapters for Oracle Applications. 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
After deploying the BPEL process, you should validate the design by testing the deployed BPEL process. It can be done by manually initiating the BPEL process from the BPEL Console to test the interface integration contained in your BPEL process.

Stay tune for Next post about live demo.

2 comments:

  1. HI,

    This is very good post...
    Please post the Part-2 asap.

    Thanks,
    R. Sathya Moorthy

    ReplyDelete
  2. Need demo example on apps Adapter

    ReplyDelete