This documentation supports the 9.0 version of Remedy Action Request System.

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

Tips to configure mid tier logging

  • Configure the amount and type of logging in the BMC Remedy Mid Tier Configuration Tool. For example:
    •  If you require detailed logging information, select Simple Text from the Log Format list on the Log Settings page to improve logging performance.
    • To log information by user, enter the user name in the Filter Log by User Name field on the Log Settings page.
  • By creating a record in the AR System User Preference form, you can log server API, filter, and database information for a specific user. (This is different from turning on logging in the AR System Administration Console which turns on logging for all users.)
  • To monitor how long it takes a request to go from the browser to the mid tier, enable Performance logging in the AR System User Preference form. You can also enable Workflow, API, Database, or Filter logging to display information about HTTP requests, which include the amount of time it takes to process a request. This information is useful for application developers to monitor their application design and look for improvements. Using this information with HTTP request monitoring programs gives you the round-trip time to process a request. Examples of HTTP request monitoring programs are Fiddler (on Internet Explorer) and Live HTTP Headers or Firebug (on FireFox).
  • Use a debug build of the mid tier to see an enhanced presentation of mid-tier log.
  • The AR System server provides a wealth of logging information that you can set through the AR System Administration Console form.
  • For web server and JSP/Servlet engine logs, consult with the product's vendor.
  • To capture a log with a sequence of events, use a combination of server and client logging.
Was this page helpful? Yes No Submitting... Thank you