Chat now with support
Chat with Support

Identity Manager 9.2.1 - 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 Application-specific configuration files

Which access level does the user use?

To deploy a One Identity Manager database on a SQL Server or a managed instance in Azure SQL Database, you are provided with SQL Server logins and database users for administrative users, configuration users, and end users. Permissions at server and database level are matched to suit the user's tasks.

For more information about users and their permissions, see the One Identity Manager Installation Guide. For more information about minimum access levels for One Identity Manager tools, see the One Identity Manager Authorization and Authentication Guide.

NOTE:

  • If you select an existing database connection in the connections dialog, the access level of the login to be used is shown in a tooltip.

  • Some user interfaces expect configuration user permissions at least. Logging in as an end user is not possible in this case.

To find the access level of the logged in user

  • To display user information, double-click the icon in the program status bar

    On the System user tab, in the SQL access level field, you will see the access level for the current login. The access levels displayed are End user, Configuration user, Administrative user, System administrator, and Unknown.

Related topics

Configuring logs in One Identity Manager

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

Configuring retention times of messages in the system journal

Table 14: Configuration parameters for logging in the system journal
Configuration parameter Meaning

Common | Journal

General parameter for configuring the system journal.

Common | Journal | LifeTime

Maximum retention time in days for a system journal entry in the database. Older entries are deleted from the database.

Common | Journal | LifeTime | D

Retention time in days for messages with the Debug information level.

Common | Journal | LifeTime | E

Retention time in days for messages with the information Error level.

Common | Journal | LifeTime | I

Retention time in days for messages with the Info information level.

Common | Journal | LifeTime | T

Retention time in days for messages with the Trace information level.

Common | Journal | LifeTime | W

Retention time in days for messages with the Warning information level.

Common | Journal | Delete

Configuration of deletion behavior for system messages.

Common | Journal | Delete | BulkCount

Number of entries to be deleted in any operation.

Common | Journal | Delete | TotalCount

Total number of entries to be deleted in any processing run.

Messages in the system journal are regularly deleted by the DBQueue Processor.

To delete log entries in the system journal

  • In the Designer, enable the Common | Journal | LifeTime configuration parameter and enter the maximum retention period for the entries in the system journal. Use the configuration subparameters to specify the retention time for each information 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. To do this, use the Common | Journal | Delete | BulkCount and Common | Journal | Delete | TotalCount configuration parameters.

Logging process handing errors in the system journal

For more information about editing processes and process steps, see the One Identity Manager Configuration Guide.

To log error in process handing in the system journal

  • At the process steps in the Designer, enable the Log errors to journal option.

Related topics
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating