14.1 Terminology Information

There are similarities in the functionality between Oracle Data Integrator and Oracle Data Transforms, however, the terminology is different.

The differences in the terminology used in Oracle Data Integrator Studio and Oracle Data Transforms are:

Oracle Data Integrator Studio	Oracle Data Transforms	Functions
Data Server	Connection	Represents the physical object where data is stored. Examples include Database Instances, File Servers, and Cloud Application Instances. The properties contain all information required to connect and access data.
Technology	Connection Type	Examples include Oracle, IBM DB2, Oracle Netsuite, Oracle Object Storage. For the list of supported technologies, see Supported Connection Types.
Physical Schema	Schema	Examples include Database Schema, File server Folder, Object Storage Bucket.
Data Store	Data Entity	A Tabular representation of a data structure. Examples include Database Tables, Files.
Reverse Engineering	Import Data Entity	The process of obtaining the metadata for a filtered set of objects in a Schema. Examples include Table Definitions from an Oracle Schema, VOs from a Cloud Applications Offering.
Model	Data Entity	The container for the imported objects. The properties define the rules for importing (how to filter and so on).
Project	Project	Container for the Transformation Design components (Mappings, Packages, Jobs). This doesn't include Data Servers, Schemas, Data Stores and Folders (which are shared between Projects)
Mapping	Data Flow	The Transformation Design. Defines how data flows from one Data Store to another, and how it is transformed.
Package	Workflow	Defines the sequence in which Mappings will be executed, together with what happens of failure conditions.
Job / Session	Job	The execution of a Package, Mapping or Reverse Engineer.
Schedule	Schedule	The rules for when a session executes.
Resource	Resource	Something you can schedule (a mapping or package).