Installing Remedy Mid Tier on an external Tomcat


In a Proof of Concept (PoC) environment, you can use bundled Apache Tomcat to deploy Mid Tier. However, in a production environment, it is recommended that you use an external Tomcat to deploy Mid Tier. Use of external Tomcat is recommended to overcome security vulnerabilities, if any, when using a bundled Tomcat

You can also install Tomcat using a .war file. For more information, see Deploying-Remedy-Mid-Tier-on-Tomcat-by-using-a-WAR-file.

Before you begin

  • Install Apache Tomcat on your computer. For download instructions, see https://tomcat.apache.org/download-80.cgi in the Apache Tomcat documentation. For the supported Tomcat version, see BMC solution and product availability and compatibility utility (SPAC).

  • If the arsys.xml file does not exist, create it in the Tomcat<ver>\conf\Catalina\localhost location and point to your Mid Tier location. Refer to the following sample code to create the file:

    <?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="<ARSystemInstallationDirectory/ARSystem/midtier>" 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 install BMC Remedy Mid Tier on an external Tomcat

  1. Download the BMC Remedy AR System installer on a computer other than where you installed the AR System server.
  2. Unzip the suite installer (for example, ARSuiteKitWindows.zip or ARSuiteKitLinux.zip).
  3. Open the Disk 1 folder.
  4. Start the installer:
    • For Windows, run setup.exe.
    • For UNIX, run setup.bin.
  5. In the lower-right corner of the Welcome panel, click Next.
  6. Review the license agreement, click I agree to the terms of license agreement, and then click Next.
  7. On the Products selection panel, perform the following actions:
    1. Select Install.
    2. Select AR System mid tier and clear the other options.
      The installer validates the system resources of your computer and displays a list of available features.
    3. Navigate to the directory in which you want to install BMC Remedy Mid Tier.
      The default locations are C:\Program Files\BMC Software\ARSystem (Windows) and /opt/bmc/ARSystem (UNIX and Linux).
    4. To install Mid Tier on external Tomcat, select Use external tomcat server check box.
    5. Navigate to the Tomcat home directory.
    6. Click Next.
  8. Enter the values from the installation spreadsheet for the mid tier.
    After you have entered the required information, the installer validates your inputs. The Installation Preview panel then appears, listing the product and features that will be installed.
  9. Click Next.
    After post-installation cleanup, a summary of the installation appears.
  10. Click View Log to review any error messages or warnings in the product installer log.
    See whether errors are due to network, host, or other environment-related issues. You can view a log file of the installation: 
    For Windows, C:\Users\Administrator\AppData\Local\Temp\arsystem_install_log.txt
    For UNIX, /tmp/arsystem_install_log.txt
  11. Click Done to exit the AR System installer.
  12. Open the BMC Remedy Mid Tier Configuration Tool ( http://<midTierServer>:<PortNumber>/arsys/shared/config/config.jsp ). 
  13. Click General Settings.
  14. Select the AR System server as the authentication server, and then click Save Changes.

Note

To access the Remedy Mid Tier, go to http://<midTierServer>:<PortNumber>/arsys/


To hide Apache Tomcat version on error pages

In a Proof of Concept (PoC) environment, when you have a bundled Tomcat, Apache Tomcat version might be displayed on error pages. Perform the following steps to hide Apache Tomcat version on error pages.

  1. Create the ServerInfo.properties file in the following directory:
    $CATALINA_HOME/lib/org/apache/catalina/util/ServerInfo.properties

  2. Define the following property in the ServerInfo.properties file:
    server.info=Apache Tomcat Version X

  3. Restart Tomcat.

Related topics

Platform-installation-and-upgrade-known-and-corrected-issues

Working-with-logs

2021-01-05_00-08-25_Troubleshooting data and workflow import issues

Troubleshooting-driver-issues

2021-01-05_00-11-41_Troubleshooting Remedy AR System issues

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*