This documentation supports the 9.1 version of Remedy IT Service Management Suite.

To view the latest version, select the version from the Product version menu.

Configuring BMC Remedy Smart Reporting log settings

Configure the log4j.properties file to get the optimum logs for better troubleshooting. Optionally, you can configure the file to modify the duration of the log files, and save memory.

To configure the BMC Remedy Smart Reporting log file

  1. Navigate to the <reportingInstallDir>\SmartReporting\appserver\webapps\ROOT\WEB-INF\ folder.

    You can modify the same settings for Onboarding logs. The onboarding issues are logged in the smartreporting.log file located at:

    <reportingInstallDir>\SmartReporting\appserver\logs

  2. Modify the appropriate properties in the log4j.properties file to change the log file settings.
    1. To change the log level modify the log4j.rootCategory value. The log level can be set using the following values:
      • ERROR — only logs error messages. This is the default value.
      • WARNING — only logs errors and warnings
      • INFO — information, warnings and errors
      • DEBUG — all usage information
    2. To modify the size of the log file, modify the log4j.appender.sourcelog.MaxFileSize value. By default, the value is set to 1 Mb / 1024 Kb. Increase of decrease the value as required.
    3. To define the number of log files to create, modify the log4j.appender.sourcelog.MaxBackupIndex value. Increase or decrease the value as required. By default, BMC Remedy Smart Reporting creates 9 log files before overwriting the existing log files that were created. Once the maximum  number of files is reached, BMC Remedy Smart Reporting will overwrite the existing log files that were created.
  3. Restart the Tomcat server.

Related Topics

Troubleshooting issues for BMC Remedy Smart Reporting

Was this page helpful? Yes No Submitting... Thank you

Comments