This documentation applies to the 8.0 version of Remedy Action Request System, which is in "End of Version Support." You will not be able to leave comments.

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

Configuring the Log Settings page

Use the Log Settings page to update logging configuration settings. A bold label with an asterisk indicates a required field.

BMC Remedy Mid Tier Configuration Tool – Log Settings page
(Click the image to expand it.)

Log Settings parameters

The following table lists the Log Settings parameters.

Setting Description
Log Categories

The type of information to be stored in the log file:

  • Reporting – Messages related to reporting.
  • Cache – Messages related to definitions, such as forms and active links in the cache.
  • Session Management – Messages related to user session construction and expiration, such as login, logout, or timeout.
  • Configuration – Messages related to the config.properties file, such as when it is loaded and changed.
  • Flashboards – Messages related to Flashboards.
  • Web Services – Messages related to web services.
  • Field – Messages related to fields.
  • Workflow – Messages related to compilation of workflow (primarily active link actions), such as invalid active links.
  • Performance – Messages related to performance, including duration of operations.
  • Qualifications and Expressions – Messages related to parsing and compilation of expressions, for example, in active links.
  • Servlet – Messages related to servlet handling of http requests, primarily for reporting results of back-channel requests.
  • Internal – Internal logging messages.
  • ARServer (API/Filter/Database) – Messages related to APIs, filters, and databases. Selecting the ARServer (API/Filter/Database) option, overrides the API logging option and all API logging is redirected to the mid tier log file.
  • Data Visualization Module – Messages related to the data visualization module.

Categories selected by default are Reporting, Cache, Session Management, Performance, and Servlet.

Filter Log by User Name The statements relating to the user who is logged in with only this user name are recorded. After you enter the user name and save changes, a new log file is started. For log messages displayed on the screen, the filter applies only to new entries. Earlier entries that existed before the user name was changed will still be displayed on the screen, up to the limit set in the View Logs setting. If the field is left blank, all logs related to the current session are stored, regardless of who is logged in. You can enter only enter one name in this field.
Log Directory The directory in which log files are stored, for example, ARSystemInstallDir/Logs. To change the log directory, enter the absolute (complete) path for the new directory. You cannot change the log file name.
Maximum Log File Size (kb) The maximum size (in kilobytes) a file can reach before a backup copy is automatically made. The default size is 1024 KB. The backup copy is made with the same file name (the default is armidtier.log) and an incremental number (for example, armidtierN.log ).
Maximum Number of Log Files The maximum number of backup files that the system will generate when the log file size exceeds the limit specified in the Maximum Log File Size. The default is 10 backups.
Log Level

The level of detail for logging information:

  • Fine – The highest level of detail.
  • Info – Less detail than Fine.
  • Warning – A moderate level of detail (the default setting). Warnings plus those errors included in the Severe level are logged.
  • Severe – The lowest level of detail; only server start time and error messages are logged.

You can see the pre-load start and end timestamp when you set the log level to Info or Warning. Irrespective of the logging level, mid tier logs the pre-load start and end time.

The default value is Severe.

Log Viewer

The method by which you want to view log files:

  • Console – The log entries are directed to the stderr (System.err) of your servlet engine.
  • File – Data is saved to a file in the specified log directory.

The default value is File.

Log Format

The log output is generated using the standard Java 1.5 logging API, including Simple and XML formatting:

  • Simple Text (the default) – A basic text file for faster performance. It does not include stack trace information except in the case of Severe log messages.
  • Detailed Text – A text file containing details such as Java class names and methods.
  • XML – A file in XML format.

This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Comments