Return-Path: Delivered-To: apmail-jakarta-tomcat-dev-archive@jakarta.apache.org Received: (qmail 14563 invoked by uid 500); 14 Mar 2001 07:31:43 -0000 Mailing-List: contact tomcat-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: tomcat-dev@jakarta.apache.org Delivered-To: mailing list tomcat-dev@jakarta.apache.org Received: (qmail 14554 invoked by uid 500); 14 Mar 2001 07:31:42 -0000 Delivered-To: apmail-jakarta-tomcat-cvs@apache.org Date: 14 Mar 2001 07:31:42 -0000 Message-ID: <20010314073142.14550.qmail@apache.org> From: larryi@apache.org To: jakarta-tomcat-cvs@apache.org Subject: cvs commit: jakarta-tomcat/src/doc mod_jk-howto.html larryi 01/03/13 23:31:42 Modified: src/doc mod_jk-howto.html Log: Updates for changes in location of config file and document need for to be added to server.xml. Submitted by: Mike Braden Revision Changes Path 1.5 +57 -16 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.4 retrieving revision 1.5 diff -u -r1.4 -r1.5 --- mod_jk-howto.html 2000/10/11 19:11:54 1.4 +++ mod_jk-howto.html 2001/03/14 07:31:42 1.5 @@ -308,12 +308,21 @@

Quick start?

-In most of simple cases Tomcat can generate the needed Apache configuration. -When Tomcat starts up it will automatically generate -a configuration file for Apache in TOMCAT_HOME/conf/mod_jk.conf-auto. +In most simple cases Tomcat can generate the needed Apache configuration. You +can configure Tomcat so that when it starts up it will automatically generate +a configuration file for Apache. Most of the time you don't need to do anything but -include this file (appending "Include TOMCAT_HOME/conf/mod_jk.conf-auto") -in your httpd.conf. That's it, you can +include this file (appending "Include TOMCAT_HOME/conf/jk/mod_jk.conf-auto") +in your httpd.conf. To configure Tomcat to generate the Apache +auto-configuration:

+

+Add the following block to your TOMCAT_HOME/conf/server.xml file after <AutoWebApp ... />. +

+
  +<ApacheConfig />
  +
+

+That's it, you can now start Tomcat and Apache and access Tomcat from the Apache server.

@@ -323,23 +332,55 @@ the Apache configuration yourself you'll need to update it whenever you add a new context.

-

Tomcat 3.2: you must restart tomcat and apache after adding a new +

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 TOMCAT_HOME/conf/mod_jk.conf-auto is generated when +the file TOMCAT_HOME/conf/jk/mod_jk.conf-auto is generated when tomcat starts, so you'll need to start Tomcat before Apache. Tomcat will -overwrite TOMCAT_HOME/conf/mod_jk.conf-auto each startup so -customized configuration should be kept elsewhere.

-

Tomcat 3.3: The default location of mod_jk.conf and -mod_jk.conf-auto has changed. They are now in -TOMCAT_HOME/conf/jk/mod_jk.conf and -TOMCAT_HOME/conf/jk/mod_jk.conf-auto. +overwrite TOMCAT_HOME/conf/jk/mod_jk.conf-auto each startup so +a customized configuration should be kept elsewhere.  For example, copy  +TOMCAT_HOME/conf/jk/mod_jk.conf-auto to TOMCAT_HOME/conf/jk/mod_jk.conf-local +before making changes.  You'll need to startup Tomcat once to generate +this file with your configuration for the first time. +

+

It is also possible to specify the location of the auto generated files by +setting options in the <ApacheConfig /> block.  The following details +the syntax:

+
  +< ContextManager ... >
  +  ...
  +  <ApacheConfig options />
  +  ...
  +< /ContextManager >
  +
+

+ where options can include any of the following attributes: +

+
    +
  • confighome - default parent directory for the following paths. If + not set, this defaults to TOMCAT_HOME. Ignored whenever any of the following + paths is absolute. +
  • jservconfig - path to write apache jserv conf file to. If not set, + defaults to "conf/jserv/tomcat-apache.conf". +
  • jkconfig - path to write apacke mod_jk conf file to. If not set, + defaults to "conf/jk/mod_jk.conf". +
  • workersconfig - path to workers.properties file used by mod_jk. If + not set, defaults to "conf/jk/workers.properties". +
  • modjserv - 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. +
  • modjk - 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. +
  • jklog - path to log file to be used by mod_jk.
  • +

Configuring workers manually.

-Workers are configured using the file TOMCAT_HOME/conf/workers.properties. +Workers are configured using the file TOMCAT_HOME/conf/jk/workers.properties. There is a great deal of information in the workers.properties howto document, and you should really look at that first. If you're in a hurry however, you can probably get away @@ -368,7 +409,7 @@

   LoadModule    jk_module  libexec/mod_jk.so
   AddModule     mod_jk.c
  -JkWorkersFile /usr/local/jakarta-tomcat/conf/workers.properties
  +JkWorkersFile /usr/local/jakarta-tomcat/conf/jk/workers.properties
   JkLogFile     /usr/local/apache/logs/mod_jk.log
   JkLogLevel    warn
   
@@ -464,7 +505,7 @@ # Configure mod_jk # -JkWorkersFile /usr/local/jakarta-tomcat/conf/workers.properties +JkWorkersFile /usr/local/jakarta-tomcat/conf/jk/workers.properties JkLogFile /usr/local/apache/logs/mod_jk.log JkLogLevel warn --------------------------------------------------------------------- To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org For additional commands, email: tomcat-dev-help@jakarta.apache.org