Deploying Remedy Mid Tier on Tomcat by using a WAR file

You can deploy Remedy Mid Tier by using a WAR file. This is an alternative method to deploy Remedy Mid Tier. The benefit of using the WAR file is that you can deploy the latest version of Mid Tier without uninstalling the existing Remedy applications. The WAR based deployment is fast and can be used in hot deployment scenarios where you can install Mid Tier without interrupting the functioning of other Remedy applications.

Best practice

If Mid Tier and Remedy SSO (RSSO) are deployed on the same Tomcat, performing the following procedure overwrites the config.properties and RSSO agent files. This breaks the RSSO functionality. Therefore, before you manually deploy the WAR file on Tomcat, we recommend that you create a backup of the config.properties and RSSO agent files and preserve the settings that are essential for the integration to function correctly. For more information, see Manually integrating Remedy SSO with BMC Remedy applications .

Before you begin

1. If you are deploying the Mid Tier WAR file for the first time on Tomcat, perform the following steps:
   (Linux)
   Navigate to <tomcat_HOME>/bin/ and add the following parameters to the startup.sh file:
   

   JAVA_OPTS="$JAVA_OPTS -Xms1024m"; 
export JAVA_OPTS

   JAVA_OPTS="$JAVA_OPTS -Xmx2048m"; 
export JAVA_OPTS
Note: Java heap size configuration values are based on the assumption that only the Mid Tier is running in the Tomcat.

   JAVA_OPTS="$JAVA_OPTS -Djava.awt.headless=true"; 
export JAVA_OPTS

   JAVA_OPTS="$JAVA_OPTS -XX:+UseCompressedOops"; 
export JAVA_OPTS

   JAVA_OPTS="$JAVA_OPTS -XX:+UseConcMarkSweepGC"; 
export JAVA_OPTS (Not supported on Java 11)

   JAVA_OPTS="$JAVA_OPTS -XX:+UseParNewGC"; 
export JAVA_OPTS (Not supported on Java 11)


   JAVA_OPTS="$JAVA_OPTS -XX:MaxMetaspaceSize=512m"; 
export JAVA_OPTS (Add this parameter 
   if you are using Java 8)

   
   (Windows)
   
   1. Navigate to <Apache Tomcat installation folder>\bin\ and open the tomcat#w.exe file. (# represents the major version number).
   2. In the Tomcat Config tool, click the Java tab and perform the following:
      1. Set the Initial memory pool (Initial Heap Size) and Maximum memory pool (Max Heap Size) values to 2048 MB.
         
      2. Add the following Java options:
         • -XX:+UseCompressedOops
         • -XX:+UseConcMarkSweepGC (Not supported on Java 11)

         • -XX:MaxMetaspaceSize=512m (Add this parameter if you are using Java 8)
           Be sure to enter each entry on a separate line and make sure there are no preceding spaces.

   Note

   Some JVM parameters are not supported on Java 11. For example:

   • -XX:+UseParNewGC
   • -XX:+PrintGCDetails
   • -XX:+PrintGCDateStamps
   • -XX:+PrintGCCause
2. Ensure that the arsys.xml file is available at the following location: <Apache Tomcat installation folder>/conf/Catalina/<ServerName>/arsys.xml

3. If arsys.xml file is not available, create it. Refer to the following sample code to create the file:
   

   Sample Tomcat/conf/Catalina/<ServerName>/arsys.xml

   <?xml version="1.0" encoding="ISO-8859-1"?>
           <!--    
             Context configuration file for the Tomcat Manager Web App    
              $Id: manager.xml 303123 2004-08-26 17:03:35Z remm $
           -->
           <!-- http://tomcat.apache.org/tomcat-7.0-doc/config/context.html -->
           <Context deployOnStartup="true" docBase="<MidTier WAR File Path>" path="/arsys" reloadable="false" sessionCookiePathUsesTrailingSlash="false">
             <!--
              reloadable will disable session persistence across shutdown/startup and sessionCookiePathUsesTrailingSlash is set to prevent
              creating of a duplicate JSESSIONID in Tomcat 7 because of enabling HTTPOnly cookie for JSessionID
             -->
             <Manager pathname=""/>
           </Context>

To deploy Remedy Mid Tier on a Tomcat server by using the WAR file

1. Download the Remedy Mid Tier WAR file. For installer file locations, see Downloading the installation files.

2. Copy the downloaded WAR file to the <Apache Tomcat installation folder>\webapps directory, and rename it to arsys.war.
   

3. Stop Tomcat.
4. Go to <Apache Tomcat installation folder>\conf\Catalina\localhost folder and open the arsys.xml file.
   
5. In the arsys.xml file, update the docBase parameter with docBase="arsys.war". 
   
   
6. Start Tomcat. Mid Tier is deployed automatically. 

7. Go to the BMC Remedy Mid Tier Configuration Tool ( http://<midTierServer>:<PortNumber>/arsys/shared/config/config.jsp ) to verify that mid tier is deployed successfully. 
   For more information on the BMC Remedy Mid Tier Configuration Tool, see  Accessing the Mid Tier Configuration Tool

Post deployment tasks

You must enable the binary payload deployment for Mid Tier to apply hotfixes through a binary payload deployment package. For instructions, see Enabling binary payload deployment for a .war file-based mid tier deployments.