This documentation supports the 20.02 version of Remedy Deployment.
To view an earlier version, select the version from the Product version menu.

Preparing your web server

A web server is responsible for accepting HTTP requests from clients (web browsers) and serving them HTTP responses along with optional data content, such as web pages (HTML documents) and linked objects such as images.

JavaServer Pages (JSP) and servlets are Java technologies that allow software developers to dynamically generate HTML, XML, or other types of documents in response to a Web client request. The technology allows Java code and certain pre-defined actions to be embedded into static content.

The mid tier uses third-party web servers and JSP/servlet engines. The following table outlines the tasks necessary to prepare your web server for use with the BMC Remedy Mid Tier (depending on the JSP engine you will use).

Steps to prepare your web server

Web server

JSP engine

Steps to follow

Apache Tomcat


See the following procedure.

IIS (Windows only)


No pre-requisite steps are necessary.



No pre-requisite steps are necessary.



For an Oracle WebLogic, or IBM WebSphere web server, use a .war file.

As you set up the mid tier to work with third-party web servers, remember these tips:

  • For Windows, you must install the Apache Tomcat as a service. Download the latest version of Tomcat Service Installer from the Apache Tomcat website:
    For UNIX, download and install the TAR file from the Apache Tomcat website.
  • The mid tier requires HTTP version 1.1.
  • If you use Tomcat 5.5.28 or later and you have a forward slash (/) in your form or view name, you must configure Tomcat to allow forward slashes in the URL.
  • Tuning web servers and JSP/servlet engines is beyond the scope of BMC Support. Contact the vendor for help with tuning these components.
  • Make sure that the Tomcat service name is in the format "TomcatX" (where X is the Tomcat version). If the Tomcat is given a different service name other than TomcatX, the installer fails to identify the service name and results in failure.

To prepare an Apache Tomcat server before installing the mid tier

See the following steps for preparing the Tomcat server on a Windows or UNIX environment:

    1. Navigate to <ApacheInstallDirectory>/bin and open the TomcatXw.exe file. 
      (X denotes the Tomcat version number)
    2. On the Java tab, set the Initial memory pool setting and the Maximum memory pool setting to 3072 MB.
    3. Click Apply and OK.
    4. Navigate to Services, and stop the Apache Tomcat service.
    5. Right-click the Apache Tomcat service and click Properties.
    6. On the General tab, select the startup type as Automatic.
    7. On the Log On tab, select Log On as Local System Account, and select the check box for Allow service to interact with desktop.
    8. Click Apply and OK, and start the Apache Tomcat service.
    1. Navigate to <ApacheInstallDirectory>/bin.

    2. Create a file named "" as follows:

      CATALINA_OPTS="-Xms{{ midtier_tomcat_min_heap_size }}m -Xmx{{ midtier_tomcat_max_heap_size }}m -XX:MaxMetaspaceSize=3072m"
    3. Run the file.

    4. Restart the Tomcat.

    Related topics

    System requirements

    Downloading the installation files

    Configuring your web server and installing BMC Remedy Mid Tier with a .war file

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


    1. Mohammad Rehman

      Why BMC does not include the Unix platforms related documentation? or BMC only care about the windows platform customers?

      Feb 28, 2020 11:25
      1. Himanshu Raul

        Hi Mohammad,

        Thank you for your feedback on the documentation. We have updated the topic. For more information on UNIX related documentation, see Preparing a UNIX environment.



        Mar 02, 2020 02:12
    2. Pierre Landry

      Hello, does it mean that there is no pre-requisite for tomcat on Linux ? How to change initial memory pool on Linux ? Thank you.

      Apr 03, 2020 08:38
      1. Himanshu Raul

        Hi Pierre-marie,

        Thank you for your feedback on the documentation. We have updated the topic.



        Apr 09, 2020 11:04