tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From lar...@apache.org
Subject cvs commit: jakarta-tomcat/src/doc mod_jk-howto.html
Date Thu, 02 Aug 2001 10:34:08 GMT
larryi      01/08/02 03:34:08

  Modified:    src/doc  mod_jk-howto.html
  Log:
  Updated to better match current ApacheConfig behavior.
  
  Revision  Changes    Path
  1.11      +53 -45    jakarta-tomcat/src/doc/mod_jk-howto.html
  
  Index: mod_jk-howto.html
  ===================================================================
  RCS file: /home/cvs/jakarta-tomcat/src/doc/mod_jk-howto.html,v
  retrieving revision 1.10
  retrieving revision 1.11
  diff -u -r1.10 -r1.11
  --- mod_jk-howto.html	2001/07/24 06:25:36	1.10
  +++ mod_jk-howto.html	2001/08/02 10:34:08	1.11
  @@ -2,7 +2,6 @@
   <html>
   <head>
      <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
  -   <meta name="GENERATOR" content="Mozilla/4.77 [en] (X11; U; Linux 2.2.19-6.2.7 i686)
[Netscape]">
      <title>Working with mod_jk</title>
   <!-- $Id  $ -->
   <!-- Copyright 2001, Apache Software Foundation -->
  @@ -291,9 +290,10 @@
   
   <p><br><span><tt>MSDEV mod_jk.dsp /MAKE ALL</tt></span>
   <p>If msdev is not in your path, enter the full path to msdev.exe. Also,
  -ApacheCore.lib is expected to exist in the APACHE1_HOME\src\CoreD and APACHE1_HOME\src\CoreR
  +ApacheCore.lib is expected to exist in the APACHE1_HOME\src\Debug or APACHE1_HOME\src\Release
  +(or the older APACHE1_HOME\src\CoreD or APACHE1_HOME\src\CoreR)
   directories before linking will succeed. You will need to build enough
  -of the Apache source to create these libraries.
  +of the Apache source to create the required librarie(s).
   <li>
   Copy mod_jk.dll to Apache's modules directory.</li>
   </ol>
  @@ -462,10 +462,10 @@
   is to turn on the Apache auto-configure setting in Tomcat and put the following
   include directive at the end of your Apache httpd.conf file (make sure
   you replace TOMCAT_HOME with the correct path for your Tomcat installation:
  -<p><tt>Include TOMCAT_HOME/conf/jk/mod_jk.conf-auto</tt>
  +<p><tt>Include TOMCAT_HOME/conf/auto/mod_jk.conf</tt>
   <p>Example:
  -<p><tt>Include /usr/local/jakarta-tomcat/conf/jk/mod_jk.conf-auto</tt>
  -<p>This will tell Apache to use directives in the mod_jk.conf-auto file
  +<p><tt>Include /usr/local/jakarta-tomcat/conf/auto/mod_jk.conf</tt>
  +<p>This will tell Apache to use directives in the mod_jk.conf file
   in the Apache configuration.&nbsp; This file is created by enabling the
   Apache auto-configuration as described in the configuring Tomcat section
   below [<a href="#s8">Configuring Tomcat</a>].
  @@ -473,8 +473,8 @@
   skip the rest of this section and continue with the <a href="#s8">Configuring
   Tomcat</a> section.</b>
   <p>Custom configurations can be created by enabling the auto-configuration
  -and copying the <tt>TOMCAT_HOME/conf/jk/mod_jk.conf-auto</tt> file to your
  -own configuration file, such as <tt>TOMCAT_HOME/conf/jk/mod_jk.conf-local</tt>.
  +and copying the <tt>TOMCAT_HOME/conf/auto/mod_jk.conf</tt> file to your
  +own configuration file, such as <tt>TOMCAT_HOME/conf/jk/mod_jk.conf</tt>.
   <p>The basic configuration is as follows:
   <ul>
   <li>
  @@ -489,7 +489,8 @@
   You should specify a location where mod_jk is going to place its log file
   and a log level to be used. Use the <tt>JkLogFile</tt> and <tt>JkLogLevel</tt>
   configuration directives. Possible log levels are <i>debug</i>, <i>info</i>,
  -<i>error</i> and <i>emerg</i>, but <i>info</i> should
be your default selection.</li>
  +<i>error</i> and <i>emerg</i>.  If the JkLogLevel is not specified,
  +no log is generated.</li>
   
   <li>
   The directive <tt>JkLogStampFormat</tt> will configure the date/time format
  @@ -512,7 +513,7 @@
   <a NAME="s73"></a>Assigning URLs to Tomcat</h3>
   
   <div class=subsection>If you have created a custom or local version of
  -<tt>mod_jk.conf-local</tt> as noted above, you can change settings such
  +<tt>mod_jk.conf</tt> as noted above, you can change settings such
   as the workers or URL prefix.
   <p>Use mod_jk's JkMount directive to assign specific URLs to Tomcat. In
   general the structure of a JkMount directive is:
  @@ -540,7 +541,7 @@
   Apache configuration. You can configure Tomcat so that when it starts up
   it will automatically generate a configuration file for Apache to use mod_jk.
   Most of the time you don't need to do anything but include this file (appending
  -<tt>"Include TOMCAT_HOME/conf/jk/mod_jk.conf-auto"</tt>) in your httpd.conf,
  +<tt>"Include TOMCAT_HOME/conf/auto/mod_jk.conf"</tt>) in your httpd.conf,
   as shown in the previous section (<a href="#s7">Configuring Apache</a>).
   <p>To configure Tomcat to generate the Apache auto-configuration add the
   following block to your <tt>TOMCAT_HOME/conf/server.xml</tt> file after
  @@ -554,19 +555,19 @@
   Older versions of Tomcat create the auto-config file without a directive
   in server.xml.&nbsp; The new directive in Tomcat 3.3 allows for additional
   configuration options as detailed later in this section.&nbsp; For older
  -versions of Tomcat, refere to the documentation that came with that version.
  +versions of Tomcat, refer to the documentation that came with that version.
   <p>If you have special needs, for example mounting URL prefixes that are
   not the default, you can use this file as a base for your customized configuration
   and save the results in another file. If you manage the Apache configuration
   yourself you'll need to update it whenever you add a new context.
   <p>Note that you must restart tomcat and apache after adding a new context;
   Apache doesn't support configuration changes without a restart. Also the
  -file <tt>TOMCAT_HOME/conf/jk/mod_jk.conf-auto</tt> is generated when tomcat
  +file <tt>TOMCAT_HOME/conf/auto/mod_jk.conf</tt> is generated when tomcat
   starts, so you'll need to start Tomcat before Apache. Tomcat will overwrite
  -<tt>TOMCAT_HOME/conf/jk/mod_jk.conf-auto</tt> each startup so customized
  +<tt>TOMCAT_HOME/conf/auto/mod_jk.conf</tt> each startup so customized
   configuration should be kept elsewhere.&nbsp; For example, copy 
  -<tt>TOMCAT_HOME/conf/jk/mod_jk.conf-auto</tt>
  -to <tt>TOMCAT_HOME/conf/jk/mod_jk.conf-local
  +<tt>TOMCAT_HOME/conf/auto/mod_jk.conf</tt>
  +to <tt>TOMCAT_HOME/conf/jk/mod_jk.conf
   </tt>before making changes.&nbsp;
   You'll need to startup Tomcat once to generate this file with your configuration
   for the first time.
  @@ -582,35 +583,42 @@
   </blockquote>
   &nbsp;where <i>options</i> can include any of the following attributes:
   <ul>
  -<li>
  -<b>confighome</b> - default parent directory for the following paths. If
  -not set, this defaults to TOMCAT_HOME. Ignored whenever any of the following
  -paths is absolute.</li>
  -
  -<li>
  -<b>jservconfig</b> - path to write apache jserv conf file to. If not set,
  -defaults to "conf/jserv/tomcat-apache.conf".</li>
  -
  -<li>
  -<b>jkconfig</b> - path to write apacke mod_jk conf file to. If not set,
  -defaults to "conf/jk/mod_jk.conf".</li>
  -
  -<li>
  -<b>workersconfig</b> - path to workers.properties file used by mod_jk.
  -If not set, defaults to "conf/jk/workers.properties".</li>
  -
  -<li>
  -<b>modjserv</b> - path to Apache JServ plugin module file. If not set,
  -defaults to "modules/ApacheModuleJServ.dll" on windows, "modules/Jserv.nlm"
  -on netware, and "libexec/mod_jserv.so" everywhere else.</li>
  -
  -<li>
  -<b>modjk</b> - path to Apache mod_jk plugin file. If not set, defaults
  -to "modules/mod_jk.dll" on windows, "modules/mod_jk.nlm" on netware, and
  -"libexec/mod_jk.so" everywhere else.</li>
  -
  -<li>
  -<b>jklog</b> - path to log file to be used by mod_jk.</li>
  +<li><b>configHome</b> - default parent directory for the following paths.
  +    If not set, this defaults to TOMCAT_HOME. Ignored
  +    whenever any of the following paths is absolute.</li>
  +<li><b>jkConfig</b> - path to use for writing Apache mod_jk conf file.
If
  +    not set, defaults to "conf/jk/mod_jk.conf".</li>
  +<li><b>workersConfig</b> - path to workers.properties file used by 
  +    mod_jk. If not set, defaults to "conf/jk/workers.properties".</li>
  +<li><b>modJk</b> - path to Apache mod_jk plugin file.  If not set,
  +    defaults to "modules/mod_jk.dll" on windows,
  +    "modules/mod_jk.nlm" on netware, and
  +    "libexec/mod_jk.so" everywhere else.</li>
  +<li><b>jkLog</b> - path to log file to be used by mod_jk.</li>
  +<li><b>jkDebug</b> - JK Loglevel setting.  May be debug, info, error,
or emerg.
  +    If not set, defaults to no log.</li>
  +<li><b>jkProtocol</b> The desired protocal, "ajp12" or "ajp13". If not
  +    specified, defaults to "ajp13" if an Ajp13Interceptor
  +    is in use, otherwise it defaults to "ajp12".</li>
  +<li><b>forwardAll</b> - If true, forward all requests to Tomcat.
  +    This helps insure that all the behavior configured in the web.xml
  +    file functions correctly. If false, let Apache serve static resources.
  +    The default is true. Warning: When false, some configuration in
  +    the web.xml may not be duplicated in Apache.
  +    Review the mod_jk conf file to see what
  +    configuration is actually being set in Apache.</li>
  +<li><b>noRoot</b> - If true, the root context is not mapped to
  +    Tomcat.  If false and forwardAll is true, all requests
  +    to the root context are mapped to Tomcat. If false and
  +    forwardAll is false, only JSP and servlets requests to
  +    the root context are mapped to Tomcat. When false,
  +    to correctly serve Tomcat's root context you must also
  +    modify the DocumentRoot setting in Apache's httpd.conf
  +    file to point to Tomcat's root context directory.
  +    Otherwise some content, such as Apache's index.html,
  +    will be served by Apache before mod_jk gets a chance
  +    to claim the request and pass it to Tomcat.
  +    The default is true.</li>
   </ul>
   &nbsp;Example:
   <blockquote>
  
  
  

Mime
View raw message