Setting up the ISAPI redirect properties for IIS

The ISAPI redirector checks for the properties file during initialisation and reads the redirection configuration from the file.
To set up the ISAPI redirector .properties file:
Open the isapi_redirect-1.2.40.properties file in a text editor and populate it with the following content.
# Configuration file for the Jakarta ISAPI Redirector
# URL http://tomcat.apache.org/connectors-doc/reference/iis.html

# This file MUST reside in the same directory as the ISAPI redirector
# and MUST be with the same name as the ISAPI redirector DLL but with
# a .properties extension.

# Starting with version 1.2.27 two environment variables are dynamically
# added to the environment that can be used inside .properties files.
# * JKISAPI_PATH - Full path to the ISAPI Redirector.
# * JKISAPI_NAME - Name of the ISAPI Redirector dll without extension

# 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-1.2.40.dll

#Full path to the log file for the ISAPI Redirector
log_file=$(JKISAPI_PATH)/log/isapi_redirect-1.2.40.log

# Log level (debug, info, warn, error or trace)
log_level=info

# Full path to the workers.properties file
worker_file=$(JKISAPI_PATH)/conf/workers.properties

# Full path to the uriworkermap.properties file
worker_mount_file=$(JKISAPI_PATH)/conf/uriworkermap.properties

# If value is set to true, chunked encoding is supported by the server.
enable_chunked_encoding=true

# By default its value is 1, which means we use the SF_NOTIFY_AUTH_COMPLETE
# event. If you set this to 0, then we use SF_NOTIFY_PREPROC_HEADERS. This
# might be needed for IIS 5.1 when handling requests using the PUT HTTP
# method or as a workaround for allowing the SPNEGO/NTLM authentication to
# be performed by Tomcat, as opposed to IIS.
auth_complete=false

If you want to increase the detail in the log, change the log_level value to debug or trace.

To configure multiple redirectors:
  1. Ensure that you have an additional directory similar to mod_jk, for example mod_jk_node2.
  2. Ensure that the isapi_redirect-1.2.40.properties file in the additional directory points to the correct location for the duplicate isapi_redirect-1.2.40.dll, isapi_redirect-1.2.40.log, and uriworkermap.properties files.
  3. You also need to add the new website using the IIS Manager console.