Working with logs
To debug an issue in Remedy Single Sign-On, check the log files described in this topic.
Remedy SSO agent logs
To set the log level for the Remedy SSO agent
By default, the log level is set to INFO on the Remedy SSO agent. To modify the log level on the Remedy SSO agent, update the rsso-log.cfg file available in the class path of an integrated application. See the documentation of the integrated application for information about the location of the file.
Alternatively, specify the configuration path to rsso-log.cfg through the following system property:
To configure logging for the Remedy SSO agent
To configure the Remedy SSO agent, modify the following parameters in the rsso-log.cfg file:
Logging file name.
SEVERE, WARNING, INFO, FINER, and FINEST log levels are supported.
|General number of logging files.|
The maximum size (in bytes) of one logging output file. The default value is 10 MB.
|Directory of the log files.|
This directory is used if rsso.log.dir and catalina.home are empty. If this parameter is not specified, java.io.tmpdir is returned.
Remedy SSO agent configuration example
For example, you need to apply the following configuration to the Remedy SSO agent:
- The logs should be stored in the D:\logger folder and the log file name should be rs_Try.%g.log.
- The maximum number of log files should be two, and the maximum size of each log file should be 5 MB.
- The logging level should be set to FINEST.
The following sample shows how to configure the Remedy SSO agent to meet these requirements:
rsso.log.name.format=rs_Try.%g.log rsso.log.level=FINEST rsso.log.roll=2 rsso.log.limit=5242880 rsso.log.dir=D:\logger
AREA plugin logs
AREA plugin logs are recorded to the following files:
- On the Remedy SSO server, to the %TEMP%/rsso.0.log
- On the on the Remedy AR System server, to the \ARserver\DB\arjavaplugin.log.
For more information about the AREA plugin logs, see .
Remedy SSO server logs
To set up the log level for the Remedy SSO server
By default, the log level is set to INFO on the Remedy SSO server.
To modify the log level on the Remedy SSO server, modify a value for the Server Log Level filed on the General tab of the Remedy SSO Admin Console.
The Remedy SSO logs are saved to the rsso.log file, available in the logs directory of Tomcat on the Remedy SSO server.
The launchpad logs configuration file is called rsso-log.cfg and is available in Tomcat/webapps/rsso/WEB-INF/classes. Launchpad logs are configured the same way as logging on the Remedy SSO agent. For more details about the configuration properties, see Logging configuration properties.
To set up the log level on the Remedy SSO server, update the
rsso.log.level in the rsso-log.cfg file, and then save it. You do not need to restart the Remedy SSO server, as the configuration is updated at runtime. If you are using system properties for updating the configuration, you must restart the server after updating the logging parameters.
The launchpad logs are by default recorded to the rsso-launchpad.0.log file which is available in the TomcatInstallFolder/logs directory.
Remedy SSO installation logs
The log files are created in the temp folder at the time of installation, and are appended with the next installation.
Remedy SSO copies the log files in the temp folder and zips the following log files:
The zipped file is called log_timestamp and saved to the RSSOInstallFolder/logs folder, so you can view the previous installation logs to troubleshoot installation issues.