Page History

Permissions

The official documentation lacks a few important bits around file permissions that must be set if the application pool identity the connector is running under does not have global permissions to the servers file system:

• The directory with your isapi_redirect.dll and associated .properties files must be at least read only to the application pool identity account
• If you have logging enabled for the filter then the application pool identity must have read & write access to the log file
• If you use the registry for the configuration then the application pool identity must have read access to the keys If you miss any of the above then the filter simply will not work and you will not receive any form of error messages to tell you it has not worked.
  

Windows 2008 / IIS 7 Step by Step

The following steps detail setting up IIS to function correctly with the connector, it assumes you have already completed the .properties or registry configuration:

Allow ISAPI Filter to run:

• In the IIS Manager console select the computer node
• Open the "ISAPI and CGI" restrictions panel
• Click the "Add" button
• Under "ISAPI or CGI path" enter the full path to the Connector ISAPI dll
• Under "Description" add something meaningful such as "Tomcat"
• Check "Allow extension path to execute"
• Click "Ok"
  

Enable ISAPI Filter for individual sites:

• In the IIS Manager console open the computer node and select the website to add the ISAPI filter to
• Right click on the website node and add a new virtual directory pointing to the directory containing the dll and associated .properties files
• Open the "ISAPI Filters" panel
• Click the "Add" button
• Under "Filter Name" add something meaningful such as "Tomcat"
• Under "Executable" enter the full path to the Connector ISAPI dll
• Click "Ok"
  

If you are using the website for hosting other technologies (such as asp.net) the order of execution for the filters may have to be changed for everything to work as expected. In order to do this click "View Ordered List" in the "ISAPI Filters" panel for a website and then use the "Move Up" and "Move Down" buttons to reorganise the execution order. If you would like asp.net to handle cases such as 404's then the Tomcat filter should appear BEFORE those for .net. If you are using specialist authentication filters (such as CA SiteMinder) then these should appear before Tomcat so that requests are correctly authenticated prior to being received by the connector.

Setup

Configuring Tomcat and IIS is documented at the IIS Howto page . The instructions there work fine, but there is a setup program which allows you to skip steps 1 through 7 in the "Configuring the ISAPI Redirector" section of this page. Also, step 8 can be done using a VBScript file like this:

...

To add the Jakarta WSE programmatically, run the following line at a command prompt:
(Change the File Path/File Name as appropriate)

...

IIS and Tomcat: you found also in Other links see here UsefulLinks. Little notice: Using the present help, I made working IIS 6.0 , Jk, Tomcat 5.0 on Windows2003 server... (but in link before you found works also with jk2!)

...

Added by JohnJames on 12 April 2011:

I have used the .net based BonCode JK connector rather than the ISAPI redirector to connect IIS6 and IIS7 to Apache Tomcat 6. This worked very easily. There is GUI installer in the distribution package that worked for me. There are also videos on how to do the setup.