You can make IIS host servlets and JSP by using Tomcat.It goes like this. You can download from the http://jakarta.apache.org/tomcat/ ****Document Conventions and Assumptions**** <tomcat_root> is the root directory of tomcat. Your Tomcat installation should have the following subdirectories: <tomcat_root>\conf - Where you can place various configuration files <tomcat_root>\webapps - Containing example applications <tomcat_root>\bin - Where you place web server plugins In all the examples in this document <tomcat_root> will be d:\tomcat. A worker is defined to be a tomcat process that accepts work from the IIS server. ****Supported Configuration**** The IIS-Tomcat redirector was developed and tested on: WinNT4.0-i386 SP4/SP5/SP6a (it should be able to work on other versions of the NT service pack.) IIS4.0 and PWS4.0 Tomcat3.0 - Tomcat3.1 build of 02/07/2000 The redirector uses ajp12 to send requests to the Tomcat containers. ****Installation**** The IIS redirector is not part of the "official" build of Jakarta, You can obtain the code and binaries needed for it by accessing http://jakarta.apache.org/builds/tomcat/release/v3.1_beta_1/bin/w in32/i386/. The redirector related file is isapi_redirect.dll. The Tomcat redirector requires three entities: isapi_redirect.dll - The IIS server plugin, either obtain a pre- built DLL workers.properties - A file that describes the host(s) and port (s) used by the workers (Tomcat processes). A sample workers.properties can be found under tomcat/conf. uriworkermap.properties - A file that maps URL-Path patterns to workers. A sample uriworkermap.properties can be found in the CVS under tomcat/conf. The installation includes the following parts: 1. Configuring the ISAPI redirector with a default /examples context and checking that you can serve servlets with IIS. 2. Adding more contexts to the configuration. ****Configuring the ISAPI Redirector**** In this document I will assume that isapi_redirect.dll is placed in d:\tomcat\bin\iis\i386\isapi_redirect.dll and that you created the properties files are in d:\tomcat\conf. In the registry, create a new registry key named "HKEY_LOCAL_MACHINE\SOFTWARE\Apache Software Foundation\Jakarta Isapi Redirector\1.0" Add a string value with the name extension_uri and a value of /jakarta/isapi_redirect.dll Add a string value with the name log_file and a value pointing to where you want your log file to be (for example d:\tomcat\isapi.log) Add a string value with the name log_level and a value for your log level (can be debug, inform, error or emerg). Add a string value with the name worker_file and a value of D:\tomcat\conf\workers.properties Add a string value with the name worker_mount_fileand a value of D:\tomcat\conf\uriworkermap.properties Using the IIS management console, add a new virtual directory to your IIS/PWS web site. The name of the virtual directory must be jakarta, its physical path should be the directory where you placed isapi_redirect.dll (in our example it is d:\tomcat\bin\iis\i386). While creating this new virtual directory assign it with execute access. Using the IIS management console, add isapi_redirect.dll as a filter in your IIS/PWS web site. The name of the filter should reflect its task (I use the name jakarta), its executable must be our d:\tomcat\bin\iis\i386\isapi_redirect.dll. For PWS, you'll need to use regedit and add/edit the "Filter DLLs" key under HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\W3SVC\Parame ters. This key contains a "," separated list of dlls ( full paths ) - you need to insert the full path to isapi_redirect.dll. Restart IIS (stop + start the IIS admin server), make sure that the jakarta filter is ed with a green up-pointing arrow. (costin)Under Win98 you may need to cd WINDOWS\SYSTEM\inetsrv and type PWS /stop ( the DLL and log files are locked - even if you click the stop button, PWS will still keep the DLLs in memory. ). Type pws to start it again. That's all, you should now start tomcat and ask IIS to serve you the /examples context.
You can download from the http://jakarta.apache.org/tomcat/
****Document Conventions and Assumptions**** <tomcat_root> is the root directory of tomcat. Your Tomcat installation should have the following subdirectories: <tomcat_root>\conf - Where you can place various configuration files
<tomcat_root>\webapps - Containing example applications
<tomcat_root>\bin - Where you place web server plugins In all the examples in this document <tomcat_root> will be d:\tomcat. A worker is defined to be a tomcat process that accepts work from the IIS server. ****Supported Configuration****
The IIS-Tomcat redirector was developed and tested on: WinNT4.0-i386 SP4/SP5/SP6a (it should be able to work on other versions of the NT service pack.)
IIS4.0 and PWS4.0
Tomcat3.0 - Tomcat3.1 build of 02/07/2000
The redirector uses ajp12 to send requests to the Tomcat containers. ****Installation****
The IIS redirector is not part of the "official" build of Jakarta, You can obtain the code and binaries needed for it by accessing
http://jakarta.apache.org/builds/tomcat/release/v3.1_beta_1/bin/w
in32/i386/. The redirector related file is isapi_redirect.dll. The Tomcat redirector requires three entities: isapi_redirect.dll - The IIS server plugin, either obtain a pre- built DLL
workers.properties - A file that describes the host(s) and port (s) used by the workers (Tomcat processes). A sample workers.properties can be found under tomcat/conf. uriworkermap.properties - A file that maps URL-Path patterns to workers. A sample uriworkermap.properties can be found in the CVS under tomcat/conf.
The installation includes the following parts: 1. Configuring the ISAPI redirector with a default /examples context and checking that you can serve servlets with IIS. 2. Adding more contexts to the configuration. ****Configuring the ISAPI Redirector****
In this document I will assume that isapi_redirect.dll is placed in d:\tomcat\bin\iis\i386\isapi_redirect.dll and that you created the properties files are in d:\tomcat\conf. In the registry, create a new registry key named "HKEY_LOCAL_MACHINE\SOFTWARE\Apache Software Foundation\Jakarta Isapi Redirector\1.0"
Add a string value with the name extension_uri and a value of /jakarta/isapi_redirect.dll
Add a string value with the name log_file and a value pointing to where you want your log file to be (for example d:\tomcat\isapi.log)
Add a string value with the name log_level and a value for your log level (can be debug, inform, error or emerg). Add a string value with the name worker_file and a value of D:\tomcat\conf\workers.properties
Add a string value with the name worker_mount_fileand a value of D:\tomcat\conf\uriworkermap.properties
Using the IIS management console, add a new virtual directory to your IIS/PWS web site. The name of the virtual directory must be jakarta, its physical path should be the directory where you placed isapi_redirect.dll (in our example it is
d:\tomcat\bin\iis\i386). While creating this new virtual directory assign it with execute access.
Using the IIS management console, add isapi_redirect.dll as a filter in your IIS/PWS web site. The name of the filter should reflect its task (I use the name jakarta), its executable must be our d:\tomcat\bin\iis\i386\isapi_redirect.dll. For PWS, you'll need to use regedit and add/edit the "Filter DLLs" key under
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\W3SVC\Parame ters. This key contains a "," separated list of dlls ( full paths ) - you need to insert the full path to
isapi_redirect.dll.
Restart IIS (stop + start the IIS admin server), make sure that the jakarta filter is ed with a green up-pointing arrow. (costin)Under Win98 you may need to cd WINDOWS\SYSTEM\inetsrv and type PWS /stop ( the DLL and log files are locked - even if you click the stop button, PWS will still keep the DLLs in memory. ). Type pws to start it again.
That's all, you should now start tomcat and ask IIS to serve you the /examples context.