...

Configure Tomcat

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

...

 netstat -na | findstr 8009

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

1. Download and Configure an ISAPI Filter  - this is the recommended approach and should be tried first. Contact Customer Support with any questions.
2. Install the IIS to Tomcat Connector  

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

...

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

Install the IIS to Tomcat Connector

• Download the connector project from:  BonCode Connector website. Click on the link to download the latest version.
• 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:

Image Added

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

Image Added

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

Image Added

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

Image Added

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

Image Added

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

Image Added

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

IIS 6 Configurations

In your Windows Server:

...

• Create a virtual directory for in 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

...

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  if you will be using [http://docs.frevvo.com/docs/index.php/V4_Working_with_LDAP#Single_Sign_On_with_Frevvo.2C_IIS_and_Active_Directory frevvo and LDAP SSO] Live Forms and LDAP SSO

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

...

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 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 )
2. Click on '''Add Virtual Directory'''
3. Configure the alias to '''jakarta'''
4. Set the path to c:\isapi\bin

...

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:

...

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  is not checked.

IIS user permissions

...