Data Transformation Engine Getting Started

Chapter 1 - Introduction
1
2
The following figure shows two adapters below the Platform API:
Platform API
Adapter Adapter
Transformation Server
Input Output
Maps use input and output cards to specify which the adapters to use. The input cards and output cards
can be overridden at runtime through the Platform API, allowing the dynamic selection of adapters.
Mercator adapters fall into four classes: Utility adapters, Messaging adapters, Database adapters, and
Application adapters. Adapters within each class share capabilities or limitations that are different from
adapters in other classes.
Utility Adapters
Utility adapters are a collection of middleware programs used with the Design Studio to retrieve and
route data. You can use utility adapters with a Command Server, CORBA Transformation Server,
Tuxedo Transformation Server, Platform API, or map in a map rule. Each adapter includes commands
you can use to customize its operation.
The memory and file utility adapters form the most basic class of adapters required to make use of the
Platform API.
The file adapter reads input data from a file and writes output data to a file. The memory adapter is used
by custom applications or specialized servers to provide the data directly and bypass the adapters. For
example the CORBA server receives CORBA requests directly (that is, not by using a CORBA
adapter,) and passes data directly to the transformation engine using the memory adapter.
The file and memory utility adapters are provided as part of the base functionality of the Platform API.