Install Tomcat 7

1. Download Tomcat 7 from http://tomcat.apache.org/download-70.cgi. Download the 64-bit Windows Zip file.
2. Unzip the file to your c:\ drive and a directory named apache-tomcat-7.0.xx will be created, where xx is the minor version number.
3.  Rename that directory to tomcat.
4. This finishes your Tomcat installation.

In order to distribute load across multiple instances of Tomcat, we need to create two more instances of Tomcat.

A connector in Tomcat is something which allows a client to connect to Tomcat. Tomcat ships will multiple connectors e.g. HTTP, AJP etc. By default, the HTTP connector is configured to listen on port 8080. In our case, the IIS server will act as a client to Tomcat. IIS web server will communicate with Tomcat using the AJP protocol. We need to ensure that we have the ports for the AJP connector configured. We also want all requests to be routed through IIS and do not want anybody to bypass it, i.e we do not want anybody to access the web application through port 8080 using the HTTP connector. Hence, we will disable (comment) the HTTP connector from our configuration.

A worker is simply an instance of Tomcat to which IIS will dispatch requests. In this case, all three Tomcat instances will be workers. Each worker needs to have a unique id, which will be assigned to it using the jvmRoute attribute of the <Engine> element in server.xml. You will see later how and where this id is used by IIS server. Lets start configuring the Tomcat instances:

• Change Shutdown ports:- All three Tomcat instances will reside on the same machine, hence we need to ensure that ports do not conflict. Shutdown ports are where Tomcat listens for the shutdown command. Open server.xml of each tomcat1, locate the <Server > element start tag and change the port number to 8006. Repeat this step for tomcat2 and change the port number to 8007.
• Change AJP ports :- In server.xml of tomcat1, locate the <Connector> element whoseprotocol=”AJP/1.3″ and change the port number to 8010. Similarly for tomcat2, change the port number to 8011
• Disable HTTP Connectors:- In the server.xml of each Tomcat instance, locate the<Connector> element shown below and either delete it or comment it out

  <Connector port=”8080″ protocol=”HTTP/1.1″ connectionTimeout=”20000″ redirectPort=”8443″ />

• Assign worker ids:- In server.xml of tomcat, locate the <Engine> element and add the following attribute to its start tag jvmRoute=”worker0″ (the value of the attribute is workerZERO and notworkerOH). Repeat this step for tomcat1 and assign the value of worker1. Similarly repeat for tomcat2 and assign the value of worker2.

Configure IIS
You will now configure ISAPI redirector plug-in provided by Tomcat. The redirector requires 4 entities:-

• isapi_redirect.dll : This is the IIS plugin which you will download later
• worker.properties: A file that describes the hosts and ports of workers (Tomcat instances/processes)
• uriworkermap.properties: A file that maps URL patterns to workers. Allows you to specify as to which worker will handle the matching URL path request
• isapi_redirect.properties: A file which tells IIS the location of all of the above files.

Lets start the configuration. After you installed IIS, it would have created a directory named c:\inetpub. All configuration will be done in the c:\inetpub directory.

1. Under c:\inetpub, create a subdirectory called isapi. Under c:\inetpub\isapi, create three subdirectories – bin, logs, conf.
2. To download the isapi_redirect.dll, go to  http://www.apache.org/dist/tomcat/tomcat-connectors/jk/binaries/windows/ and download the zip appropriate for your system i.e. 32-bit or 64-bit.
3. Unzip the downloaded file and copy isapi_redirect.dll and paste it under c:\inetpub\isapi\bin
4. Inside c:\inetpub\isapi\conf, create a file named worker.properties. In this file you will create workers, their host and the port on which they will communicate with IIS. Workers are of different types e.g. ajp13 is a worker which communicates with web server  i.e. tomcat instances , lb is the worker which will act as the load balancer, stats worker type will give you load balancing statistics and status information. You will be adding key-value pairs, each key must begin with the wordworker. The complete worker.properties file is shown below. Copy/paste the below to your worker.properties file and save it. Explanation of each line is given above the line in a comment
   

   12345678910111213141516171819202122232425262728293031323334353637

   #The list of workers worker.list=balancer,stats   #The template contains default values. Each worker will inherit #these values and override the port   # the worker type worker.template.type=ajp13 #This could also be an IP address. Since all Tomcat instances #and IIS are installed on the same host, hence "localhost" #will suffice as the value worker.template.host=localhost # AJP port should match the one in server.xml worker.template.port=8009 #load balancing factor worker.template.lbfactor=1   #worker0 inherits everything from template worker.worker0.reference=worker.template   #worker1 inherits from template but overrides port worker.worker1.reference=worker.template worker.worker1.port=8010   #worker2 inherits from template but overrides port worker.worker2.reference=worker.template worker.worker2.port=8011   #The load balancer worker worker.balancer.type=lb worker.balancer.sticky_session=1 #session is sticky #List of workers amongst which load is distributed worker.balancer.balance_workers=worker0,worker1,worker2   #The worker stats will be of type status #will get load balancing statistics worker.stats.type=status

   view rawworker.properties hosted with ❤ by GitHub
5. Inside c:\inetpub\isapi\conf, create a file named uriworkermap.properties. In this file you will map the workers to the URL path patterns. This will tell IIS, which worker will handle a request for a given URL path. As you can see below, the /foo web application is mapped to the load balancer worker, which the /jkstatus path is mapped to the stats worker.
   

   12345

   #/foo and /foo/* are both mapped to balancer worker /foo|/*=balancer   #/jkstatus is mapped to the stats worker /jkstatus/=stats

   view rawuriworkermap.properties hosted with ❤ by GitHub
6. Inside c:\inetpub\isapi\bin, create a file named isapi_redirect.properties. This file will tell IIS, the location of isapi_redirect.dll, worker.properties, uriworkermap.properties and the location of the log file for the redirector plugin. You can copy/paste contents from the file as shown below.
   

   123456789

   #tomcat will be the name of the virtual directory under IIS extension_uri=/tomcat/isapi_redirect.dll #location of the log file log_file=C:\inetpub\isapi\logs\isapi_redirect.log log_level=debug #location of worker.properties worker_file=C:\inetpub\isapi\conf\worker.properties #location of uriworkermap.properties worker_mount_file=C:\inetpub\isapi\conf\uriworkermap.properties

   view rawisapi_redirect.properties hosted with ❤ by GitHub

The remainder of the configuration is through the IIS Manager:

1. To open the IIS Manager, open  Administrative Tools from the Control Panel and then click onInternet Information Services (IIS) Manager
2. You will now create a Virtual Directory named tomcat. Under Connections, navigate to [[Root Node]] > Sites > Default Web Site. Right-click on Default Web Site  and select Add Virtual Directory. ForAlias enter tomcat, and for Physical Path, enter C:\inetpub\isapi\bin. Click OK to close the Edit Virtual Directory window.
3. To configure Handler Mappings, under Default Web Site, select tomcat. In the Features View pane, double-click on Handler Mappings and then select ISAPI-dll, which should be disabled at the moment. Now in the Actions pane, select Edit feature permissions. In the Edit Feature Permissions window, check the Execute option and click OK to close the window. ISAPI-dll should now be enabled.
4. You now need to configure the ISAPI Filter and specify the location of the dll. Select Default Web Site . In the Features View pane, double-click on ISAPI Filters. From the Actions pane, click onAdd. For Filter Name, enter isapi_redirect. For Executable, enter the absolute path of the location of the isapi_redirect.dll – C:\inetpub\isapi\bin\isapi_redirect.dll.
5. Finally, you have to now enable the ISAPI extension which you have configured above. In theConnections pane, click on the root node. In the Features View pane, double-click on ISAPI and CGI Restrictions. In the Actions pane, click on Add. This will open the Edit ISAPI or CGI Restrictions window. For the ISAPI or CGI Path field, enter the absolute path of isapi_redirect.dll – C:\inetpub\isapi\bin\isapi_redirect.dll. In the Description field, enter isapi_redirect. Also make sure to check the option Allow extension path to execute. Click OK to close this window.
6. This step  is only for those who have downloaded a 32 bit version of isapi_redirect.dll, but have a 64 bit operating system. If you already downloaded the 64 bit version, then please ignore this step. Click on [[Root Node]] > Application Pools. In the Features View pane, select DefaultAppPool and then click on Advanced Settings… in the Actions pane. In the Advanced Settings window, under the(General) section, set Enable 32-Bit Applications to true. Click OK to close the Advanced Settings window.