Running Tomcat with IIS

The 64-bit version of Microsoft Internet Information Services (IIS) does not load the Apache 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 2008, or Windows 2012 server

Note

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

  1. Verify that roles are installed:

    1. Go to Control Panel > Administrative Tools > Sever Manager > Roles. 
    2. In the Role Service section, under Web server, verify that 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.  Perform the following post-installation tasks:
    1. Verify that the isapi_redirect.dll is installed at the following location:
      <drive>:\apps\Apache Software Foundation\Jakarta Isapi Redirector
    2. Verify that the <drive>:\apps\Apache Software Foundation\Jakarta Isapi Redirector\conf directory contains the following two files, and see if the file type is recognized by Windows:
      • workers.properties.minimal
      • uriworkermap.properties

    3. Verify that isapi_redirect.properties file exists at the location <drive>:\apps\Apache Software Foundation\Jakarta Isapi Redirector\bin\ and has the following sample contents.

      (The snippet uses 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
      extension_uri=/jakarta/isapi_redirect.dll
      # 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)
      log_level=debug
      # Full path to the workers.properties file
      worker_file=d:\apps\Apache Software Foundation\Jakarta Isapi Redirector\conf\workers.properties.minimal
      # Full path to the uriworkermap.properties file
      worker_mount_file=d:\apps\Apache Software Foundation\Jakarta Isapi Redirector\conf\uriworkermap.properties
    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.
    6. Verify that jakarta entry with restriction is set to Allowed. 
      If you do not find the entry, add an entry for jakarta, with a path to the isapi_redirect.dll, and select Allow extension path to execute.  
    7. Confirm that a jakarta virtual directory exists under the website pointing to the directory that contains the isapi_redirect.dll file.
    8. In the Handler Mappings section of this virtual directory, enable the ISAPI-dll handler and give it read, script, and execute permissions; then click the Edit Permission link to give permissions. 
    9. 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
    10. 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.
    11. Grant Full Control to everyone on the <drive>:\apps\Apache Software Foundation\Jakarta Isapi Redirector directory. 
    12. Restart the IIS Admin Service.
  4. Verify that the 32-bit applications property is disabled.
    1. In the IIS Manager, expand the server node.
    2. Click 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.
  5. Restart the Application Pool.


Important

If you use IIS web server with BMC Remedy Mid Tier, the following exception occurs and the AR system Admin console does not open because of the invalid characters.

Server Error in '/' Application.

Perform the following steps at <Install Dir>:\inetpub\wwwroot\web.config location:

  1. Update the requestPathInvalidCharacters parameter from the httpRuntime section of the web.config file.
    The default value is as follows:

    <system.web>
    <httpRuntime requestPathInvalidCharacters="<,>,*,%,&,:,\,?"/>
    </system.web>

  2. When you want to add support for any of these characters, remove that particular character from the list. For example,
    <system.web>

        <httpRuntime requestPathInvalidCharacters="<,>,*,%,&,\,?"/>
    </system.web>

    Here, : (colon) is removed.

  3. (Optional) Use the following command if you want to remove all the characters.

    <system.web>
        <httpRuntime requestPathInvalidCharacters="" />
    </system.web>
  4. Save the web.xml file.
  5. Restart the mid tier.

 

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