Skip Headers
Oracle® Application Server Adapter Concepts Guide
10g Release 2 (10.1.2)
B14058-04
  Go To Documentation Library
Home
Go To Product List
Solution Area
Go To Table Of Contents
Contents
Go To Index
Index

Previous
Previous
Next
Next
 

1 Introduction

With the growing need for business process optimization, efficient integration with existing back-end applications has become the key to success. To optimize business processes, you can integrate applications by using Oracle Application Server adapters. Adapters support a robust, light-weight, highly scalable, and standard-based integration framework, which enables disparate applications to communicate with each other. For example, adapters enable you to integrate packaged applications, legacy applications, databases, and Web services. Using adapters, you can ensure interoperability by integrating applications that are heterogeneous, provided by different vendors, based on different technologies, and run on different platforms.


Note:

Adapters support local transactions in this release and do not participate in global transactions. This document addresses the integration of adapters with OC4J, Business Process Execution Language for Web Services (BPEL) Process Manager, and OracleAS Integration InterConnect.

This chapter contains the following topics:

Features of Oracle Application Server Adapters

Oracle Application Server adapters provide the following benefits:

Types of Oracle Application Server Adapters

There are three types of Oracle Application Server adapters: technology, packaged application, and legacy. Figure 1-1 illustrates the different types of adapters.

Figure 1-1 Types of Oracle Application Server Adapters

Description of Figure 1-1  follows
Description of "Figure 1-1 Types of Oracle Application Server Adapters"

This section describes the following types of adapters:

Technology Adapters

Technology adapters integrate Oracle Application Server with transport protocols, data stores, and messaging middleware. These adapters include OracleAS Adapter for FTP, OracleAS Adapter for JMS, OracleAS Adapter for Database, OracleAS Adapter for Advanced Queuing, and OracleAS Adapter for Files. Technology adapters are currently available with the BPEL Process Manager installation.

Packaged-Application Adapters

Packaged-application adapters integrate Oracle Application Server with various packaged applications, such as SAP and Siebel. These adapters include OracleAS Adapter for Oracle Applications, OracleAS Adapter for PeopleSoft, OracleAS Adapter for SAP R/3, OracleAS Adapter for Siebel, and OracleAS Adapter for J.D. Edwards. Packaged-application adapters are available as part of the OracleAS Adapters CD.

Legacy Adapters

Legacy adapters integrate Oracle Application Server with legacy and mainframe applications. These adapters include OracleAS Adapter for Tuxedo, OracleAS Adapter for CICS, OracleAS Adapter for VSAM, OracleAS Adapter for IMS/TM, and OracleAS Adapter for IMS/DB. Legacy adapters are available as part of the OracleAS Adapters CD.

Types of Oracle Application Server Adapter Services

Adapters provide the following types of services to facilitate communication between applications:

Request-Response (Outbound Interaction) Service

Adapters support the synchronous request-response service. The adapters receive requests from adapter clients, translate these requests into the native back-end data format, and call the appropriate method in the back-end application. In addition, the request-response service retrieves the back-end response to the Adapter Framework component after performing reverse translation. In J2CA terminology, this type of service is also known as outbound interaction.

The request-response service can be used to create, delete, update, and query back-end data as well as to call back-end workflows and transactions. For example, an OC4J application client can use OracleAS Adapter for SAP to create a customer within the SAP application.

Figure 1-2 illustrates the request-response service.

Figure 1-2 Request-Response Service

Description of Figure 1-2  follows
Description of "Figure 1-2 Request-Response Service"

Event Notification (Inbound Interaction) Service

Adapters support the event-notification service, which is an asynchronous communication paradigm. In J2CA terminology, this type of service is also known as inbound interaction.

Adapters either listen or poll for back-end event changes. When listening for events, an adapter registers as a listener for the back-end application that is configured to push events to the adapter. The adapter can also poll the back-end application, which is usually a database or file, for the events required by the client application.

The event-notification service can be used to keep a track of back-end events associated with successful back-end transactions for creating, deleting, and updating back-end data.

Figure 1-3 illustrates the event-notification service.

Figure 1-3 Event-Notification Service

Description of Figure 1-3  follows
Description of "Figure 1-3 Event-Notification Service"

Metadata Service

The adapter metadata definition stores information about the back-end connection and schemas for business objects and services. Adapters consist of a design-time component for browsing and storing metadata and a run-time component for running services. The adapter metadata definitions are generated as XML Schema Definition (XSD) and WSDL files. Figure 1-4 illustrates the metadata interaction.

Figure 1-4 Metadata Service

Description of Figure 1-4  follows
Description of "Figure 1-4 Metadata Service"