Oracle Audio Technologies B31003-01 ユーザーズマニュアル
OracleAS Adapter for IMS/TM Architecture
1-2 Oracle Application Server Adapter for IMS/TM User’s Guide
OracleAS Adapter for IMS/TM Architecture
OracleAS adapter includes the following components:
■
J2CA 1.5 IMS/TM adapter: The J2CA IMS/TM adapter is a standard resource
adapter that is compliant with J2EE Connector Architecture, providing J2EE
components connectivity.
adapter that is compliant with J2EE Connector Architecture, providing J2EE
components connectivity.
■
Oracle Connect: Oracale Connect runs on the legacy system and handles requests
from the J2CA 1.5 IMS/TM adapter, that runs within Oracle Application Server
Containers for J2EE (OC4J).
from the J2CA 1.5 IMS/TM adapter, that runs within Oracle Application Server
Containers for J2EE (OC4J).
■
Oracle Studio: Oracle Studio is the configuration tool for Oracle Connect.
Configuration tasks using Oracle Studio are performed on a Windows platform.
Oracle Studio uses perspectives that enables you to generate specific information
necessary to model OracleAS Adapter for IMS/TM.
Configuration tasks using Oracle Studio are performed on a Windows platform.
Oracle Studio uses perspectives that enables you to generate specific information
necessary to model OracleAS Adapter for IMS/TM.
The following figure illustrates the components of OracleAS Adapter for IMS/TM:
Figure 1–1 Adapter Architecture
Integration Flow from Oracle Application Server to a Legacy Application
The J2CA 1.5 IMS/TM 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.5
IMS/TM 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 IMS/TM 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 to be executed. The results of the 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.
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.5
IMS/TM 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 IMS/TM 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 to be executed. The results of the 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.
Note:
For a comprehensive description of the integration adapter
architecture, see the following Oracle documentation:
Oracle Application Server Adapter Concepts Guide