Chat now with support
Chat with Support

Identity Manager 8.1.4 - Process Monitoring and Troubleshooting Guide

About this guide Monitoring handling of processes Support for error localization in One Identity Manager Configuring logs in One Identity Manager One Identity Manager configuration files

Enabling the crash recorder

The crash recorder saves the previous 128 messages starting at Debug level and issues these in the error message window. You can configure the crash recorder using the configuration files for the One Identity Manager tools (*.exe.config).

Example for activating the crash recorder in the configuration file

<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 CrashRecorderLevel are Debug, Error, Fatal, Info, Off, Trace and Warn.

Related topics

One Identity Manager configuration files

General configuration settings can be preset in a configuration file. The configuration file is kept in the program directory. Each administration tool can take its settings from a configuration file in NET executable format. Valid global configuration settings can also be defined through a configuration file in One Identity Manager's own format.

Detailed information about this topic

Application-specific configuration files

NOTE: Use the globallog.config configuration file to define global settings that apply to all One Identity Manager components.

One Identity Manager components, such as the Manager or the Designer, have a configuration file for .NET executables with a predefined format for this. There is a configuration section in the file for each of the different modules of a One Identity Manager component.

NOTE: Entries are case-sensitive.

The root in the XML file is always called configuration. All other sections of the configuration file must be in the mandatory configSections section and their type must be defined.

Format of the configuration file using .exe.config as an example

<?xml version="1.0" encoding="utf-8" ?>

<configuration>

<configSections>

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

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

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

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

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

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

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

</configSections>

<dialogplugins>

<add key="ComplianceRuleSimulation" value="VI.DialogEngine.Plugins.ComplianceRuleSimulation, AE.DialogEngine.Plugins" />

<add key="ComplianceRuleSimulationSummary" value="VI.DialogEngine.Plugins.ComplianceRuleSimulationSummary, AE.DialogEngine.Plugins" />

</dialogplugins>

<consistencychecks>

<add key="AE" value="VI.ConsistencyChecks.AE.dll" />

<add key="Common" value="VI.ConsistencyChecks.Common.dll" />

</consistencychecks>

<formarchives>

<add key="Forms" value="archive:.\???.Forms*.vif;10" />

<add key="CustomForms" value="archive:.\AE.CustomForms.*.vif;5" />

<add key="CommonForms" value="archive:.\Common.Forms*.vif;5" />

</formarchives>

<vicontrols>

<add key="defaultcontroldesign" value="System" />

</vicontrols>

<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

Global configuration file for One Identity Manager tools

The Global.cfg is an XML configuration file in One Identity Manager’s own simplified format. The advantage of this file is that run-time loading is supported. Each of the different modules has its own section allocated within the file.

NOTE: Entries are case-sensitive. Both the sections and the names of the values must be written in lower case.

You can find an example of a configuration file on the installation medium in the QBM\dvd\AddOn\SDK\ConfigSample directory. If the file Global.cfg is in the program directory, it is used when the One Identity Manager tools start up.

The root in the XML file is always called configuration. Each configuration file module and its values are defined in a section category respectively.

Format of global.cfg

<configuration>

<category name="settings">

<value name="language">English</value>

<value name="autoupdateenabled">true</value>

<value name="connectiontimeout">15</value>

</category>

<category name="connections">

<value name="database display 1">ConnectionString</value>

<value name="database display 2">ConnectionString</value>

</category>

</configuration>

TIP: To generate the (ConnectionString) connection parameters, use the Config Encryptor program. You will find this program on the installation medium in the directory QBM\dvd\AddOn\ConfigEncryptor.

Related topics
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating