Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Code Block
 netstat -na | findstr 8009

 When When the tomcat server configuration is completed, choose one of two methods listed below to continue with the configuration: 

...

 install the IIS to Tomcat Connector

...

.

...

Install the IIS to Tomcat Connector

...

Proceed to the IIS configuration for your specific version (IIS6 and IIS7 below). 

Using the ISAPI Filter

Follow these steps if you are using the ISAPI filter instead of the IIS to tomcat connector approach.

Download and Configure an ISAPI Filter

...

Code Block
# 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=c:\isapi\logs\isapi_redirect.log

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

# Full path to the workers.properties file
worker_file=c:\isapi\conf\workers.properties

# Full path to the uriworkermap.properties file
worker_mount_file=c:\isapi\conf\uriworkermap.properties

If you have modified the port for the AJP Connector you will need to modify the workers.properties file. The file c:\isap\conf\workers.properties assumes that Tomcat is running on the same machine as IIS and using the default port (8009) for AJP.  Make adjustments if necessary.

Code Block
worker.list=workerFrevvo
worker.workerFrevvo.host=localhost
worker.workerFrevvo.port=8009
worker.workerFrevvo.type=ajp13

 The file c:\isap\conf\uriworkmap.properties lists the http request paths that will be forwarded to 

Code Block
/frevvo/*=workerFrevvo

Proceed to the IIS configuration for your specific version (IIS6 and IIS7 below). 

IIS 6 Configurations

In your Windows Server:

  1. Open Open Control Panel, then then Administrative Tools and open  and open Internet Information Services.
  2. Add the ISAPI Filter to IIS
    1. Right-click on Default Web Site (or the Web Site that should be responsible for proxying requests to to ), and click on Properties.
    2. Click the ISAPI Filters tab.
    3. Click Add and create one. Enter Enter jakarta as  as the Filter Name and enter the location of the isapi_redirect.dll file for the executable.
    4. Click OK, Apply and then OK.

Image Modified 

  • Create a virtual directory for  in IIS. 
    1. Right-click on Default Web Site (or the Web Site that should be responsible for proxying requests to to ), choose New and then Virtual Directory.
    2. Go through the creation wizard. Set the alias to be the same as the context path configured in c:\isapi\bin\isapi_redirect.properties. If you kept the defaults in the section section Download and Configure an ISAPI Filter you  you would enter enter jakarta.

Image Modified 

  • Enter the path to the directory that contains the isapi_redirect.dll

Image Modified

  • Grant the 'Execute' permission for the Virtual Directory by checking the 'Execute' checkbox.
    • You will need to restart the IIS Service. To do this, browse to Control Panel, click Administrative Tools, click on Services, find the IIS Admin Service and click restart.

Image Modified

  • Add a Web Service Extension
    1. Right-click on Web Service Extensions and choose Add a new Web Service Extension...
    2. Enter Enter jakarta for  for the Extension Name and then add the isapi_redirect.dll file to the required files
    3. Select the the Set extension status to Allowed check check-box, then click OK

Image Modified

The ISAPI filter is installed and configured. You can check the status of the filter: right click

...

on Default Web Site

...

 and select the

...

tab ISAPI Filters. The ISAPI filter should be listed with a green arrow pointing upwards as shown below:

Image Modified

IIS 7 Configurations

It is necessary to have the role Web Server  ISAPI Extensions and ISAPI Filters configured in IIS. If this is a new installation of IIS:

  1. Navigate to Start Menu > Administrative Tools > Server Manager.
  2. Select 'Web Server (IIS)' in Server Manager > Roles.
  3. Click 'Add Role Services' and follow the Wizard.
  4. You also need to select select Windows Authentication if you will be using using Live Forms and LDAP SSO

Image Modified

If this is not a new installation of IIS you can verify the installed roles: 

  1. Navigate to Start Menu > Administrative Tools > Server Manager.
  2. Click on Roles and then Web Server (IIS).
  3. Check that the required role services are installed.

...

  1. Navigate to Start > Administrative Tools > Internet Information Services (IIS) Manager
  2. Click the Default Web Site (or the Web Site that should be responsible for proxying requests to to ), and click on ISAPI Filters (on the right panel).
  3. Check if there is a Filter that points to the isapi_redirect.dll file and that it is in the right location. If not, click Add and create one. Enter Enter jakarta as the Filter Name and enter the location of the isapi_redirect.dll file.
  4. Click OK.

...

  1. Right-click on Default Web Site (or the Web Site that should be responsible for proxying requests to to )
  2. Click on on Add Virtual Directory
  3. Configure the alias to to jakarta
  4. Set the path to c:\isapi\bin

Add a Web Service Extension

Navigate to the servers and highlight your server:

Image Modified

  1. Navigate to 'ISAPI and CGI Restrictions'.
  2. Add isapi_redirect.dll extension.
  3. In the wizard, allow the extension to execute.

...

  1. Navigate to Start Menu > Administrative Tools > Server Manager.
  2. In the Server Manager, click on Roles and right click Web Server (IIS).
  3. On the right panel, look for the section section System Services.
  4. Restart World Wide Web Publishing Service.

If you already

...

installed  you can test the IIS configuration by pointing your browser to: http://localhost/frevvo/web/static/home

Trouble Shooting

Sometimes the IIS and ISAPI configurations may not work as described above. In a number of cases this may be related
to specific settings in your environment. Here are some things to check:

On windows 2008: Encrypt Content to Secure Data

  1. Right Click on the isapi forlder (c:\isapi if used the defaults)
  2. Select Properties. 
  3. In the General Tab select select Advanced
  4. In the Advanced Attributes verify that the checkbox checkbox Encrypt contents to secure data is not checked.

IIS user permissions

Check if the user running IIS has enough permissions to run the ISAPI dll.

...