Common Elements

The Optim Directory is a set of tables that store objects needed for processing. You must use the Configuration program to create or configure the Optim Directory tables and stored procedures needed to access the Directory.

Objects in the Optim Directory that are common to these products include:

• Access Definitions. An Access Definition identifies a set of related data to be processed. It references the database tables and their relationships, and provides criteria to select specific rows within tables. An Access Definition is sometimes used in a Compare 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 is used in a single table Compare Process and can be referenced in a Table Map used in a Compare Process.

• Column Map Procedures. A Column Map Procedure facilitates data transformations in a 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. It is used as a high-order qualifier for an object or table name, in order to access the appropriate database.

  A DB Alias is needed anytime you reference 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 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.

  Relationships are used to retrieve related rows from tables and may be available to the database. 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 used in a Restore Process and can exclude one or more tables from processing. A Table Map is required for a Compare Process.

Utilities common to the Optim components include:

• Schedule. Use the Schedule Utility to schedule processes and monitor processing.
• Browse. Use the Browse Utility to review the contents of an Extract or Control File.
• Export/Import. Use the Export/Import Utilities to copy Optim objects from one Optim Directory to another.

These utilities are discussed in detail in the Common Elements Manual.

Options are used to maintain the environment. Generally, Product Options parameters enforce site and system requirements, while Personal Options customize Optim for use at each workstation.

Refer to the Installation and Configuration Guide for Product Options and the Common Elements Manual for Personal Options.

Security options allow you to establish as many as three levels of security for using Optim. Functional security allows you to control user access to the interface for functions provided by Optim, object security allows you to control access to specific objects in the Optim Directory, and Archive File security allows you to control access to data in Archive Files. All security options are documented in the Installation and Configuration Guide .

The Compare processes and utilities are discussed in the following sections.