Identity Manager 8.0 - Configuration Guide

Name of the table in the data model.

The table's usage type provides the basis for reports and the selection of tasks for daily maintenance.

Permitted values are:

The display name is used, for example, to identify the table in a database search or for error output. Translate the given text using the button.

The display template is used to specify the form in which objects will be represented in the administration tool result list. Translate the given text using the button.

Additional display pattern for individual tables containing the object's full name.

Enter the foreign key column that should be used as a basis for displaying tables hierarchically, for example, on assignment forms.

Example:

An Active Directory user account (table ADSAccount) is typically displayed on an assignment form below its Active Directory container (UID_ADSContainer). The Active Directory container (table ADSContainer) is, on the other hand, displayed underneath its Active Directory domain (column UID_ADSDomain). The path for the hierarchy structure is entered as follows:

An alternative list for objects that do not have values in all foreign keys, can be given by a pipe (|).

Example:

(UID_ADSContainer,UID_ADSDomain|UID_ADSDomain)

Spare text box for additional explanation.

Caching behavior for tables in the Designer. This data is only required for system tables. Cache information for a table is composed of the sort order and loading behavior.

Permitted values are:

Tables can have preprocessor conditions added. The table is therefore only available when the preprocessor condition is fulfilled.

If a table is disabled by a preprocessor condition, the option is set by the Database Compiler.

Delete operations are deferred (0 = delete immediately, other: delete after given number of days).

Icon representing the table in the administration tool interface.

Color, with which the control for this table is displayed in the schema overview.

The various target system tables are joined in database layers of type "Proxy" in the Unified Namespace. The table which serves as the proxy view is entered here. Columns of the underlying proxy view are then entered in the column definition.

Example:

The proxy view UNSRoot is used for mapping the tables ADSDomain and LDAPDomain.

List of columns as SQL text. These are used in the view's SELECT statement. To use if columns are mapped twice, for example, or if additional columns of the proxy view need to be filled.

Example:

The view UNSRoot expects the target system type as input in the column UID_DPRNameSpace. This column is not in the tables ADSDomain and LDAPDomain.

The proxy view extension is defined as follows:

Comma delimited list of all FK columns that are required for displaying objects in the scope hierarchy in the Synchronization Editor. List of all columns that lead to tables made available by the parent object.

The table's logical disk store. Associated tables are grouped together in logical disk stores. In the default installation, logical disk stores are predefined for the table in each module of the One Identity Manager and the system tables. You cannot change the assignments. You can create your own logical disk storage for grouping custom tables.

This option determines whether the table should be exported for the SPML schema.

Label for assignment tables (many-to-many tables). Assignment tables are tables are used to create relations between two other tables.

Marks assignment tables, which have a dynamic foreign key as partner.

Tables labeled with this option cannot be excluded from a custom configuration package. These tables are excluded from data transport.

Specifies how assignments and deletions are handled in tables. This option only applies to assignment tables (many-to-many tables) in the application data model.

If the option is not set, assignments and deletions are dealt with directly by the DBQueue Processor.

If the option is set, tasks for the process component "HandleObjectComponent" are placed in the Job queue, which then deal with the appropriate operations. This makes it possible to link specific processes directly to the "Assign" and "Remove" events. This behavior has to be implemented on a custom basis.

Specifies whether the table contents for the data connection can be buffered. The threshold is defined in the configuration parameter "Common\ResidentTableLimit".

Table type.

For more information, see Working with Module Globally Unique Modifiers.

For more information, see Working with Module Globally Unique Modifiers.

Base table that the view is based on.

WHERE clause as database query for setting the database view.

Specify default settings for a column that is assigned when a new data set is added. The values are entered in VB.Net syntax.

Selection script as a VB.Net term, to determine during runtime whether the object passed belongs to the view.

Name of an extension to the view definition.

Specifies whether the view definition extension is generated by the DBQueue Processor.

Database query as a SELECT statement for setting up the database view.

Several extensions for the view definition can be defined. The extensions are linked with each other with the Union operator.

Define actions that are executed before or after saving, loading or discarding an object. The values are entered in VB.Net syntax.

This is information about table sizes, row counts and basic record lengths that are determined once a day by the maintenance tasks. The data material can help to plan capacities and maintenance work on the database.

The Customizer contains special methods and has side effects on the table columns. Several Customizers can be defined for one table. Customizers execute processing, logic which is normally implemented in the object code, such as mutual exclusion of properties.

There are various Customizers contained in the One Identity Manager default installation, which provide specific behavior. Do not modify Customizers as error-free behavior of One Identity Manager would no longer be guaranteed.

Specifies columns that must be collectively unique. The columns are collected into a unique groups.

Name of the group of columns with a unique total value.

Specifies whether empty values are permitted. If all the columns in one group are empty, group uniqueness cannot be tested. If this option is not set, empty values are permitted but only once for each column.

To prevent empty values, define a minimum column length in the column definition.

Comma delimited list of all foreign key columns required for displaying objects in the scope hierarchy in the Synchronization Editor. List of all columns that lead to tables made available by the parent object.