Working with logs

To debug an issue in Remedy Single Sign-On, you can investigate log files. Logs give information about various events on the Remedy SSO server, Remedy SSO agent, Remedy SSO AREA plugin, Java SDK, and installation.

Remedy SSO server logs

By default, the Remedy SSO server log level is set to INFO. To modify the log level on the Remedy SSO server, use one of the options:

• Configure the log level in the Remedy SSO Admin Console; see Configuring settings for the Remedy SSO server.

• Configure the logback.xml file in $TOMCAT$/webapps/rsso/WEB-INF/classes
  For more information about the logback.xml file, see Logback configuration .

The Remedy SSO server log example is as follows:

$TOMCAT_HOME$\logs\rsso.0.log—internal Remedy SSO logger

The Remedy SSO server logs are recorded to the rsso.log file available in the logs directory of Tomcat on the Remedy SSO server. BMC recommends that you preserve the default log parameters for the Remedy SSO server. If you need to reconfigure these logs, see Simple Logging Facade for Java (SLF4J) .

Remedy SSO agent logs

To set the log level for the Remedy SSO agent

By default, the Remedy SSO agent log level is set to INFO. To modify the log level on the Remedy SSO agent, use one of the options:

• Update the rsso-log.cfg file available in the class path of an integrated application. 
  For information about the location of the file, see the documentation of the integrated application.
• Specify the configuration path to the rsso-log.cfg file through the following system property:

-Drsso.log.cfg.file=<path_to_rsso-log.cfg>

Remedy SSO agent log examples are as follows:

• $TOMCAT_HOME$\logs\rsso.0.log—internal Remedy SSO logger
• $TOMCAT_HOME$\logs\rsso-agent.0.log—internal Remedy SSO logger used in the Remedy SSO agent

To configure logging for the Remedy SSO agent

To configure the Remedy SSO agent logging, modify the following parameters in the rsso-log.cfg file: 

Remedy SSO agent logs configuration example

For example, you need to apply the following configuration to the Remedy SSO agent:

• The logs should be stored in the logger folder and the log file name should be rs_Try.%g.log. 
• The maximum number of log files should be 2, 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=logger

Remedy SSO AREA plugin logs

Remedy SSO AREA plugin log files are as follows:

• %TEMP%/rsso.0.log—logs recorded on the Remedy SSO server
• \ARserver\DB\arjavaplugin.log—logs recorded on the Remedy AR System server

For more information about the Remedy SSO AREA plugin logs, see Troubleshooting issues with plug-in servers .

Remedy SSO installation logs 

The log files are created in the temp folder at the time of installation, and are preserved during the next installation. Remedy SSO copies the log files in the temp folder and zips the following log files:

• remedysso_configuration_log
• remedysso_install_log

The zipped file is called log_timestamp and saved to the RSSOInstallFolder/logs folder, which enables viewing the previous installation logs to troubleshoot installation issues.