Skip Headers
Oracle® Application Server Adapter for IMS/DB User's Guide
10g Release 2 (10.1.2)
B15806-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

The Oracle Application Server Adapter for IMS/DB (OracleAS Adapter for IMS/DB) provides connectivity and runs interactions on an Information Management System - Data Base (IMS/DB) system. This chapter provides an overview of the features and architecture of OracleAS Adapter for IMS/DB.

This chapter contains the following sections:

OracleAS Adapter for IMS/DB Overview

IMS/DB (Information Management System - Data Base) is a high-performance hierarchical database. The data access API to IMS/DB is called DL/I, which is a function by which the IMS/DB database can be traversed and operated on. Working with DL/I requires the caller to run under the control of IMS/DB. APIs are also available to enable access to IMS/DB from CICS and IMS/TM transactions.

OracleAS Adapter for IMS/DB includes the following feature:

OracleAS Adapter for IMS/DB Architecture

OracleAS Adapter for IMS/DB includes the following components:

The following figure illustrates the components of OracleAS Adapter for IMS/DB.

Architecture of the Oracle Integration Adapter for Tuxedo.
Description of the illustration xipims_db002.gif

Integration Flow from Oracle Application Server to the Legacy Application

The J2CA 1.0 IMS/DB adapter converts the J2CA interaction invocation received from Oracle Application Server 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 IMS/DB 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 standard SQL which is passed to the data engine. The data engine processes the SQL to create an efficient strategy for retrieving the data from IMS/DB and then passes the SQL and execution strategy to the database back-end adapter. The database back-end adapter passes the SQL to the back-end driver, which converts the SQL to the language understood by IMS/DB and passes it to IMS/DB to be executed. The results of the SQL statement are passed back to the application engine, through the back-end adapter, where these results are converted to XML and passed back to the client.