Optim Directory and Common Optim Objects

The Optim™ Directory is a set of tables in which Optim tracks processing status and stores objects needed for processing. You must use the Configuration program to create or configure the Directory tables and stored procedures needed to access the Directory.

Objects in the Directory that are common to Optim components include the following:

Access Definitions
An Access Definition identifies a set of related data to be processed by Optim. It references the database tables and their relationships, and provides criteria to select specific rows within tables. An Access Definition is required for an Extract Process.
Column Maps
A Column Map provides specifications needed to match columns between two tables referenced in a Table Map. Also, a Column Map can be used to transform data, age dates in tables, and exclude one or more columns from processing. A Column Map can be referenced in a Table Map for an Insert or Load Process.
Column Map Procedures
A Column Map Procedure facilitates data transformations in a Convert, Insert, Load, or Restore Process that are beyond the scope of native Column Map functions.
DB Aliases
A DB Alias provides parameters needed to connect with a specific database. A DB Alias name is used as a high-order qualifier for an object or table name, providing information that Optim needs to access the appropriate database. A DB Alias is needed anytime Optim references a database object; for example, to qualify the name of an Optim primary key, Optim relationship, or a database table referenced in an Access Definition, Column Map, or Table Map.
Primary Keys
Primary key columns uniquely identify each row in a database table. A primary key can be used to create an Optim relationship, and is required for a table that is changed by an Insert Process or a table that is visited more than once in an Extract Process. A primary key is also required to enable the row selection (Point and Shoot) feature for an Access Definition or an Extract Process.
Relationships
A relationship is a defined connection between the rows of two tables that determines the parent or child rows to be processed and the order in which they are processed. Optim uses relationships to determine the data to be retrieved from related tables and rely upon relationships defined to the database, when available. However, you can also define relationships to supplement those in the database. Generally, a relationship is needed in a process that uses an Access Definition.
Table Maps
A Table Map identifies and matches two tables or sets of tables in an Insert or Load Process and can exclude one or more tables from processing. A Table Map is required for an Insert, Load, or Restore Process.