This documentation applies to the 8.1 version of Remedy Action Request System, which is in "End of Version Support."

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

Running Tomcat with IIS

The 64-bit version of Microsoft Internet Information Services (IIS) does not load the Tomcat ISAPI filter by default because the Tomcat filter is designed for 32-bit platforms. Complete the following procedure to run IIS with Tomcat on this platform.

To run Tomcat with IIS on a 64-bit version Windows 2003, Windows 2008 or Windows 2012 server


 If BMC Remedy Mid-tier and Tomcat are already installed, uninstall both. You must download the latest installer. 

  1. Verify if roles are installed
    1. Go to Control Panel> Administrive Tools > Sever Manager > Roles
    2. In the Role Service section, under Web server, verify if the following roles are installed: 
      • ISAPI Filters
      • ISAPI Extensions
      • CGI 
      • IIS6 Management Compatibility 
    1. If the roles are not installed, click Add Roles Services link and add the roles. 
  2. Run the BMC Remedy Mid-tier installer with IIS as the web server and Tomcat as the JSP engine.
  3. Install the 64 bit isapi redirector.dll
    1. Download the 64 bit isapi redirector.dll from the the following location:
    2. Install the 64 bit isapi redirector.dll at the following location:

      <drive>:\apps\Apache Software Foundation\Jakarta Isapi Redirector

  4.  Perform the following post-installation tasks:
    1. Verify if the isapi_redirect.dll is installed at the following location:
      <drive>:\apps\Apache Software Foundation\Jakarta Isapi Redirector
    2. Verify if the <drive>:\apps\Apache Software Foundation\Jakarta Isapi Redirector\conf directory contains the following two files. See if the file type is recognized by Windows:
    3. Create a <drive>:\apps\Apache Software Foundation\Jakarta Isapi Redirector\bin\ file. Use the following snippet: 
      The snippet uses the path of d:\apps\Apache Software Foundation\Jakarta Isapi Redirector as the installation directory. 

      # Configuration file for the Jakarta ISAPI Redirector
      # The path to the ISAPI Redirector Extension, relative to the website
      # This must be in a virtual directory with execute privileges
      # Full path to the log file for the ISAPI Redirector
      log_file=d:\apps\Apache Software Foundation\Jakarta Isapi Redirector\logs\isapi_redirect.log
      # Log level (debug, info, warn, error or trace)
      # Full path to the file
      worker_file=d:\apps\Apache Software Foundation\Jakarta Isapi Redirector\conf\
      # Full path to the file
      worker_mount_file=d:\apps\Apache Software Foundation\Jakarta Isapi Redirector\conf\
    4. Create a <drive>:\apps\Apache Software Foundation\Jakarta Isapi Redirector\logs directory/
    5. In the IIS Manager, select the server node and the click the ISAPI and CGI Restriction icon.  Verify that jakarta entry with restriction is set to Allowed
      If you don't find the entry, add an entry for jakarta, with a path to the isapi_redirect.dll and select Allow extension path to execute.  
    6. Confirm that a jakarta virtual directory exists under the website pointing to the directory containing the file isapi_redirect.dll.
    7. In the Handler Mappings section of this virtual directory,  enable the ISAPI-dll handler and give it read, script and execute permissions.  Click the Edit Permission link to give permissions. 
    8. If ISAPI-dll is not present, you must add it.
      • Click Add Module Mapping and provide the following details: 
        • Request path:  *.dll 
        • Module:  IsapiModule 
        • Executable:  point to the isapi-redirect.dll 
        • Name:  ISAPI-dll Feature 
        • Permissions:  read, script, execute
    9. Add a filter called  jakarta that points to the isapi_redirect.dll found in the <drive>:\apps\Apache Software Foundation\Jakarta Isapi Redirector\bin directory.
    10. Grant Full Control to everyone on the <drive>:\apps\Apache Software Foundation\Jakarta Isapi Redirector directory. 
    11. Restart the IIS Admin Service.
  5. Verify if 32-bit applications property is disabled.
    1. In the IIS Manager, expand the server node.
    2. Click on the Application Pool properties (for the AppPool used by the specific website).
    3. Verify that the Enable 32-bit applications property is set to False.
  6. Restart the Application Pool.

This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.