Optim™ components have many features and utilities in common.
To carry out its functions, the Optim solutions rely upon user‑defined objects to supplement objects defined to the database (for example, tables, primary keys, relationships, stored procedures). These user‑defined objects (collectively, Optim objects) are stored in the Optim directory.
The Optim directory is a set of tables used to track processing status and store 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 include:
An access definition is required for archiving and is sometimes used in restoring data.
A column map can be referenced in a table map for an insert or load used in a restore process.
For example, you might use a column map procedure to round year-to-date sales amounts before restoring data for analysis or reporting.
A DB alias name is used as a high-order qualifier for an object or table name, providing information needed to access the appropriate database. A DB alias is needed anytime a database object is referenced. 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.
A primary key can be used to create an Optim relationship, and is required for a table that is changed by a delete, insert, or restore process or a table that is visited more than once in an archive process. A primary key is also required for the row selection or point and shoot feature for an access definition or an archive process.
Relationships are used to determine the data to be retrieved from related tables. Relationships defined to the database are relied upon, 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.
A table map is required for an insert, load, or restore process.
The Archive utilities are directory maintenance, register files, and index maintenance, as well as and the storage profile utility. Other utilities are common to all Optim solutions:
Personal and product options are used to maintain the solution environment. Generally, product options enforce site and system requirements, while you can use personal options to customize the solution for use at each workstation.
Using security options, you can establish as many as three levels of security for using the Optim solutions. Use functional security to control user access to the interface for functions, object security to control access to specific objects in the Optim directory, and archive file security to control access to data in archive files.