nacho 01/06/02 15:00:25
Modified: src/doc tomcat-iis-howto.html
Log:
Changed docs, isapi_redirector works smoothly with ajp13,
andthis protocol is suppoused to be the default for Tomcat 3.3,
changed references and examples to ajp13,
thus ajp12 is used for explanations too.
Revision Changes Path
1.3 +84 -77 jakarta-tomcat/src/doc/tomcat-iis-howto.html
Index: tomcat-iis-howto.html
===================================================================
RCS file: /home/cvs/jakarta-tomcat/src/doc/tomcat-iis-howto.html,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- tomcat-iis-howto.html 2001/02/09 02:28:03 1.2
+++ tomcat-iis-howto.html 2001/06/02 22:00:25 1.3
@@ -1,6 +1,6 @@
<html>
<head>
- <!-- $Id: tomcat-iis-howto.html,v 1.2 2001/02/09 02:28:03 larryi Exp $ -->
+ <!-- $Id: tomcat-iis-howto.html,v 1.3 2001/06/02 22:00:25 nacho Exp $ -->
<!-- Copyright 1999-2001, Apache Software Foundation -->
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<link rel="stylesheet" href="style.css">
@@ -45,10 +45,10 @@
<li>Tomcat3.0 - Tomcat3.3</li>
</ol>
-<p>The redirector uses <b>ajp12</b> to send requests to the Tomcat
-containers. There is also an option to use Tomcat in process, more about the
-in-process mode can be found in the <a href="in-process-howto.html">in process
-howto.</a></p>
+<p>The redirector uses <b>ajp13</b> or <b>ajp12</b> to send requests to the Tomcat
+ containers. There is also an option to use Tomcat in process, more about the
+ in-process mode can be found in the <a href="in-process-howto.html">in process
+ howto.</a></p>
<h2>Installation</h2>
@@ -148,12 +148,12 @@
<p><tt>/context/*=worker_name</tt></p>
-<p>Workers and their name are defined in workers.properties, by default
workers.properties
-comes with a single pre-configured worker named "ajp12" so you can use
it. As an
-example, if you want to add a context named "shop", the line that you
should add
-to <tt>uriworkermap.properties</tt> will be:</p>
+<p>Workers and their name are defined in workers.properties, by default
workers.properties
+ comes with 2 pre-configured workers named "<b>ajp13</b>" and
"<b>ajp12</b>"
+ so you can use it. As an example, if you want to add a context named
"shop",
+ the line that you should add to <tt>uriworkermap.properties</tt> will be:</p>
-<p><tt>/shop/*=ajp12</tt></p>
+<p><tt>/shop/*=ajp13</tt></p>
<p>After saving <tt>uriworkermap.properties</tt> restart IIS and it will serve the
new context.</p>
@@ -195,7 +195,7 @@
<tt>uriworkermap.properties</tt>, If the current request matches one of the
entries in the list of
URI-paths, the filter transfer the request to the extension.</li>
<li>The extension collects the request parameters and forwards them to the
appropriate
- worker using the ajp12 protocol.</li>
+ worker using the ajp1X protocol.</li>
<li>The extension collects the response from the worker and returns it to the
browser.</li>
</ol>
@@ -223,13 +223,12 @@
This requires a change to the <tt>uriworkermap.properties</tt>. For the examples
context it
requires to replace the following line:</p>
-<p><tt>/examples/*=ajp12</tt></p>
+<p><tt>/examples/*=ajp13</tt></p>
<p>with the following two lines:</p>
-<p><tt>/examples/*.jsp=ajp12 <br>
-/examples/servlet/*=ajp12 </tt></p>
-
+<p><tt>/examples/*.jsp=ajp13<br>
+ /examples/servlet/*=ajp13</tt></p>
<p>As you can see the second configuration is more explicit, it actually instruct
the
redirector to redirect only requests to resources under <tt>/examples/servlet/</tt>
and
resources under <tt>/examples/ </tt>whose name ends with <tt>.jsp</tt>. This is
@@ -238,10 +237,10 @@
<p>You can even be more explicit and provide lines such as:</p>
-<p><tt>/example/servletname=ajp12</tt> </p>
+<p><tt>/example/servletname=ajp13</tt> </p>
-<p>that instructs the redirector to redirect request whose URL-Path equals
-<tt>/example/servletname </tt>to the worker named ajp12.</p>
+<p>that instructs the redirector to redirect request whose URL-Path equals
<tt>/example/servletname
+ </tt>to the worker named ajp13.</p>
<h3>Protecting the WEB-INF Directory</h3>
@@ -263,23 +262,28 @@
<ol>
<li>An entry that lists all the workers defined. For example:<br>
- <tt>worker.list=ajp12, ajp12second</tt></li>
- <li>Entries that define the host and port associated with these workers. For
example:<br>
- <tt>worker.ajp12.host=localhost<br>
+ <tt>worker.list=ajp12, ajp13, ajp13second</tt></li>
+ <li>Entries that define the host and port associated with these workers. For
+ example:<br>
+ <tt>worker.ajp12.host=farhost<br>
worker.ajp12.port=8007<br>
- worker.ajp12second.host=otherhost<br>
- worker.ajp12second.port=8007</tt></li>
+ worker.ajp13.host=localhost<br>
+ worker.ajp13.port=8009<br>
+ worker.ajp13second.host=otherhost<br>
+ worker.ajp13second.port=8009</tt></li>
</ol>
-<p>The above examples defined two workers, now we can use these workers to serve two
+<p>The above examples defined three workers, now we can use these workers to serve
two
different contexts each with its own worker. For example look at the following
<tt>uriworkermap.properties</tt> fragment:</p>
<p><tt>/examples/*=ajp12 <br>
-/webpages/*=ajp12second </tt></p>
+ /webapp1/*=ajp13 <br>
+ /webapp2/*=ajp13second </tt></p>
-<p>As you can see the examples context is served by ajp12 while the webpages
context is
-served by ajp12second.</p>
+<p>As you can see the examples context is served by ajp12 while the webapp1 context
+ is served by ajp13, and the webapp2 context is served by the ajp13second worker.
+</p>
<h2><a name="troubleshoot">Troubleshooting</a></h2>
@@ -299,74 +303,76 @@
<h3>Win98</h3>
<ol>
- <li>Make sure web site activity is being logged. For PWS 4.0 make sure
- "Save Web Site Activity Log" is checked in the Advanced Options of
- the Personal Web Manager.</li>
+ <li>Make sure web site activity is being logged. For PWS 4.0 make sure "Save
+ Web Site Activity Log" is checked in the Advanced Options of the Personal
+ Web Manager.</li>
<li>Start the IIS service and Tomcat.</li>
- <li>Check for the presence of the ISAPI redirector log file you specified in the
- <tt>log_file</tt> setting. If not found, check the following:
+ <li>Check for the presence of the ISAPI redirector log file you specified in
+ the <tt>log_file</tt> setting. If not found, check the following:
<ol type="A">
- <li>Check the "Filter DLLs" setting in the
-
"HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\W3SVC\Parameters"
+ <li>Check the "Filter DLLs" setting in the
"HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\W3SVC\Parameters"
key and make sure the path is correct.</li>
- <li>Check the spelling of the "HKEY_LOCAL_MACHINE\SOFTWARE\Apache
Software
- Foundation\Jakarta Isapi Redirector\1.0" key. Case isn't important,
- but an incorrect letter will prevent the isapi_redirect.dll from finding
+ <li>Check the spelling of the "HKEY_LOCAL_MACHINE\SOFTWARE\Apache
Software
+ Foundation\Jakarta Isapi Redirector\1.0" key. Case isn't important,
+ but an incorrect letter will prevent the isapi_redirect.dll from finding
its registry settings.</li>
- <li>Check the <tt>log_file</tt> setting for typos, name and data. Also
- insure the directory in which the log file will appear already exists.</li>
+ <li>Check the <tt>log_file</tt> setting for typos, name and data. Also insure
+ the directory in which the log file will appear already exists.</li>
</ol>
- If the above are set correctly, the ISAPI redirector should be able to create
+ If the above are set correctly, the ISAPI redirector should be able to create
the log file.</li>
- <li>Invoke the URL "http://localhost/examples/jsp/index.html" in your
- browser. Case is important in Tomcat 3.2. The characters following
- "localhost" in the URL must be lower case. If the page fails to
- appear, stop the IIS service (required to view the IIS log file). Then
- examine the last line in the IIS log file in found in SYSTEM/LogFiles/W3SVC1.
+ <li>Invoke the URL "http://localhost/examples/jsp/index.html" in your
+ browser. Case is important in Tomcat 3.2. The characters following
"localhost"
+ in the URL must be lower case. If the page fails to appear, stop the IIS
service
+ (required to view the IIS log file). Then examine the last line in the IIS
+ log file in found in SYSTEM/LogFiles/W3SVC1.
<ol type="A">
- <li>If the last line contains: <tt>GET "/examples/jsp/index.html
HTTP/1.1" 404</tt>,
- then the ISAPI redirector is not recognizing that it should be handling
- requests for the "/examples" context. Check the following:
+ <li>If the last line contains: <tt>GET "/examples/jsp/index.html
HTTP/1.1"
+ 404</tt>, then the ISAPI redirector is not recognizing that it should
+ be handling requests for the "/examples" context. Check the
+ following:
<ol>
<li>Check the <tt>extension_uri</tt> name for typos.</li>
<li>Check the <tt>worker_file</tt> setting for typos, name and data.</li>
<li>Check the <tt>worker_mount_file</tt> setting typos, name and
data.</li>
</ol>
- If these are set correctly, the ISAPI redirector should recognize that it
- should handle requests for the "/examples" context.</li>
- <li>If the last line contains something like: <tt>GET
"/jakarta/isapi_redirect.dll
- HTTP1.1"</tt>, then the ISAPI redirector is recognizing that it should
- handle the request, but is not successful at getting Tomcat to service
- the request.
+ If these are set correctly, the ISAPI redirector should recognize that
+ it should handle requests for the "/examples" context.</li>
+ <li>If the last line contains something like: <tt>GET
"/jakarta/isapi_redirect.dll
+ HTTP1.1"</tt>, then the ISAPI redirector is recognizing that it should
+ handle the request, but is not successful at getting Tomcat to service
+ the request.
<ol>
- <li>If the number following <tt>GET "/..."</tt> is 404, check
- the following:
+ <li>If the number following <tt>GET "/..."</tt> is 404, check
+ the following:
<ol type="a">
<li>Make sure you entered the URL correctly.</li>
- <li>Make sure the virtual directory created was called
"jakarta".
- It should display in Personal Web Manager as "/jakarta"
+ <li>Make sure the virtual directory created was called
"jakarta".
+ It should display in Personal Web Manager as "/jakarta"
(without the quotes).</li>
- <li>Make sure the <tt>extension_uri</tt> data begins with
- "/jakarta/" (without the quotes).</li>
- </ol></li>
- <li>If the number following <tt>GET "/..."</tt> is 500, check
- the following:
+ <li>Make sure the <tt>extension_uri</tt> data begins with
"/jakarta/"
+ (without the quotes).</li>
+ </ol>
+ </li>
+ <li>If the number following <tt>GET "/..."</tt> is 500, check
+ the following:
<ol type="a">
- <li>Make sure that "isapi_redirect.dll" follows
- "/jakarta/" in the <tt>extension_uri</tt> setting.</li>
- <li>Check the workers.properties file and make sure the port setting
for
- <tt>worker.ajp12.port</tt> is the same as the port specified in the
server.xml
- for the "Apache AJP12 support".</li>
+ <li>Make sure that "isapi_redirect.dll" follows
"/jakarta/"
+ in the <tt>extension_uri</tt> setting.</li>
+ <li>Check the workers.properties file and make sure the port setting
+ for <tt>workers used </tt> is the same as the port specified in
+ the server.xml for the ajp13 or ajp12 connectors, normally this
+ ports are 8007 for ajp12 and 8009 for ajp13.</li>
</ol>
- </li>
- <li>If the number following <tt>GET "/..."</tt> is 200 or 403,
- make sure you have checked Execute Access for the jakarta virtual
+ </li>
+ <li>If the number following <tt>GET "/..."</tt> is 200 or
+ 403, make sure you have checked Execute Access for the jakarta virtual
directory in the Advanced Options of the Personal Web Manager.</li>
</ol>
</ol>
- If the above settings are correct, the index.html page should appear in your
- browser. You should also be able to click the <b>Execute</b> links to
- execute the JSP examples.</li>
+ If the above settings are correct, the index.html page should appear in your
+ browser. You should also be able to click the <b>Execute</b> links to execute
+ the JSP examples.</li>
</ol>
<h3>WinNT</h3>
@@ -418,9 +424,10 @@
<ol type="a">
<li>Make sure the virtual directory created was called
"jakarta".</li>
<li>Make sure that the <tt>extension_uri</tt> setting is correct.</li>
- <li>Check the workers.properties file and make sure the port setting
for
- <tt>worker.ajp12.port</tt> is the same as the port specified in the
server.xml
- for the "Apache AJP12 support".</li>
+ <li>Check the workers.properties file and make sure the port setting
+ for <tt>workers used </tt> is the same as the port specified in
+ the server.xml for the ajp13 or ajp12 connectors, normally this
+ ports are 8007 for ajp12 and 8009 for ajp13.</li>
</ol>
</li>
<li>If the number following <tt>GET "/..."</tt> is 200 or 403,
