You can enable and configure how the system performs logging. Logging is the main tool you use for debugging the Identity Server configuration. All administrative and end-user actions and events are logged to a central event log. This allows easy access to this information for security and operational purposes. Additionally, the log system provides the ability to monitor ongoing activities (such as identity provider authentication activity, up-time of the system, and so on) by using this page. File logging is not enabled by default.
Identity Servers and Embedded Service Providers use these logging features. If you change or enable logging, you must update the Identity Server configuration (using Update Servers on the Servers page) and restart the Embedded Service Providers, in order to apply the changes. When you disable logging, you must also restart the Embedded Service Providers.
This section describes the following about component logging:
File logging records the actions that have occurred. For example, Web servers maintain log files listing every request made to the server. With log file analysis tools, it’s possible to get a good idea of where visitors are coming from, how often they return, and how they navigate through a site. The content logged to file logging can be controlled by specifying logger levels and by enabling statistics logging.
In the Administration Console, click > > > .
The following options are available for component logging in the section:
Enabled: Enables file logging for this server and its associated Embedded Service Providers.
Echo To Console: Copies the Identity Server XML log file to /var/opt/novell/tomcat5/logs/catalina.out. You can download the file from > If you want to view Identity Server logs mixed with logs from other application devices, you use catalina.out.
For the Embedded Service Providers, it depends upon the platform:
For a Linux Access Gateway, this sends the messages to the catalina.out file of the Access Gateway.
For a SSL VPN, this sends the messages to the catalina.out file of the SSL VPN.
Log File Path: Specifies the path that the system uses to save the Identity Server XML log file. The default path is tomcat application directory/web-inf/logs.
If you change this path, you must ensure that the user associated with configuring the identity or service provider has administrative rights to the Tomcat application directory in the new path.
If you have a mixed platform environment (for example, the Identity Server is installed on Windows and the Access Gateway is on Linux), do not specify a path. In a mixed platform environment, you must use the default path.
Maximum Log Files: Specifies the maximum number of Identity Server XML log files to leave on the machine. After this value is reached, the system deletes log files, beginning with the oldest file. You can specify , or values of 1 through 200. 10 is the default value.
File Wrap: Specifies the frequency (hour, day week, month) for the system to use when closing an XML log file and creating a new one. The system saves each file based on the time you specify and attaches the date and/or time to the filename.
GZip Wrapped Log Files: Uses the GZip compression utility to compress logged files. The log files that are associated with the option and the value are stored in the directory you specify in the field.
In the section, you can specify the logging sensitivity for the following:
Application: Logs system-wide events, except events that belong to a specific subsystem.
Liberty: Logs events specific to the Liberty IDFF protocol and profiles.
SAML 1: Logs events specific to the SAML1 protocol and profiles.
SAML 2: Logs events specific to the SAML2 protocol and profiles.
STS: Logs events specific to the STS protocol.
CardSpace: Logs events specific to the CardSpace protocol.
WS Federation: Logs events specific to the WS Federation protocol.
Web Service Provider: (Liberty) Logs events specific to fulfilling Web service requests from other Web service consumers.
Web Service Consumer: (Liberty) Logs all events specific to requesting Web services from a Web service provider.
Use the drop-down menu to categorize logging sensitivity. Higher logging levels include the lower levels in the log.
Off: Turns off component file logging for the selected item.
Severe: Logs serious failures that can cause system processing to not proceed.
Warning: Logs potential failures, but the impact on execution is minimal. Warnings indicate that you should be aware that this event is happening and might want to make a configuration change to avoid it.
Info: Logs informational events. No execution or data impact occurred.
Verbose: Logs static configuration information. The system logs any configuration errors under one of the primary three levels: Severe, Warning, and Info.
Debug: Includes all of the preceding levels.
(Optional) Enable statistics logging:
When statistics logging is enabled, the system periodically sends the system statistics, in string format, to the current file logger. Statistical data (such as counts, levels, and so on) are included in the file log.
In the section, select .
In the field, specify the time interval in seconds that statistics are logged.
Click .
Update the Identity Server configuration (using on the Servers page).
Restart the Embedded Service Providers on the Access Gateways, in order to apply the changes.
When you disable component logging, you need to update the Identity Server configuration and restart the Embedded Service Providers.
On Windows, you need to monitor the size of the log files manually. On Linux, the logrotate daemon manages the log files located in the following directories:
/var/opt/novell/tomcat5/logs /opt/volera/roma/logs/
The logrotate daemon has been configured to scan the files in these directories once a day. It rolls them over when they have reached their maximum size and deletes the oldest version when the maximum number of copies have been created.
If you want to modify this behavior, see the following files in the /etc/logrotate.d directory:
novell-tomcat5 novell-devman
For information about the parameters in these files, see the documentation for the logrotate daemon.