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.

BMC Remedy Mid Tier logging

You can log BMC Remedy Mid Tier activity to help you debug issues with the BMC Remedy Mid Tier. Use a combination of logging provided by the mid tier and third-party products. The BMC Remedy Mid Tier log statement includes method calls, code execution, and informative messages for BMC Remedy Mid Tier components. BMC Remedy Mid Tier log statements are written into armidtier.log file in the BMC Remedy Mid Tier installation directory. JSP engine log and web server log statements are logged separately in their respective install directories.

To set logging properties for the BMC Remedy Mid Tier, open the BMC Remedy BMC Remedy Mid Tier Configuration Tool and click Log Settings in the navigation bar. See Configuring the Log Settings page, or the BMC Remedy Mid Tier Configuration Tool online help.

Remember these tips when you configure the mid tier logging.

Logging property settings in BMC Remedy Mid Tier (top portion of Log Setting window)
(Click the image to expand it.)

Following are some examples from a BMC Remedy Mid Tier log:

  • Log Statement with Session ID
    
    <WtXUmAWNLW8QgAaLX9KU> <FormAction> <2001-02-28 16:35:36,639> <Reached isDataAvail() method >
  • Log Statement with no Session ID
    
    <-> <Reporting> <2001-02-28 16:35:36,655> <In doStartTag, atts[0] = 16 >Log Statement with Session ID and Exception Stack Trace
    < WtXUmAWNLADFERSDFFSF> <TagHandler> <2001-02-28 16:35:36,671> <IOException in tagHandler()>
    java.lang.IOException: IOException at com.remedy.arsys.framework.FormTag.tagHandler(FormTag.java, Compiled Code)
    at java.lang.Exception.<init>(Exception.java, Compiled Code)
    at com.remedy.arsys.framework.FormTag.AddInitTags(FormTag.java, Compiled Code)
    at com.remedy.arsys.framework.FormTag.doStartTag(FormTag.java:122)
    at pagecompile._jsp._Bugs_xjsp._jspService(_Bugs_xjsp.java, Compiled Code)
    at com.unify.ewave.servletexec.JSP10HttpJspPage.service JSP10HttpJspPage.java)
    at com.unify.ewave.servletexec.JSP10Servlet.service (JSP10Servlet.java)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:865)
    at com.unify.ewave.servletexec.ServletExec.CallServletService ServletExec.java)
    at com.unify.ewave.servletexec.ServerHostInfo.processApplRequest (ServerHostInfo.java, Compiled Code)
    at com.unify.ewave.servletexec.ServletExec.ProcessRequest (ServletExec.java, Compiled Code

Use the View Log File button on the Log Settings page to view logs.

Viewing logs from the BMC Remedy Mid Tier
(Click the image to expand it.)

Third-party products

You can use some third-party products in combination with mid tier logging to monitor and tune your application. The mid tier runs in a Java Virtual Machine (JVM), which is started by the Java binary. Oracle, IBM, BEA, and HP provide a Java Software Development Kit (SDK) as well as tools to monitor the Java process. Since version 1.5, the Java Development Kit (JDK) comes with the built-in process monitor called JConsole. HP and AIX also provide free tools (such as HPJmeter) to monitor the JVM. Other operating system tools can also be used (for example, pstack and truss on UNIX and DebugDiag and ADPlus on Windows).

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

Comments