3.1 About Event Logging

The Identity Manager User Application implements logging by using log4j, an open-source logging package distributed by The Apache Software Foundation. See Logging Services for details. By default, event messages are logged to the system console and to the application server’s log file at logging level INFO and above. You can also configure the User Application to log to Novell® Audit and OpenXDAS. Events are logged to all activated loggers.

The default behavior of the JBoss server is to limit the console log4j appender to display log messages with a verbosity of INFO or less. In order to see log messages for more verbose levels (for example, DEBUG), you need to examine the server log file.

IMPORTANT:If you are logging to Novell Audit, review the Novell Audit documentation.

WARNING:You must use Novell Audit (or Sentinel) to preserve documents that you digitally sign. Digital signature documents are not stored with workflow data in the User Application database, but are stored in the logging database. You must enable logging to preserve these documents.

The log4j configuration settings are in

3.1.1 About the Log Level Settings

Console logging involves synchronized writes. This means that logging can become a processor usage issue as well as a concurrency impedance. You can change the priority value default setting to ERROR, on a JBoss server, by modifying the setting in the <installdir>/jboss/server/IDM/conf/jboss-log4j.xml. Locate the root node that looks like this:


   <root>
      <priority value="INFO"/>
      <appender-ref ref="CONSOLE"/>
      <appender-ref ref="FILE"/>
   </root>

Change the priority value to:


<root>
      <priority value="ERROR"/>
      <appender-ref ref="CONSOLE"/>
      <appender-ref ref="FILE"/>
</root>

Assigning a value to the root ensures that any appenders that do not explicitly have a level assigned inherit the root's level.

3.1.2 Changing the User Application Log Level Settings

The User Application enables you to change the log level settings of individual loggers.

  1. Log in to the User Application as the User Application Administrator.

  2. Select the Administration tab.

  3. Select the Logging link.

  4. Change the Log Level of any logger.

  5. To save the changes for application server restarts, select Persist the logging changes.

  6. Click Submit.

The User Application logging configuration is saved in the file idmuserapp_logging.xml. On JBoss, the path is <installdir>/jboss/server/IDM/conf/idmuserapp_logging.xml.