Self Service Password Reset provides logs for your to troubleshoot any issues that might occur. The system uses Apache log4j for logging. Apache log4j is a Java-based logging utility that allows logging to a variety of outputs such as files, syslog, NT event log, databases, and so forth.
You configure the logging settings through the Configuration Editor and you view the logs through the administration console for Self Service Password Reset. The system also outputs a number of logs to the file system depending on the options you configure.
You configure the setting for logging in the Configuration Editor. A number of settings use the same log levels. Depending on what you need to see, you set a different level of severity for the logs. The following list includes available log levels for all settings in order of severity:
Most detailed information. Use this level during initial configuration.
Detailed information on the flow through the system.
Informational messages that highlight the progress of the application at coarse-grained level. Use this level for normal operations. This is the default log level for StdOut.
Potentially harmful situations.
Runtime errors or unexpected conditions.
Severe errors that cause premature termination.
To configure logging:
Log in to Self Service Password Reset at https://dns-name/sspr as an administrator.
In the toolbar, click your name.
Click Configuration Editor.
Click Settings > Logging.
Configure the following settings:
Select the appropriate log level for StdOut. Most servlet containers redirect StdOut to a log file. For example, Tomcat logs StdOut output to the tomcat/logs/catalina.out file by default.
Select the appropriate log level for the local database. You view the log events written to the local database in the Administrator event log viewer. For more information, see Viewing Logs.
Select the appropriate log level to log events to the local file log. The system writes the log files to the WEB-INF/logs directory of the servlet.
Set the maximum log events stored in the local database. Each 100,000 log events consumes approximately 100 MB of disk space. The local database retains this number of events and uses these events to display in the log viewer. For more information, see Viewing Logs.
This setting does not affect the normal log files configured in the log4jconfig.xml file or the log file settings for Tomcat.
Set the maximum age of events stored in the local database (seconds). The system periodically purges events older than the configured value. The default value is four weeks (60s * 60m * 24h * 7d * 4w = 2419200). The system does not remove events due to age if you specify a value of 0.
Enable this option to send an email alert once a day (at 0:00 GMT) that contains a summary of the statistics and health for the day.
In the toolbar, click Save changes.
(Conditional) To log all LDAP events to the Trace logging level:
In the Configuration Editor, click LDAP > LDAP Settings > Global.
Select Enable LDAP Wire Trace. For more information, see Configuring LDAP Settings.
In the toolbar, click Save changes.
Self Service Password Reset allows you to view the logs through the administration console. The option you set in Configuring Logging Settings determines what the log shows. You can also change the log level through the viewer.
To view the log:
Log in to Self Service Password Reset at https://dns-name/sspr as an administrator.
In the toolbar, click your name.
Click View Log.
Select the appropriate log level, then click Refresh to see that level.
(Conditional) To save the information to a file, right click and select Save page as.
Close the separate browser window to return to the administration console.