1 Introduction

This chapter provides an overview of Oracle Application Server adapters. It contains the following topics:

Oracle Application Server Adapter Overview
Oracle Application Server Adapter System Requirements

Oracle Application Server Adapter Overview

The OracleAS Adapters CD enables you to install the following types of adapters:

Packaged-Application Adapters
Legacy Adapters
Oracle Application Server Components Integration with Adapters
Types of 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 PeopleSoft, OracleAS Adapter for SAP R3, OracleAS Adapter for mySAP ERP, OracleAS Adapter for Siebel, and OracleAS Adapter for J.D. Edwards.

Note:

In the current release, OracleAS Adapter for mySAP ERP adapter would be preferred over OracleAS Adapter for SAP R3, if you are installaing adapters from scratch because of it's backward compatibility

Table 1-1 describes the packaged-application adapters.

Table 1-1 Oracle Application Server Adapters for Packaged Applications

Adapter	Description
OracleAS Adapter for J.D. Edwards	Provides comprehensive, bidirectional, and standards-based connectivity to J.D.Edwards applications
OracleAS Adapter for PeopleSoft	Provides unique features, such as the support for J2CA and Web Service standards, for creating an open and reusable service-oriented architecture that offers a complete connectivity solution for PeopleSoft applications
OracleAS Adapter for SAP R3	Exchanges real-time business data between SAP systems and other applications, databases, or external business partner systems.
OracleAS Adapter for Siebel	Connects Oracle Application Server to a Siebel system by providing unique features that minimize the implementation effort.
OracleAS Adapter for mySAP ERP	Connects Oracle Application Server to an SAP system through OracleAS Adapter for mySAP ERP (OracleAS Adapter for mySAP) to provide connectivity and carry out interactions on an SAP system. OracleAS Adapter for mySAP ERP is a part of the same installation as that of the SAP adapter. In addition, mySAP ERP adapter is backward compatible to all versions supported by the SAP adapter. Note: Verify the certifcation matrix and the Statement of direction (SOD) for both mySAP ERP and SAP R/3 before installing.

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.

Table 1-2 describes legacy adapters. These adapters are deployed as J2CA resource adapters within the OC4J container during installation.

Table 1-2 Oracle Application Server Adapters for Legacy Applications

Adapter	Description
OracleAS Adapter for Tuxedo	Models services running on the BEA Tuxedo application server. Captures and maintains a metadata schema for the Tuxedo system by importing Tuxedo metadata and transforming this metadata into mapping definitions for Oracle Connect.
OracleAS Adapter for CICS	Connects Oracle Application Server with CICS. This adapter supports two-phase commit and can fully participate in a distributed transaction.
OracleAS Adapter for VSAM	Enables access to VSAM data managed by CICS or directly. This adapter implements interactions as parameterized SQL with the parameters forming the input record, and with the output (in cases where there is an output) aggregated into an XML document forming the output record.
OracleAS Adapter for IMS/TM	Provides access to MPP based IMS/TM transactions. Each OracleAS Adapter for IMS/TM outbound interaction is mapped to a specific IMS/TM transaction.
OracleAS Adapter for IMS/DB	Captures and maintains a metadata schema for IMS/DB by importing various IMS definition files such as a PSB file, DBD files, and COBOL copybooks.

Oracle Application Server Components Integration with Adapters

The Oracle Application Server adapters enable you to integrate packaged, legacy, and mainframe applications with various Oracle Application Server components, such as Oracle BPEL Process Manager and Oracle Enterprise Service Bus. The Oracle Application Server adapters for technology applications and Oracle AS Adapter for Oracle Applications are packaged with the BPEL Process Manager installation.

Table 1-3 describes the Oracle Application Server components that can be integrated with adapters. Adapters are certified to work with the SOA Suite, Oracle Enterprise Service Bus, and Oracle BPEL Process Manager.

Table 1-3 Oracle Application Server Component Integration with Adapters

Component	Description
Oracle Application Server Portal	Combines a declarative environment for creating a portal Web interface, publishing and managing information, accessing dynamic data, and customizing the portal experience, with an extensible framework for J2EE-based application access. Using OracleAS Portal, organizations can provide employees, partners, and suppliers with the information they need and the flexibility to create views tailored to each community.
Oracle Containers for J2EE (OC4J)	The J2EE server component of Oracle Application Server written entirely in Java that runs on the standard Java Development Kit (JDK) Java Virtual Machine (JVM). OC4J includes a JSP Translator, a Java servlet container, and an Enterprise JavaBeans container.
Oracle BPEL Process Manager	Enables organizations to model and deploy business processes based on the Business Process Execution Language for Web Services (BPEL) standard. Using Oracle BPEL Process Manager, organizations can reduce the cost and complexity of integration projects and increase their strategic value.
Oracle Enterprise Service Bus	An enterprise service bus moves data among multiple endpoints, both within and outside of an enterprise. It uses open standards to connect, transform, and route business documents (as Extensible Markup Language (XML) messages), among disparate applications. It enables monitoring and management of business data, with minimal impact on existing applications. An enterprise service bus is the underlying infrastructure for delivering a service-oriented architecture (SOA) and event-driven architecture (EDA).

Types of Installation

You can use the following two types of installation for Oracle Application Server adapters:

Design time and Run time
Design time

After selecting an installation type during installation, select the type of adapter you want to install. Table 1-4 describes the types of installation.

Table 1-4 Types of Installation

Installation Type	Description
Design time and Run time	Installs the following design time and run time components: Design time components Installs Application Explorer. Note: For legacy applications, the design-time components are not installed. Run-time components Deploys the following runtime components automatically: J2CA deployment for packaged applications BSE deployment for packaged applications J2CA legacy adapter for connecting with Oracle Connect engine running on legacy platforms Note: You need to install Oracle Studio on Windows and Oracle Connect on the required legacy platform. These are not components of Oracle Universal Installer, but part of the Adapters CD.
Design time	Installs only the Application Explorer design time component. None of the run-time components are deployed. Note: This installation type does not require J2EE and Web Cache or any other Middle Tier installation type.

Installation Type

Description

Design time and Run time

Installs the following design time and run time components:

Design time components

Installs Application Explorer.

Note: For legacy applications, the design-time components are not installed.
Run-time components

Deploys the following runtime components automatically:
- J2CA deployment for packaged applications
- BSE deployment for packaged applications
- J2CA legacy adapter for connecting with Oracle Connect engine running on legacy platforms

Note: You need to install Oracle Studio on Windows and Oracle Connect on the required legacy platform. These are not components of Oracle Universal Installer, but part of the Adapters CD.

Design time

Installs only the Application Explorer design time component. None of the run-time components are deployed.

Note: This installation type does not require J2EE and Web Cache or any other Middle Tier installation type.

Packaged-application adapters can be deployed as a:

J2CA 1.0 resource adapter and test servlet for J2CA deployments
Web services servlet within the OC4J container, which is known as OracleAS Adapter Business Services Engine (BSE)

The OracleAS Adapter Application Explorer tool is also provided for configuring OracleAS adapters for packaged applications (for both J2CA and BSE deployments).

Legacy adapters can be deployed as a J2CA 1.0 resource adapter. To install Oracle Connect for legacy adapters, refer to the sections described in Table 1-5. These sections describe how to install Oracle Connect and Oracle Studio from the CD-ROM and how to configure Oracle Connect using Oracle Studio.

Table 1-5 Installing Oracle Connect

Legacy Adapter	Refer to
OracleAS Adapter for Tuxedo	The Installing and Configuring OracleAS Adapter for Tuxedo chapter in Oracle Application Server Adapter for Tuxedo User's Guide
OracleAS Adapter for CICS	The Installing and Configuring OracleAS Adapter for CICS chapter in Oracle Application Server Adapter for CICS User's Guide
OracleAS Adapter for VSAM	The Installing and Configuring OracleAS Adapter for VSAM chapter in Oracle Application Server Adapter for VSAM User's Guide
OracleAS Adapter for IMS/TM	The Installing and Configuring OracleAS Adapter for IMS/TM chapter in Oracle Application Server Adapter for IMS/TM User's Guide
OracleAS Adapter for IMS/DB	The Installing and Configuring the OracleAS Adapter for IMS/DB chapter in Oracle Application Server Adapter for IMS/DB User's Guide

Oracle Application Server Adapter System Requirements

The following sections describe the system requirements for installing Oracle Application Server adapters:

Hardware Requirements
Software Requirements

Hardware Requirements

Table 1-6 lists the hardware requirements for the computer where OracleAS Adapter will be installed.

Table 1-6 Hardware Requirements

Hardware	Windows 2000	Solaris	Linux
Disk Space (to install all adapters)	200 MB	200 MB	200 MB
Memory	256 MB	256 MB	256 MB

Software Requirements

The following sections describe the Oracle Application Server adapters software requirements:

Operating System Requirements
J2EE and Web Cache Requirements

Operating System Requirements

Table 1-7 lists the operating system requirements for the computer where Oracle Application Server adapters will be installed.

Table 1-7 Operating System Requirements

Operating System	Version
HP Tru64	HP Tru64 UNIX (Alpha) 5.1b
HP-UX	HP-UX (PA-RISC) 11.11, 11.23
IBM AIX	AIX (POWER) version 5.2
Linux (x86)	Red Hat Enterprise Linux 2.1, 3.0 SuSE SLES8, SLES9 See Also: Oracle Application Server Installation Guide for Microsoft Windows for Linux x86 for information about any required operating system patches and packages and kernel parameter settings
Sun SPARC Solaris	Sun SPARC Solaris 8 and 9 See Also: Oracle Application Server Installation Guide for Microsoft Windows for Solaris for information about any required operating system patches and packages, swap space requirements, and kernel parameter settings
Microsoft Windows	Windows XP Professional, Windows 2000( SP3 or later) See Also: Oracle Application Server Installation Guide for Microsoft Windows for Windows for information on processor, `TEMP` directory, virtual memory, and swap space requirements

J2EE and Web Cache Requirements

If you want to use the Complete installation type, then the J2EE and Web Cache installation type of Oracle Application Server must first be installed. You then install the Complete installation type of Oracle Application Server adapters into the same Oracle home.

The design time installation type does not require J2EE and Web Cache or any other Middle Tier installation type.

Note:

To install Oracle Application Server adapters with Oracle BPEL Process Manager, you need to use the BPEL Process Manager patch 1.