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

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

Configuring a cluster

To ensure seamless failover, configure the mid tier on an Apache Tomcat cluster. (BMC does not support the clustering for web servers other than Tomcat.)

The BMC Remedy AR System installer allows you to only install or upgrade the BMC Remedy Mid Tier and does not provides an option for Tomcat clustering. To add the mid tier in a Tomcat cluster, install mid tiers on different virtual computers and configure the cluster manually with the following procedure.

  1. Stop Tomcat.

  2. Open the arsys.xml file located in the TomcatInstallationFolder\conf\Catalina\localhost folder in a text editor, and replace the <Manager> tag with the following XML:

    <Manager className="org.apache.catalina.ha.session.DeltaManager"
      notifyListenersOnReplication="true" />
  3. Open the server.xml file located in the TomcatInstallationFolder\conf folder in a text editor and make the following changes:

    • Locate the <Engine> tag and add the jvmRoute attribute.
      Use Node1 for the first node, Node2 for the second, and so on.
      <Engine name="Catalina" defaultHost="localhost" jvmRoute="Node1">

    • Copy the <Cluster> tag information from the attached file and paste it after the <Engine> tag in your server.xml file. You can download the sample server.xml file. 


      If you are using Tomcat version 8.0.38 and above, you must remove the following XML tag from the server.xml file.

      <ClusterListener className="org.apache.catalina.ha.session.JvmRouteSessionIDBinderListener"/>

      For versions of Tomcat prior to 8.0.38, you can use the server.xml file as is without making any changes.

      <Cluster className="org.apache.catalina.ha.tcp.SimpleTcpCluster" channelSendOptions="8">
      <Manager className="org.apache.catalina.ha.session.DeltaManager"
      <Channel className="">
                <Membership className="org.apache.catalina.tribes.
              <Receiver className="org.apache.catalina.tribes.transport.nio.NioReceiver"
              <Sender className="org.apache.catalina.tribes.transport.
                    <Transport className="org.apache.catalina.tribes.transport.
      <Interceptor className="
            <Interceptor className="
       <Valve className="org.apache.catalina.ha.tcp.ReplicationValve"
      statistics="false" />
      <Valve className="org.apache.catalina.ha.session.JvmRouteBinderValve"/>
       <Deployer className="org.apache.catalina.ha.deploy.FarmWarDeployer"
      <ClusterListener className="org.apache.catalina.ha.session.
      <ClusterListener className="org.apache.catalina.ha.session.


      The default value for the <ipAddress> variable is This IP address and port number defines a unique cluster. However, for each member of a cluster, ensure that they have the same multicast IP address and port number.

  4. Enter the multicast IP address of the host on which you want the session replication to take place in the Address value instead of auto. For example, in the <Receiver> tag, modify address="auto" to address="172.x.x.x". For more information, see FAQ about cluster configuration.
  5. (Optional) Add two new file handlers and in the handlers section to the file.

    handlers =, \
     , \
     , \
     , \, \ 
  6. (Optional) To increase the cluster logging, change the log level to FINE for the following file handlers in the file located in the TomcatInstallationFolder/conf folder: and = INFO = ${catalina.base}/logs = cluster.
 = INFO = ${catalina.base}/logs = ha.
    org.apache.catalina.tribes.MESSAGES.level = INFO
    org.apache.catalina.tribes.MESSAGES.handlers =
    org.apache.catalina.tribes.level = INFO
    org.apache.catalina.tribes.handlers =
    org.apache.catalina.ha.level = INFO
    org.apache.catalina.ha.handlers =
  7. Restart Tomcat.
  8. Verify whether the node is added to the cluster:
    1. Open the file located at /opt/apache/tomcat7.0/logs for Linux and <C:\Program Files\Apache Software Foundation\Tomcat7.0\logs> for Windows.
    2. Search for memberAdded entry. If you have added four mid tiers to the cluster, you should see three memberAdded entries and their IP addresses in the file for the other three members. Ensure that the IP address does not represent a localhost.


To add an extra mid tier to the cluster, perform the same configurations on the extra (n+1) mid tier.

To access the mid tier configuration URL, use the HTTP URL in the following format:


Best practices for configuring a cluster

To improve application scalability, we recommend that you increase the File Descriptor limit in mid tiers running in a cluster. If you have a cluster of 2 mid tiers with 12 tenants, which is serving 3600 users, set the File Descriptor limit to 35000.


Average load per tenant is considered as 300 users.

To set the File Descriptor limit, perform the following steps:

  • Edit the /etc/security/limits.conf file and add the following:

root  soft  nofile   35000

  • Edit the /etc/bashrc file and set the unlimit value as follows:
if [ "$EUID" = "0" ]; then

    ulimit -n 35000

  • Edit the /etc/sysctl.conf file and increase the File Descriptor limit for the system as follows:

fs.file-max = 210000


Ensure that you set the system-wide limit of File Descriptors to approximately 6 times of the per process limit set in the limits.conf file.

Refer to the following table for guidance on deciding the File Descriptor limit:

S NoComponentVariableDescription
1Tomcat connections

maxThreads setting in Tomcat HTTP Connector

maxThreads defines the maximum connections used by Tomcat when
BIO Connector is used.


Tomcat NIO Receivers

Default setting is 6

NIO Receivers for Session Replications.


Tomcat and Mid Tier Class Loaders

Estimate is 1200Class loader for JAR files loaded by Tomcat. This includes JARs in Mid Tier distribution, configured Third-party JARs, and DVF plug-ins.

Mid Tier properties files

1 + 1 * Number of Tenants

1 for global configuration and 1 per tenant


Mid Tier Cache files

27 x 2 = 5427 categories x 2 files per category. Data files are always open.
Index files are read into Memory at startup and closed and later written to
during Mid Tier shutdown.

Mid Tier Cache lock file


Single file for Cache lock status

7Java API RPC connections to AR Serverarsystem.pooling_max_connections_per_server from Mid Tier Configuration * Number of TenantsConfigured by arsystem.pooling_max_connections_per_server setting
in Mid Tier Configuration
8Java API JMS Connections for CCS1 + 1 * Number of Tenants1 for ECCS and 1 per Tenant

Attachments and Reports

Estimate is 20% * Maximum Concurrent Users on the Mid-Tier Node

Attachment files and report files created by MT on Disk


SSO Agent - Files


A single Configuration file is used by the SSO Agent which is queried from the SSO Server

11SSO Agent – Connections to SSO Server

maxThreads setting in Tomcat HTTP Connector

SSO Agent opens a URLConnection to SSO Server when it logs in a
User or validates SSO Token with SSO Server
12Safety Factor25% * Sum of (#1 to #11) 
 Total Sum of #1 to #12 rounded up to nearest 5000 on 6th higher side

Related topics

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


  1. Stefan Hall

    Why should we configure ... twice - in arsys.xml (point 2) AND server.xml (point 3)?

    Jul 19, 2019 02:39
    1. Stefan Hall

      the missing/blocked part :)

      Manager className="org.apache.catalina.ha.session.DeltaManager" expireSessionsOnShutdown="false" notifyListenersOnReplication="true"

      Jul 19, 2019 02:39
      1. Himanshu Raul

        Hi Stefan,

        Thank you for your feedback on the documentation. The response to your query is:

        Changes made to the arsys.xml are applicable only to the Mid Tier web application while the changes made to server.xml apply to the whole tomcat i.e. all applications deployed in that Tomcat instance. Changes in server.xml are required to allow cluster configuration at the container level i.e. tomcat webserver level. However, we do not want the manager changes for all web apps, which may break if session replication starts happening. So changes in arsys.xml are also needed to only allow session replication for midtier.

        Hope this helps.



        Nov 22, 2019 05:19