Skip Headers
Oracle® Application Server Adapter for Tuxedo User's Guide
10g Release 2 (10.1.2)
B15802-01
  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

This chapter provides an overview of the features and architecture of OracleAS Adapter for Tuxedo.

This chapter contains the following sections:

OracleAS Adapter for Tuxedo Overview

OracleAS adapter for Tuxedo integrates Oracle Application Server with the legacy and mainframe applications. OracleAS Adapter for Tuxedo models services running on the BEA Tuxedo application server. The BEA Tuxedo application server provides two programming interfaces, Common Object Request Broker Architecture (CORBA) and Application to Transaction Monitor Interface (ATMI). ATMI supports a programming interface that offers procedural library-based programming using a set of C or COBOL procedures. ATMI also provides an interface for communication, transaction, and data buffer management. In addition, the ATMI interface and BEA Tuxedo system implement the X/Open distributed transaction processing (DTP) model for transaction processing.

In OracleAS Adapter for Tuxedo, Tuxedo services are modeled as a collection of interactions, where each interaction is mapped to a specific Tuxedo service along with its particular input record and output record.

OracleAS Adapter for Tuxedo includes the following features:

OracleAS Adapter for Tuxedo does not support two-phase commit and cannot participate in a distributed transaction.

OracleAS Adapter for Tuxedo Architecture

The following components comprise the architecture for Oracle AS Adapter for Tuxedo:

Figure 1-1 illustrates the components of OracleAS Adapter for Tuxedo.

Figure 1-1 Architecture of OracleAS Adapter for Tuxedo

Oracle Application Server Adapter architecture for Tuxedo
Description of the illustration xiptu002.gif

The Flow from Oracle Application Server to the Legacy Application and Back

The J2CA 1.0 Tuxedo adapter converts the J2CA interaction invocation received from an application client to the XML format and passes the XML format to Oracle Connect on the legacy server. The daemon listens for the request coming from the J2CA 1.0 Tuxedo adapter client and assigns a server process to handle the request. The properties of the server process (such as connection pooling requirements) are defined by a workspace definition within the daemon. The server process includes an instance of the application engine, which converts the XML format into native structures understandable by Tuxedo and passes the converted XML to the back-end adapter. The back-end adapter builds an interaction based on the metadata for the back-end adapter stored in the repository and the incoming converted XML and passes it to the legacy application. The results of this execution are passed back to the application engine, using the back-end adapter, where these results are converted to XML and passed back to the client.