The Optim™ Directory
is a set of tables in which Optim stores
the objects that are needed for processing and tracking processing
status. Before you use Optim,
you must use the Configuration program to create or configure the Optim Directory tables and stored
procedures that are needed to access the Directory.
For more information, see the Installation
and Configuration Guide.
You can create the Optim Directory
in one of the following databases: Oracle, SQL Server, or DB2® for Linux, UNIX,
and Windows. You can create
DB Aliases for other supported databases, as well as these databases,
but you cannot put the Optim Directory
in them. For example, you can create DB Aliases to process data for
the following data sources, but cannot put the Optim Directory in them: Informix®, Sybase ASE, DB2 for z/OS®,
Teradata, Netezza®, PostgreSQL,
and Hive (for Hadoop).
Important Optim Directory
objects include the following objects:
- DB Aliases
- A DB Alias provides parameters that are needed to connect with
a specific database. It is used as a high-order qualifier for an object
or table name and tells Optim how
to access the appropriate database.
- Access Definitions
- An Access Definition identifies the set of related data to be
processed by Optim. It identifies
the database tables and their relationships, and provides criteria
to select specific rows within tables.
- Table Maps
- A Table Map defines the correlation between two tables or sets
of tables in an Insert, Update, Restore, or Compare Process and can
be used to exclude one or more tables from processing.
- Column Maps
- A Column Map defines the correlation between columns in two tables.
Additionally, a Column Map can be used to transform data, age dates
in tables, and exclude one or more columns from processing.
- Column Map Procedures
- A Column Map Procedure is a custom program that is referenced
by a Column Map and is used for special processing and data manipulation
that is beyond the scope of native Column Maps.
- Primary Keys
- Values in primary key columns uniquely identify each row in a
database table.
- Relationships
- A Relationship determines the parent or child rows to be processed
and the order in which they are processed.
- Processing Definitions
- A Processing Definition provides parameters that are needed to
run a process, including the names of generated files, the Access
Definition that is used for the process, and the source of processed
data. You can sometimes use parameters in a process definition to
override parameters that are defined for the Access Definition. Process
definitions include the following Request types: Archive, Compare,
Convert, Delete, Edit, Extract, Insert, Load, Report, and Restore.
- Utility Definitions
- A Utility Definition is used for some type of specialized processing.
Utility definitions include Calendars, Storage Profiles, and Currency
Tables.
- Security Definitions
- A Security Definition provides parameters that are needed for Optim Security.
- Access Control Domains (ACDs) map
roles to network accounts.
- The (Default) ACD provides Functional
Security parameters.
- Access Control Lists (ACLs) provide
parameters that are used with Object Security.
- File Access Definitions (FADs) provide
parameters that are used with Archive File Security.
- Archive File Registrations
- Archive File Registrations provide all information that is needed
to locate and process data on archive files.
After one or more Optim Directories
are created, you can use the
Optim Directory Editor to
- Browse a list of Optim Directories available to the workstation.
- Establish or change the Default
Directory or connection for the workstation.
- View Optim Directory
attributes while connected.
- Modify the code page or connection
string for an Optim Directory
connection.
Contents
This
section describes the specifications on the Optim Directory
Editor.