This documentation applies to the 8.1 version of Remedy Action Request System, which is in "End of Version Support."

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

Configuring mid tier memory

This topic describes the following memory-related issues for the BMC Remedy Mid Tier.

Allocating enough memory for your application and the mid tier

If there is not enough memory allocated to your application server to run your BMC Remedy AR System application on the BMC Remedy Mid Tier, the application server will produce out-of-memory exceptions. (You can see this in the application server log file.)

To avoid out-of-memory exceptions

  1. Shut down your application server.
  2. Allocate enough memory to the application server.
  3. Restart the application server.
  4. If the Enable Cache Persistence check box is selected in the BMC Remedy Mid Tier Configuration Tool, flush the cache.
    For more information, see Configuring the Cache Settings page.

Monitoring mid-tier memory use and performance in real time

To monitor mid-tier memory use and performance in real time through a web server, such as Tomcat, perform the following procedure. By default, real-time mid-tier monitoring is disabled.

To monitor mid-tier memory use and performance in real time in Tomcat

  1. Add the following parameters to the Java Virtual Machine (JVM) started by the mid-tier JavaServer Pages (JSP) or servlet engine.
    • To monitor the mid tier on the mid-tier host:
      At the At the command-line prompt, set the JAVA_OPTS environment variable as follows, and then start Tomcat:
      set JAVA_OPTS=-
      Dcom.sun.management.jmxremote
      Alternatively, add that parameter to the JAVA_OPTS entry in the TomcatInstallDir/bin/catalina.bat file, and then restart Tomcat.
    • To monitor the mid tier remotely:
      At the command-line prompt, set the JAVA_OPTS environment variable as follows, and then start Tomcat:
      set JAVA_OPTS=-
      Dcom.sun.management.jmxremote.authenticate
      =false
      -Dcom.sun.management.jmxremote.ssl=false
      -Dcom.sun.management.jmxremote
      -Dcom.sun.management.jmxremote.port=portNumber
      portNumber is the port number to connect to your JMX Remote Method Invocation (RMI) connector. Specify an unused port number.
      Alternatively, add those parameters to the JAVA_OPTS entry in the TomcatInstallDir/bin/catalina.bat file, and then restart Tomcat.
    • If remote monitoring JMX client is unable to connect to the mid-tier server:
      Add the following parameter to the JAVA_OPTS entry in the TomcatInstallDir/bin/catalina.bat file, and then restart Tomcat.
      -Djava.rmi.server.hostname=<servername.sitename.com>
  2. To enable real-time monitoring, select the Enable Mid Tier Performance MBean check box on the General Settings page In the BMC Remedy Mid Tier Configuration Tool. See Configuring the General Settings page.
  3. Restart the mid tier.

Note

You can also monitor the performance by analyzing the entries in the armidtier.log file. For more information, see BMC Remedy Mid Tier logging.

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