Skip to main content

Manually Set up DocuShare 3.x to use IIS on Win 2K3 Server

Updated
Configuring the IIS Out of Process with Tomcat 4.0.1:

The files needed for DocuShare-IIS configuration have been installed into the Tomcat Servlet included with DocuShare. The files are in these locations:

%DOCUSHARE_HOME%\tomcat\server\lib\jk.jar
%DOCUSHARE_HOME%\tomcat\server\lib\tomcat-util.jar
%DOCUSHARE_HOME%\bin\native\isapi_redirect.dll
%DOCUSHARE_HOME%\tomcat\conf\ntiis\workers.properties
%DOCUSHARE_HOME\tomcat\conf\ntiis\uriworkermap.properties
%DOCUSHARE_HOME%\tomcat\conf\ntiis\iis_redirect.reg
%DOCUSHARE_HOME%\tomcat\conf\server.xml
%DOCUSHARE_HOME%\tomcat\log\iis_redirect.log

The files marked in bold need to be edited to suit your environment.
  1. Edit the worker.properties file. Update the following fields to suit your environment:
    workers.tomcat_home=%DOCUSHARE_HOME%\tomcat
    workers.java_home=%DOCUSHARE_HOME%\jdk1.4.2

  2. Edit the uriworkermap.properties file. Add any web sites that IIS needs to serve to Tomcat.
    #
    # Default worker to be used through our mappings
    #
    default.worker=ajp13
    #
    # Sites to be redirected to Tomcat
    #
    /examples=$(default.worker)
    /examples/*=$(default.worker)

    For example, if you want DocuShare to be the DocuShare root, add the following two lines to the uriworkermap.properties file:

    /DocuShare=$(default.worker)
    /DocuShare/*=$(default.worker)
  3. Edit the iis_redirect.reg registry file. Modify the paths to suit your environment. For example:
    REGEDIT
    [HKEY_LOCAL_MACHINE\SOFTWARE\Apache Software Foundation\Jakarta Isapi Redirector\1.0]

    extension_uri = /jakarta/isapi_redirect.dll

    log_file = %DOCUSHARE_HOME%\tomcat\logs\iis_redirect.log

    log_level = emerg

    worker_file = %DOCUSHARE_HOME%\tomcat\conf\ntiis\workers.properties

    worker_mount_file = %DOCUSHARE_HOME%\tomcat4\conf\ntiis\uriworkermap.properties

  4. Execute the registry file by double-clicking on [iis_redirect.reg], or right-clicking on [iis_redirect.reg] and selecting [Merge].

    To verify that the registry was successful:
    1. Click on [Start] and select [Run].
    2. In the Open field, type regedit and click [OK].
    3. View the contents.

  5. Edit the server.xml file. Open the %DOCUSHARE_HOME%\tomcat\conf\server.xml file for editing. The AJP connector is not enabled by default. To enable it, uncomment (remove the ) the following section in $DOCUSHARE_HOME/tomcat/conf/server.xml (in the original file this is line 74 ;):



    NOTE: When placing new files (for example, jars) into %DOCUSHARE_HOME%\tomcat\lib edit the wrapper.properties, and make sure to restart WWW Publishing Service (IIS), rather than the Tomcat service, in order to have the new libs used by Tomcat.

  6. Add Jakarta to IIS and register adding an ISAPI filter.
    1. Start the Internet Services Manager.
    2. Go to Default web site.
    3. Add a new virtual directory called jakarta that points to %DOCUSHARE_HOME%\tomcat\bin\native\, where %DOCUSHARE_HOME%\tomcat is your actual tomcat directory typed out, for example, C:\DocuShare\tomcat\bin\native.
    4. Make sure execute permissions are enabled.

  7. Add the ISAPI filter isapi_redirect.dll to the IIS server.
    1. Using IIS Manager, open the properties for the Web Sites.
    2. Click on the [ISAPI Filters] tab.
    3. Click on [Add] to add the Jakarta Redirector. The redirector file is \tomcat\bin\native\isapi_redirect.dll.

  8. After adding the isapi filter, the status will be a red down arrow. Stop and restart the Default Web Sites in IIS. The status should now be green.

  9. Add an Extension and set IIS Permission for running Jakarta.
    1. Navigate to Web Services Extension, and click on [Add a new Web Services Extenion].
    2. In the Extension Name field, type Jakarta Redirector then click on [Add].
    3. In the Path to File field, type %DSHome%\tomcat\bin\native\isapi_redirect.dll. and click on [OK]. Jakarta Redirector will be displayed on the Web Services Extension, but will be prohibited.
    4. Click on [Allow] to allow the Extension.
    5. Restart IIS from Services Manager.