Glossary

ABAP script

A script that can be generated in OWB that extracts and loads data from SAP systems.

activity

A unit of work for a process flow. See also process flow.

analytic workspace

A container within Oracle Database that stores data in a multidimensional format. Analytic workspaces provide the best support for OLAP processing.

Code Template (CT)

A cross-platform, reusable object that contains the information required to perform a specific set of tasks against a specific technology or set of technologies, for example data integration or data transformation tasks.

Code Template mapping

A mapping that contains an association with a Code Template. Typically used to extract or load data (both with and without transformations) from non-Oracle databases, such as IBM DB2 and Microsoft SQL Server.

connector

A logical link created by a mapping between a source location and a target location.

Control Center Agent (CCA)

The agent that runs the Code Templates in the Oracle Containers for J2EE (OC4J) server. You must start the Control Center Agent before you deploy Code Templates or CT mappings. Also referred to as the J2EE Runtime.

Control Center Manager

The graphical console of the Control Center Service for centrally viewing and managing all aspects of deployment and execution. Provides access to the information stored in the active configuration. Includes update capabilities to enable management of your data system's life cycle.

Control Center Service

A service that runs outside the database, which can monitor and execute things that cannot be run directly in the database, such as: PL*SQL scripts, SQL*Loader, and shell scripts. Enables deployment of OWB mappings and processes to targets (databases, etc.), and the execution of these mappings and processes.

control row

A row that links fact data to a dimension at any level.

CT mapping

See Code Template mapping.

cube

A data object that contains measures, and links to one or more dimensions. The axes of a cube contain dimension members, and the body of the cube contains measure values.

data auditors

Processes that provide data monitoring by validating data against a set of data rules to determine which records comply and which do not.

data rule

Metadata (as definitions) about data profiling results, which can be bound to the profiled data objects, and then be available in any context in which the profiled objects are used in ETL.

data transformation

A set of operations, which are specified in a mapping, that change source data into consistent, compatible output for a target.

DDL script

A script that can be generated in OWB that creates or drops database objects.

deployable parameter

The parameter for an object that specifies it is to be deployed. By default this parameter is selected. To prevent an object from being deployed, clear this parameter.

deployable parameter

The parameter for an object that specifies it is to be deployed. By default this parameter is selected. To prevent an object from being deployed, clear this parameter.

deployment

The process of creating physical objects in a target location according to the logical objects defined in an OWB workspace.

dimension

An object that contains additional metadata to identify and categorize data. Same as dimensional object. Can be a cube.

dimension attribute

A descriptive characteristic of a dimension member, having a name and a data type.

dimensional object

Refer to dimension.

ETL

The process of extracting data from its source location, transforming it as defined in a mapping, and loading it into target objects (or schemas). ETL stands for extract, transform, and load.

execution

The process of running the code for the ETL logic that is defined in the deployed objects in order to instantiate the logic within the objects.

Expert

Mini-applications or task-flows that perform a specific sequence of tasks in OWB.

flat files

Non-hierarchical, non-object-oriented file structures in plain text comma-separated or tab-separated format, ASCII format, or proprietary binary formats.

folders

Structures in which to organize all or some objects within a target module based on specific object characteristics. For example, you may create user folders to group tables based on their functionality (sales, marketing, administration and so forth).

hierarchy

A structure that uses ordered levels to organize data. OWB uses hierarchies to define relationships between adjacent levels in time dimensions.

item folder

A result set of data, similar to a database view. Item folders store information in the same manner as tables.

J2EE Runtime

Refer to Control Center Agent (CCA). Also, sometimes called Java Runtime.

level attribute

For time dimensions, a descriptive characteristic of a level value.

location

Object that stores the connection information to the various files, databases, and applications that OWB accesses for extracting and loading data. Locations also store connection information to ETL management tools and Business Intelligence tools.

logical definition

The data objects created when you design a target schema.

mapping

An object that contains operations for extraction, transformation, and loading (ETL) that moves data from sources to targets.

mapping operator

The representation of an operation for a distinct task you want to perform in a mapping. For example, operations include extracting data, loading data, and transforming data.

match bin set

A match record set consisting of one or more similar records.

metadata

Data that describes the contents of objects in a data set.

module

A container object that appears in the Projects Navigator and that corresponds to a specific location in the Locations Navigator. A module can correspond to only one metadata location and data location at a time.

ODI

See Oracle Data Integrator.

OMB*Plus

The OWB scripting API, which is based on the Java implementation of Tcl called Jacl.

OMB

The OMB-prefixed commands ('B' for batch component) of OMB*Plus.

OMU

A subset of OMB*Plus that provides scripting commands for manipulating the user interface in OWB. Also OMU-prefixed commands ('U' for UI component).

operator

OWB contains pre-built operators for transformations, mappings, names and addresses, and so forth. Operators in OWB are customizable and take advantage of the library of PL/SQL functions, procedures, package functions, and package procedures for Oracle Database. See also mapping operator.

Oracle Data Integrator

Oracle Data Integrator (ODI). See Oracle Fusion Middleware Developer's Guide for Oracle Data Integrator.

OWB Repository

The single, unified repository for the database instance, which is pre-seeded with a schema and database objects. The runtime environment and the design environment reside in this single repository. The repository schema, named OWBSYS, gets created when you install Oracle Database.

pluggable mapping

A reusable grouping of mapping operators that works as a single operator. Similar in concept to a function in a programming language.

process flow

An object that describes dependencies and activities between OWB mappings and external processes, applets, or applications. Process flows begin with a start activity and conclude with an end activity and can also start other process flows. Compare to schedule. See also activity.

process flow module

A container for a grouping of process packages.

process flow package

A container for a grouping of process flows.

project

The highest-level and largest object in the OWB workspace. Each project contains the metadata and definitions for objects in the data system that contains the sources and targets.

relational target schema

A target schema that contains relational data objects such as tables, views, materialized views, and sequences. All of the data for a data store or data warehouse is contained in these objects.

repository

Refer to OWB Repository.

SQL*Loader control file

A file or script that can be generated in OWB that extracts and transports data from file sources.

table function

A set of operators that enable manipulation of a set of input rows, which return another set of rows of the same or different cardinality. Can return a set of output rows that can be queried like a physical table.

target module

A container that holds the metadata definitions of all your data warehouse objects. Each target module corresponds to a target location that represents the physical location where the objects are stored.

target schema

A schema that contains the data objects that store your data warehouse data. You can design a relational target schema or a dimensional target schema.

transportable module

Type of module that enables rapid copying of a group of related database objects in one database, to be pasted or inserted into another database.

transformation operators

Prebuilt operators that enable commonly performed operations such as filtering, joining, and sorting. OWB also includes prebuilt operators for complex operations such as merging data, cleansing data, or profiling data.

user folder

A folder you can create to organize all or some objects in a target module based on specific object characteristics. Related tables and views that must be generated or deployed together can be placed under a common folder. For example, you may create user folders to group tables based on their functionality (sales, marketing, administration and so forth).

validation

The process of verifying metadata definitions and configuration parameters to ensure that data object definitions are complete and that scripts can be generated and deployed.

value-based hierarchy

A dimension in which hierarchical relationships are defined by a parent dimension attribute and a child dimension attribute.

workspace

The OWB structure that contains all the related projects and their objects. Graphically displayed as the canvas in the Design Center where OWB windows, navigators, wizards, and dialog boxes are laid out to create a work environment that one or more users log in to.