Chat now with support
Chat with Support

Identity Manager 8.0 - Configuration Guide

One Identity Manager Software Architecture Working with the Designer Customizing the One Identity Manager Default Configuration Checking Data Consistency Compiling a One Identity Manager Database Working with Change Labels Basic System Configuration Data
One Identity Manager Authentication Module Database Connection Data Configuration Parameters for System Configuration Setting up the Mail Notification System Enabling More Languages for Displaying and Maintaining Data Displaying Country Information Setting Up and Configuring Schedules Password Policies in One Identity Manager Reloading Changes Dynamically TimeTrace Databases Machine Roles and Server Functions Files for Software Update Operating Systems in Use System Configuration Reports Using Predefined Database Queries Managing Custom Database Objects within a Database
The One Identity Manager Data Model Granting One Identity Manager Schema Permissions Working with the User Interface
Object definitions for the User Interface User Interface Navigation Forms for the User Interface Statistics in the 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 Language Dependent Data Representation
Process Orchestration in One Identity Manager
Declaring the Job Server One Identity Manager Service Configuration Handling Processes in the One Identity Manager
Tracking Changes with Process Monitoring Conditional Compilation using Preprocessor Conditions One Identity Manager Scripts Maintaining Mail Templates Reports in the One Identity Manager Custom schema extensions Transporting One Identity Manager Schema Customizations Importing Data Web Service Integration SOAP Web Service One Identity Manager as SPML Provisioning Service Provider Searching for Errors in the One Identity Manager Processing DBQueue Tasks One Identity Manager Configuration Files

Logging Messages in the Database Journal

Table 358: Configuration Parameters for Logging in the Database Journal
Configuration parameter Meaning
Common\Journal General parameter for configuring the database journal.
Common\Journal\LifeTime

Use this configuration parameter to specify the maximum amount of time (in days) that a database journal entry can be stored in the database. Older entries are deleted from the database.

Common\Journal\LifeTime\D

This configuration parameter contains retention period (in days) for entries with type 'Debug'.

Common\Journal\LifeTime\E

This configuration parameter contains retention period (in days) for entries with type 'Error'.

Common\Journal\LifeTime\I

This configuration parameter contains retention period (in days) for entries with type 'Info'.

Common\Journal\LifeTime\T

This configuration parameter contains retention period (in days) for entries with type 'Trace'.

Common\Journal\LifeTime\W

This configuration parameter contains retention period (in days) for entries with type 'Warning'.

Common\Journal\LoginAudit Logs successful One Identity Manager logins.

Common\Journal\Delete

This configuration parameter allows configuration of deletion behavior for system messages.

Common\Journal\Delete\BulkCount

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

Common\Journal\Delete\TotalCount

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

The database journal is used to store information, warning and error messages from different components of One Identity Manager, for example, DBQueue Processor, Configuration Wizard or One Identity Manager Service. Actions in the program "Job Queue Info", such as re-enabling process steps, are also written to the database journal.

To log error in process handing in the database journal

  • Set the option Log errors to journal in the process steps.
    1. Open the process in the Process Editor.
    2. Click on the element for the process step in the process document.
    3. Set the option Log errors to journal on the "Error handling" tab.

To log One Identity Manager successful logins

  • Set the configuration parameter "Common\Journal\LoginAudit" in the Designer.

To delete log entries in the database journal

  • Set the configuration parameter "Common\Journal\LifeTime" in the Designer and enter the maximum retention time for entries in the database journal. Use the configuration sub parameters to specify the retention period for each warning level.
  • 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. Use the configuration parameter "Common\Journal\Delete\BulkCount" and "Common\Journal\Delete\TotalCount" to do this.
  • Configure and set the schedule "Delete journal" in the Designer.
Related Topics

Writing the One Identity Manager Log

Writing the One Identity Manager Log

One Identity Manager provides various options for extending its log. The log can be configured for each One Identity Manager component.

Detailed information about this topic

Logging Messages using NLog

Each One Identity Manager component supports message logging using the integrated NLog functionality. For an exact description and functionality, see the online help (http://nlog-project.org/).

Setting for logging with Nlog are made in the "nlog" section in the One Identity Manager component's configuration files. Use the variable appName to pass the One Identity Manager component names. The configuration of the logs is defined in the global configuration file globallog.config. This file is referenced in the One Identity Manager component's configuration files.

In the One Identity Manager default installation, the log files are written to the directory %LocalAppData%\One Identity\One Identity Manager\<appName> under the name <appName>.log, where appName is the name of the One Identity Manager component. All messages with a minimum information level of "info", are recorded in the <appName>.log. The files are kept for 7 days and backed up daily. All messages with the information level "fatal" are additionally recorded in the event log for the source One IdentityOne Identity Manager <appName>.

Example of a Configuration File

<configuration>

<configSections>

...

<section name="nlog" type="NLog.Config.ConfigSectionHandler, NLog"/>

</configSections>

...

<nlog autoReload="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">

<variable name="appName" value="Manager"/>

<include file="${basedir}/globallog.config" ignoreErrors="true"/>

</nlog>

...

</configuration>

Related Topics

Enabling the Crash Recorder

The crash recorder saves the last 128 message from the "Debug" level and shows them in an error message window. The crash recorder is configured through the One Identity Manager tool's configuration file.

Example: Configuration file entry for a One Identity Manager component

<configuration>

<configSections>

...

<section name="connectionbehaviour" type="System.Configuration. NameValueSectionHandler" />

</configSections>

...

<appSettings>

<add key="CrashRecorderBuffer" value="128" />

<add key="CrashRecorderLevel" value="Error" />

</appSettings>

<connectionbehaviour>

...

</connectionbehaviour>

...

</configuration>

If the variable CrashRecorderBuffer is set to the value 0, the crash record functionality is disabled. Permitted values for the CrashRecorderLevel are "Debug", "Error", "Fatal", "Info", "Off", "Trace" and "Warn".

Related Topics
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating