Chat now with support
Chat with Support

Identity Manager 8.1.4 - Configuration Guide

About this guide One Identity Manager software architecture Customizing the One Identity Manager default configuration Customizing the One Identity Manager base configuration One Identity Manager schema basics Editing the user interface
Object definitions for the user interface User interface navigation Forms for the user interface Statistics in One Identity Manager Extending the Launchpad Task definitions for the user interface Applications for configuring the user interface Icons and images for configuring the user interface Using predefined database queries
Localization in One Identity Manager Process orchestration in One Identity Manager
Setting up Job servers Configuring the One Identity Manager Service Handling processes in One Identity Manager
Tracking changes with process monitoring Conditional compilation using preprocessor conditions Scripts in One Identity Manager
Using scripts Notes on message output Notes on using date values Using dollar ($) notation Using base objects Calling functions Pre-scripts for use in processes and process steps Using session services Using #LD-notation Script library Support for processing of scripts in Script Editor Creating and editing scripts in the Script Editor Copying scripts in the Script Editor Testing scripts in the Script Editor Testing script compilation in the Script Editor Overriding scripts Permissions for executing scripts Editing and testing script code with the System Debugger Extended debugging in the Object Browser
Reports in One Identity Manager Adding custom tables or columns to the One Identity Manager schema Web service integration SOAP Web Service One Identity Manager as SPML provisioning service provider Processing DBQueue tasks One Identity Manager Service configuration files

Optimizing performance by deleting log entries

If there is a large amount of data, you can specify the number of objects to delete per DBQueue Processor operation and run in order to improve performance. You use configuration parameters to make the choice for each section.

Table 129: Configuration parameters for deleting logged data changes
Configuration parameter Meaning

Common | ProcessState | PropertyLog | Delete

This configuration parameter allows configuration of deletion behavior for logged data changes.

Common | ProcessState | PropertyLog | Delete | BulkCount

This configuration parameter contains the number of entries to be deleted in an operation.

Common | ProcessState | PropertyLog | Delete | TotalCount

This configuration parameter contains the total number of entries to be deleted in any processing run.

Table 130: Configuration parameters for deleting process information
Configuration parameter Meaning

Common | ProcessState | ProgressView | Delete

This configuration parameter allows configuration of deletion behavior for process information.

Common | ProcessState | ProgressView | Delete | BulkCount

This configuration parameter contains the number of entries to be deleted in an operation.

Common | ProcessState | ProgressView | Delete | TotalCount

This configuration parameter contains the total number of entries to be deleted in any processing run.

Table 131: Configuration parameters for deleting process history

Configuration parameter

Meaning

Common | ProcessState | JobHistory | Delete

This configuration parameter allows configuration of deletion behavior for the process history.

Common | ProcessState | JobHistory | Delete | BulkCount

This configuration parameter contains the number of entries to be deleted in an operation.

Common | ProcessState | JobHistory | Delete | TotalCount

This configuration parameter contains the total number of entries to be deleted in any processing run.

Table 132: Configuration parameters for deleting process status entries
Configuration parameter Meaning

Common | ProcessState | Delete

This configuration parameter allows configuration of deletion behavior for process status entries.

Common | ProcessState | Delete | BulkCount

This configuration parameter contains the number of entries to be deleted in an operation.

Common | ProcessState | Delete | TotalCount

This configuration parameter contains the total number of entries to be deleted in any processing run.

Conditional compilation using preprocessor conditions

Conditional compiling of program code is integrated into One Identity Manager. Conditional compilation allows parts of the program code to be parsed whereas other parts remain untouched.

Conditional compiling has the following advantages:

  • Assemblies are reduced in size

  • System configuration organization

  • Improves clarity for the model and rights

  • Speeds up processing

  • Hides unnecessary data in all VB.Net expressions

  • Hides unnecessary model components

Conditional compiling in One Identity Manager is controlled using preprocessor conditions. Preprocessor conditions can be used in:

  • Objects with the Preprocessor condition property.

  • VB.Net expressions

Configuration parameters and their options define the possible preprocessor conditions.

In order to become effective on a system-wide basis, every modification to preprocessor relevant configuration parameters as well as modifications to preprocessor conditions on objects and VB.Net expressions requires the One Identity Manager database to be recompiled.

Detailed information about this topic

Preprocessor-relevant configuration parameters

IMPORTANT: The One Identity Manager database needs to be recompiled every time a preprocessor-relevant configuration parameter and its options are changed.

The Preprocessor relevant parameter option is used to label a configuration parameter as preprocessor relevant. A preprocessor expression is entered in the associated configuration parameter option.

When a preprocessor relevant configuration parameter is set it is valid globally across the system. The preprocessor condition does not come into effect until the database has been compiled.

NOTE: Predefined preprocessor configuration parameters are overwritten during schema installation. Define company-specific, preprocessor-relevant configuration parameters and options in the Designer under the Custom configuration parameter.

To display preprocessor relevant configuration parameters

  1. In the Designer, select Base data | General | Configuration parameters.
  2. In the Configuration Parameter Editor, select the View | Preprocessor definitions menu item.

    The Preprocessor definitions view shows all preprocessor conditions. Double-click an entry to display the configuration parameter.

NOTE: In the Designer, you can find an overview of existing preprocessor dependencies in the One Identity Manager Schema | Preprocessor dependencies category.

Related topics

Preprocessor conditions in objects

IMPORTANT: Each modification to preprocessor objects requires recompiling the One Identity Manager database.

You can enter a preprocessor condition directly for certain objects.

To enter a preprocessor condition

  • In the Preprocessor condition property, enter the preprocessor expressions of the configuration parameters. You can link preprocessor expressions together with AND, OR, NOT, ().
Example

The column Person.RiskIndexCalculated should only be shown in the interface if the risk function is set.

The following preprocessor conditions are entered in the column definition (DialogColumn table).

Table 133: Example for preprocessor conditions
Table Column Preprocessor condition
Employee RiskIndexCalculated COMPLIANCE

If a preprocessor-relevant configuration parameter is enabled or disabled, tasks are created for the DBQueue Processor to calculate all preprocessor and calculation tasks for the affected objects. The Disabled by preprocessor option is updated for each object. If the re-interpretation of the preprocessor conditions leads to a change in the option, the preprocessor interpretation tasks that follow are generated for the dependent objects. User rights can also be affected. After DBQueue Processor has processed the tasks, the database needs to be recompiled.

The interpretation of preprocessor conditions has the following effects:

  • If a table is disabled by a preprocessor condition then all the columns and object definitions that relate to the table and the user interface forms and the associated navigation are disabled.

  • If a primary key column is disabled, all foreign key columns that relate to it are disabled.

  • If a primary key member is disabled according to the preceding rule (for example, in the case of many-to-many tables), then this primary key’s table and all further columns belonging to this table are also disabled.

    This method has the advantage that, for example, when a table such as ADSGroup is disabled then all assignments are automatically disabled, such as the table, DepartmentHasADSGroup.

NOTE: In the Designer, you can find an overview of existing preprocessor dependencies in the One Identity Manager Schema | Preprocessor dependencies category.

Related topics
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating