Install and Configure the Form Server

IIS configuration is a complex task. The integration steps below relating to your IIS web server should be performed by your IIS Web System Administrator. 

Configure Tomcat

It is necessary to configure Tomcat to receive proxied requests from IIS.

• Stop Tomcat. 
• In a text editor open FREVVO_HOME/tomcat/conf/server.xml 
• Ensure that the AJP Connector is enabled by uncommenting out the section.   

<Connector port="8009" protocol="AJP/1.3" redirectPort="8443"
maxHttpHeaderSize="32768"
useBodyEncodingForURI="true" 
tomcatAuthentication="false" /

• Start Tomcat
• Check that the configured AJP port is enabled and listening for requests. On a windows command prompt:

 netstat -na | findstr 8009

 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 - this is the recommended approach and should be tried first. Contact Customer Support with questions.
• Download and Configure an ISAPI Filter

Install the IIS to Tomcat Connector

• Download the connector project from: http://tomcatiis.riaforge.org/
• To avoid multiple issues with using the zip file content, unblock the package before unzipping. Simply right click on the zip file and click “Unblock” on the “General” tab:

• Extract the project zip file.
• Execute the Connector_Setup.exe file.
• Accept the License Agreement and click Next.
• Follow the prompts and in the Apache Tomcat location details enter correct AJP port as configured in the tomcat server.xml file above:

• Click Next and use default values in all the prompts until you reach the Select Handler Mapping prompt.
• In Select Handler Mapping prompt select the option Servlet (add wildcard reference and pass all traffic to tomcat)

• Continue to the final prompt and click Install to finish the connector installation.
• Test the configuration by browsing http://localhost/frevvo/web/login
• If you see an access error like the one below,  make sure that the Application Pool Identity (the security account set for the Application Pool) also has write permissions to C:\WINDOWS\Microsoft.NET directory.

• To check the currently set identity, open IIS and right click on your Application Pool, then click on the Identity tab:

• Then in your Windows explorer, right click on C:\WINDOWS\Microsoft.NET directory and click on Properties. Check if the identity user set of your Application Pool has the ‘write’ permissions for this directory. If not, then add the user permissions.

• Test the configuration again by browsing http://localhost/frevvo/web/login

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

1. Download  isapi package here. The archive is a pre-packaged isapi filter along with a recommended directory structure and pre-configured files. It is a starting point.
2. Expand the archive. For the sake of this document we will assume the archive is expanded under your "c:\" drive. If you do that, you should have a folder c:\isapi after expanding. 
3. The isapi archive contains version 1.2.28 of the isapi connector for win 32. If you need to upgrade and/or IIS is running on win64, download the ISAPI Redirect DLL from the Apache site. If you download a new isapi filter:  
   1. When downloading, choose the version of Windows that IIS is running on (either win32 or win64), and then choose the latest available jk version. 
   2. The file to download is named isapi_redirect_X.X.X.dll, where 'X.X.X' is the version number. You will need to remove the version number from the DLL file (i.e. it needs to be named isapi_redirect.dll). 
   3. After downloading and renaming, update the dll in c:\isapi\bin. 
4. Under c:\isapi\bin you will find isapi_redirect.properties (shown below). If you expanded the filter in c:\isapi you don't have to change anything. Otherwise, just edit the paths accordingly.

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

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 

/frevvo/*=workerFrevvo

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

IIS 6 Configurations

In your Windows Server:

1. Open Control Panel, then Administrative Tools 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 ), and click on Properties.
   2. Click the ISAPI Filters tab.
   3. Click Add and create one. Enter jakarta as the Filter Name and enter the location of the isapi_redirect.dll file for the executable.
   4. Click OK, Apply and then OK.

• 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 ), 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 Download and Configure an ISAPI Filter you would enter jakarta.

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

• 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.

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

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:

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 Windows Authentication if you will be using Live Forms and LDAP SSO

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.

Configure the ISAPI Filter

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 ), 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 jakarta as the Filter Name and enter the location of the isapi_redirect.dll file.
4. Click OK.

Add a Virtual Directory

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

Add a Web Service Extension

Navigate to the servers and highlight your server:

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

Configure the HTTP Handler Mappings

1. Open the IIS Manager
2. Click on the Default Web Site
3. Double click on "Handler Mappings" on the right.
4. Select the ISAPI-dll mapping
5. On the right column click on "Edit Feature Permissions"
6. Check the "Execute" checkbox.

Restart IIS

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 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 Advanced
4. In the Advanced Attributes verify that the 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.