Configuring notification behavior for DBQueue Processor initialization
If errors occur during initialization of the DBQueue Processor, messages are written to the application log. You can use the results display in the Microsoft Management Console, for example, to view the application log.
Use the QBM | DBServerAgent | CreateNotification configuration parameter to configure in which cases error messages are written to the application log. In the Designer, you can modify the configuration parameter as required.
Permitted values are:
-
0: No logging.
-
1: Only success messages are logged.
-
2: Only error messages are logged.
-
3: All messages are logged.
For more information about the DBQueue Processor, see the One Identity Manager Configuration Guide.
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).
-
Permitted values for CrashRecorderLevel are Debug, Error, Fatal, Info, Off, Trace and Warn.
Example: Enabling 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>
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 .exe format.
Detailed information about this topic
Application-specific configuration files
One Identity Manager components, such as the Manager or the Designer, have a configuration file for .NET exe's 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.
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.
NOTE: Entries are case-sensitive.
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
