remm        02/01/31 10:45:14

  Modified:    webapps/tomcat-docs/config jk.xml
  Log:
  - Remove a few confusing statements, and reorganize a bit.
  
  Revision  Changes    Path
  1.3       +64 -61    jakarta-tomcat-4.0/webapps/tomcat-docs/config/jk.xml
  
  Index: jk.xml
  ===================================================================
  RCS file: /home/cvs/jakarta-tomcat-4.0/webapps/tomcat-docs/config/jk.xml,v
  retrieving revision 1.2
  retrieving revision 1.3
  diff -u -r1.2 -r1.3
  --- jk.xml    27 Jan 2002 11:52:11 -0000      1.2
  +++ jk.xml    31 Jan 2002 18:45:14 -0000      1.3
  @@ -18,16 +18,15 @@
   
     <p>The <strong>JK Connector</strong> element represents a
     <strong>Connector</strong> component that communicates with a web
  -  connector via the <code>AJP</code> protocol.  This is used for cases
  -  where you wish to invisibly integrate Tomcat 4 into an existing (or new)
  -  Apache installation, and you want Apache to handle the static content
  -  contained in the web application, and/or utilize Apache's SSL
  -  processing.  In many application environments, this will result in
  -  better overall performance than running your applications under
  +  connector via the <code>JK</code> protocol (also known as the AJP protocol).
  +  This is used for cases where you wish to invisibly integrate Tomcat 4 into 
  +  an existing (or new) Apache installation, and you want Apache to handle 
  +  the static content contained in the web application, and/or utilize 
  +  Apache's SSL processing.  In many application environments, this will 
  +  result in better overall performance than running your applications under
     Tomcat stand-alone using the <a href="http11.html">HTTP/1.1 Connector</a>.  
     However, the only way to know for sure whether it will provide better 
  -  performance for <strong>your</strong> application is to try it both 
  -  ways.</p>
  +  performance for <strong>your</strong> application is to try it both ways.</p>
   
     <p>This connector supports load balancing when used in conjunction with
     the <code>jvmRoute</code> attribute of the 
  @@ -92,7 +91,7 @@
     <p>The standard implementation of <strong>JK Connector</strong> is
     <strong>org.apache.ajp.tomcat4.Ajp13Connector</strong>.</p>
   
  -  <p><strong>This implementation supports the AJP 1.3 and 1.4 
protocols.</strong></p>
  +  <p><strong>This implementation supports the JK 1.3 and 1.4 protocols (also known 
as AJP 1.3 and 1.4).</strong></p>
   
     <p>It supports the following additional attributes (in addition to the
     common attributes listed above):</p>
  @@ -266,10 +265,11 @@
              The mod_jserv configuration directives are not compatible 
              with mod_jk!</p>
   
  -           <p>Unlike Tomcat 3, Tomcat 4 doesn't automatically generate the 
  +           <p>Like Tomcat 3, Tomcat 4 can automatically generate the 
              necessary <code>$CATALINA_HOME/conf/mod_jk.conf</code>,
  -           and it will have to be created manually. Note that Tomcat 
  -           and Apache must be restarted after adding a new context.</p>
  +           but it can also be created manually. Note that Tomcat 
  +           and Apache must be restarted after adding a new context.
  +           See the "Using ApacheConfig" section for more details.</p>
   
              <p>The basic configuration is as follows:</p>
   
  @@ -300,8 +300,8 @@
           <subsection name="Configuring Tomcat">
   
              <p>Tomcat 4 can be configured to automatically generate the Apache 
  -           configuration file.  The next section describes how to enable
  -           this option.</p>
  +          configuration file.  The next section describes how to enable
  +          this option.</p>
   
              <p>After enabling the AJP 1.3 connector, you need to define workers,
              using a <code>$CATALINA_HOME/conf/workers.properties</code> file.
  @@ -526,9 +526,9 @@
           <a 
href="http://jakarta.apache.org/builds/jakarta-tomcat/release/v3.3/bin/win32/i386/";>link</a>.
           </p>
   
  -        <p>Note: See below for examples of the configuration files. Those 
  -        configuration files assume Tomcat is installed in the 
  -        <code>c:\jakarta-tomcat-4.0.1</code> directory.</p>
  +        <p>You can then either manually define a few extra configuration files
  +        (read below), or use the automatic IISConfig to have Tomcat generate 
  +        them for you (see next section).</p>
   
           <p>The next step is to create worker.properties to help 
           isapi_redirect.dll to identify where to find Tomcat and its 
  @@ -540,47 +540,9 @@
           <p>Then the <code>uriworkermap.properties</code> file must be created
           in <code>%CATALINA_HOME%\conf</code> directory.</p>
   
  -     </subsection>
  -
  -     <subsection name="Configuring IIS">
  -
  -        <p>
  -        <ul>
  -           <li>Launch Internet Service Manager</li>
  -           <li>Stop the Web Site if it is running</li>
  -           <li>Create a virtual directory, by clicking on the default 
  -               web site
  -              <ul>
  -                 <li>Type the alias to say jakarta, press Next</li>
  -                 <li>Set the directory to <code>%CATALINA_HOME%\bin</code>
  -                     where you installed isapi_redirect.dll, press next</li>
  -                 <li>Provide only read and execute privileges for 
  -                     security purposes</li>
  -              </ul>
  -           </li>
  -           <li>Add a filter to the default web site, using the 
  -           IIS Management Console, right click on the properties and 
  -           go to ISAPI filters tab. Press Add button, 
  -           add isapi_redirect.dll as a filter the name of the filter 
  -           should reflect its task (for example, "Jakarta Redirector"). 
  -           The Executable field should point to the place where we installed 
  -           isapi_redirect.dll, in our case 
  -           <code>%CATALINA_HOME%\bin\isapi_redirect.dll</code></li>
  -           <li>Copy and paste the registry entries found below into a file 
  -           iis_redirect.reg. Remember to correct the 
  -           directories where Tomcat is installed in this file. 
  -           Run the iis_redirect.reg file found at the end of this document. 
  -           This will create entries in the registry which 
  -           the isapi_redirect.dll looks for to determine the configuration 
  -           and location of Tomcat.</li>
  -           <li>Startup IIS.</li>
  -           <li>Go to the Properties of the web site and select the ISAPI 
  -           filters tab to make sure that the ISAPI filter got registered 
  -           correctly. It should have a Green arrow alongside it. 
  -           Note: it is recommended to restart computer for the ISAPI filter 
  -           to load.</li>
  -        </ul>
  -        </p>
  +        <p>Note: See below for examples of the configuration files. Those 
  +        configuration files assume Tomcat is installed in the 
  +        <code>c:\jakarta-tomcat-4.0.1</code> directory.</p>
   
        </subsection>
   
  @@ -590,9 +552,9 @@
             the automatic generation of the IIS configuration file.  
             However, this comes at the cost of a bit more complexity.  Each
             time that Tomcat is started, it will write the configuration file
  -          to <code>%CATALINA_HOME%/conf/auto/uriworkers.properties</code>. If
  -          enabled as a <code>Server</code> Listener, it will also write the
  -          required registry entries to 
  +          to <code>%CATALINA_HOME%/conf/auto/uriworkersmap.properties</code>.
  +             If enabled as a <code>Server</code> Listener, it will also write 
  +             the required registry entries to 
             <code>%CATALINA_HOME%/conf/auto/iis_redirect.reg</code>. You may
             enter the settings into the registry by double-clicking on this
             file from the Windows Explorer.</p>
  @@ -695,6 +657,47 @@
          </attribute>
   
         </attributes>
  +
  +     </subsection>
  +
  +     <subsection name="Configuring IIS">
  +
  +        <p>
  +        <ul>
  +           <li>Launch Internet Service Manager</li>
  +           <li>Stop the Web Site if it is running</li>
  +           <li>Create a virtual directory, by clicking on the default 
  +               web site
  +              <ul>
  +                 <li>Type the alias to say jakarta, press Next</li>
  +                 <li>Set the directory to <code>%CATALINA_HOME%\bin</code>
  +                     where you installed isapi_redirect.dll, press next</li>
  +                 <li>Provide only read and execute privileges for 
  +                     security purposes</li>
  +              </ul>
  +           </li>
  +           <li>Add a filter to the default web site, using the 
  +           IIS Management Console, right click on the properties and 
  +           go to ISAPI filters tab. Press Add button, 
  +           add isapi_redirect.dll as a filter the name of the filter 
  +           should reflect its task (for example, "Jakarta Redirector"). 
  +           The Executable field should point to the place where we installed 
  +           isapi_redirect.dll, in our case 
  +           <code>%CATALINA_HOME%\bin\isapi_redirect.dll</code></li>
  +           <li>If not done yet, enter the keys from 
  +           <code>iis_redirect.reg</code> in the Windows registry (this can
  +           be done by double-clicking on the file in the explorer).
  +           Note: When manually creating the file (maybe from the example given
  +           below), remember to correct the directories where Tomcat 
  +           is installed.</li>
  +           <li>Startup IIS.</li>
  +           <li>Go to the Properties of the web site and select the ISAPI 
  +           filters tab to make sure that the ISAPI filter got registered 
  +           correctly. It should have a Green arrow alongside it. 
  +           Note: it is recommended to restart computer for the ISAPI filter 
  +           to load.</li>
  +        </ul>
  +        </p>
   
        </subsection>
   
  
  
  

--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to