This configuration is specific to small, medium and large models defined as follows:

This checklist is for the configurations in the Midtier, RSSO, AR Server, Smart Reporting and database server.
There’s also a section for the web-infrastructure (web proxy, tomcat, JVM parameters), the Midtier, and ITSM application stack.

Web Proxy or Load-Balancer for The Remedy SSO Service
There are 2 network segments: From the browser proxy (or from the actual client if there’s no proxy) to the F5; from the F5 to the SSO service.
Since the interaction between the browser and the SSO service is brief, there is no need to activate HTTP keep-alive for either of the network segments.
For the F5, the recommended load-balancing scheme is round-robin no session binding.
Notes:
1- The client HTTP protocol version for HTTP monitoring must be set to HTTP 1.1. The return HTTP code for alive is HTTP 200.
​2- For performance testing, the granularity of ping interval was 5 seconds with 3 consecutive non-HTTP 200 indicating the node is down.
For deployment, you may configure this to a lower threshold as required.

JVM Options in tomcat/bin/setenv.sh for Remedy SSO

Web Proxy or Load-Balancer for Midtier
There are 2 network segments:
              - From the client browser proxy to the F5
              - From the F5 to the Midtier Tomcat cluster
1. For both network segments, HTTP keep-alive must be turned on.
If the keep-alive feature supports the optional values as in tomcat, the recommended values are given by the following table:

2. For the F5, the recommended load-balancing scheme is round-robin with HTTP session binding cookie insert.
3. For detection whether a node is alive, use HTTP monitoring and issue a GET on the following URL:  /arsys/shared/images/bkgd_image.gif
Notes:
a) The client HTTP protocol version for HTTP monitoring must be set to HTTP 1.1. The return HTTP code for alive is HTTP 200
b) For performance testing, the granularity of ping interval was 15 seconds with 3 consecutive non-HTTP 200 indicating the node is down.
For deployment, you may configure this to a lower threshold as required

JVM Options in tomcat/bin/startup.sh For The Midtier Tomcat
Important: The following settings assume that each tomcat instance in the cluster hosts only the Midtier and the RSSO agent.

BMC AR Mid-Tier Server configuration settings
Note:  For Windows, use the “Configure Tomcat’ tool and select the ‘Java’ tab to set these options:

JVM Options in tomcat/bin/startup.sh For The Midtier+RSSO Tomcat
Important: The following settings assume that each tomcat instance in the cluster hosts both the Midtier (with the RSSO agent) and the RSSO web app.
All of the settings in the previous section (where tomcat hosts only the Midtier and the RSSO agent) applies.
There’s only 1 change given by the following:

BMC Remedy AR System Server (user facing) configuration settings

* Denotes new default value in 9.1 SP2. If this value is unset, the new default is used.

Plugin Servers
Note: Plugin servers can run with default GC settings unless they act primarily as a server and are configured for >= 4GB heap. Only the FTS plugin server requires the additional GC settings as specified below.  

<ar install dir>/pluginsvr/pluginsvr_config.xml
Add or alter this file to:
              <numCoreThreads>30</numCoreThreads>
<atrium core install dir>/cmdb/plugins/shared/pluginsvr_config.xml
Add or alter this file to
              <numCoreThreads>10</numCoreThreads>
AR Dir/pluginsvr/fts/secondary/pluginsvr_config.xml
Plugin Server Settings:

GC settings
BMC recommends using these GC parameters with Plugin Server for FTS when using Java 1.8
.................................................
-XX:+DisableExplicitGC
-XX:+UseParNewGC
-XX:+UseConcMarkSweepGC
-XX:NewRatio=2
-XX:+UseCompressedOops
.................................................
For Java 11 and higher, use the following parameters
.................................................
-XX:+DisableExplicitGC
-XX:MaxMetaspaceSize=512m
-XX:MetaspaceSize=384m
-XX:+UseCompressedOops
-XX:+UseG1GC
-XX:+UseStringDeduplication
-XX:G1NewSizePercent=40
-XX:+UnlockExperimentalVMOptions
-XX:MaxGCPauseMillis=200
.................................................
More information about configuring Java Plugin server options.  

Database Server
Please consult your DBA when making changes to your Database environment.
All recommendations are based on testing and customer feedback.
But the specific settings may vary depending on each specific environment properties.
Whenever possible, test in lower environments before applying to production.

NOTE: If you choose to work with PostgreSQL Databases, please work with your DBA to schedule and configure the auto-vacuum feature based on your business needs and usage patterns.  Additionally, BMC recommends after doing any upgrades to run a “VACUUM FULL ANALYZE” command from pgAdmin for every AR-related database.  Keeping pgSQL vacuumed is required to reclaim unused disk space as well as keeping your statistics up to date.  To learn more about the vacuum feature, please see Routine Vacuuming in the PostgreSQL documentation.

Tomcat/conf/server.xml for smart reporting

General Virtual Agent Administration Console Configuration Checklist