cvs commit: jakarta-tomcat-4.0/webapps/tomcat-docs/config ajp.xml
glenn 02/04/09 06:29:10 Modified:webapps/tomcat-docs/config Tag: tomcat_40_branch ajp.xml Log: Add a note about 1 to 1 httpd to processor mapping with Apache Revision ChangesPath No revision No revision 1.2.2.8 +4 -0 jakarta-tomcat-4.0/webapps/tomcat-docs/config/Attic/ajp.xml Index: ajp.xml === RCS file: /home/cvs/jakarta-tomcat-4.0/webapps/tomcat-docs/config/Attic/ajp.xml,v retrieving revision 1.2.2.7 retrieving revision 1.2.2.8 diff -u -r1.2.2.7 -r1.2.2.8 --- ajp.xml 27 Feb 2002 03:43:55 - 1.2.2.7 +++ ajp.xml 9 Apr 2002 13:29:10 - 1.2.2.8 @@ -123,6 +123,10 @@ by this strongConnector/strong, which therefore determines the maximum number of simultaneous requests that can be handled. If not specified, this attribute is set to 20./p + pbNOTE:/bFor Apache 1.3 on Unix there is a 1 to 1 mapping + between httpd processes and Ajp13Processors. You must configure + maxProcessors to be greater than or equal to the maximum number + of httpd processes your Apache web server spawns./p /attribute attribute name=minProcessors required=false -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
cvs commit: jakarta-tomcat-4.0/webapps/tomcat-docs/config ajp.xml
remm02/02/26 19:43:55 Modified:webapps/tomcat-docs/config Tag: tomcat_40_branch ajp.xml Log: - Document address attribute (bug 6327). Revision ChangesPath No revision No revision 1.2.2.7 +7 -0 jakarta-tomcat-4.0/webapps/tomcat-docs/config/Attic/ajp.xml Index: ajp.xml === RCS file: /home/cvs/jakarta-tomcat-4.0/webapps/tomcat-docs/config/Attic/ajp.xml,v retrieving revision 1.2.2.6 retrieving revision 1.2.2.7 diff -u -r1.2.2.6 -r1.2.2.7 --- ajp.xml 20 Feb 2002 02:40:22 - 1.2.2.6 +++ ajp.xml 27 Feb 2002 03:43:55 - 1.2.2.7 @@ -105,6 +105,13 @@ value is 10./p /attribute +attribute name=address required=false + pFor servers with more than one IP address, this attribute + specifies which address will be used for listening on the specified + port. By default, this port will be used on all IP addresses + associated with the server./p +/attribute + attribute name=debug required=false pThe debugging detail level of log messages generated by this component, with higher numbers creating more detailed output. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
cvs commit: jakarta-tomcat-4.0/webapps/tomcat-docs/config ajp.xml
remm02/02/19 18:40:22 Modified:webapps/tomcat-docs/config Tag: tomcat_40_branch ajp.xml Log: - Add documentation on the 'tomcatAuthentication' flag. Revision ChangesPath No revision No revision 1.2.2.6 +10 -0 jakarta-tomcat-4.0/webapps/tomcat-docs/config/Attic/ajp.xml Index: ajp.xml === RCS file: /home/cvs/jakarta-tomcat-4.0/webapps/tomcat-docs/config/Attic/ajp.xml,v retrieving revision 1.2.2.5 retrieving revision 1.2.2.6 diff -u -r1.2.2.5 -r1.2.2.6 --- ajp.xml 30 Jan 2002 17:32:10 - 1.2.2.5 +++ ajp.xml 20 Feb 2002 02:40:22 - 1.2.2.6 @@ -132,6 +132,16 @@ to a particular port number on a particular IP address./p /attribute +attribute name=tomcatAuthentication required=false + pThis flag, which value defaults to codetrue/code, indicates + whether or not authentication will be handled by Tomcat or the native + web server. If the attribute value is codetrue/code, any pricipal + authenticated by the native web server will be ignored, and Tomcat will + take care of the authentication. If the attribute value + is codefalse/code, Tomcat will not attempt to authenticate + a principal if the native web server has already authenticated one./p +/attribute + /attributes /subsection -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
cvs commit: jakarta-tomcat-4.0/webapps/tomcat-docs/config ajp.xml
remm02/01/30 09:32:11 Modified:webapps/tomcat-docs/config Tag: tomcat_40_branch ajp.xml Log: - Remove a few confusing statements, and reorganize a bit. Revision ChangesPath No revision No revision 1.2.2.5 +56 -50jakarta-tomcat-4.0/webapps/tomcat-docs/config/Attic/ajp.xml Index: ajp.xml === RCS file: /home/cvs/jakarta-tomcat-4.0/webapps/tomcat-docs/config/Attic/ajp.xml,v retrieving revision 1.2.2.4 retrieving revision 1.2.2.5 diff -u -r1.2.2.4 -r1.2.2.5 --- ajp.xml 27 Jan 2002 04:15:05 - 1.2.2.4 +++ ajp.xml 30 Jan 2002 17:32:10 - 1.2.2.5 @@ -265,10 +265,11 @@ The mod_jserv configuration directives are not compatible with mod_jk!/p - pUnlike Tomcat 3, Tomcat 4 doesn't automatically generate the + pLike 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 pThe basic configuration is as follows:/p @@ -504,9 +505,9 @@ a href=http://jakarta.apache.org/builds/jakarta-tomcat/release/v3.3/bin/win32/i386/;link/a. /p -pNote: See below for examples of the configuration files. Those -configuration files assume Tomcat is installed in the -codec:\jakarta-tomcat-4.0.1/code directory./p +pYou 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 pThe next step is to create worker.properties to help isapi_redirect.dll to identify where to find Tomcat and its @@ -518,57 +519,20 @@ pThen the codeuriworkermap.properties/code file must be created in code%CATALINA_HOME%\conf/code directory./p - /subsection - - subsection name=Configuring IIS - -p -ul - liLaunch Internet Service Manager/li - liStop the Web Site if it is running/li - liCreate a virtual directory, by clicking on the default - web site - ul - liType the alias to say jakarta, press Next/li - liSet the directory to code%CATALINA_HOME%\bin/code - where you installed isapi_redirect.dll, press next/li - liProvide only read and execute privileges for - security purposes/li - /ul - /li - liAdd 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 - liCopy 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 - liStartup IIS./li - liGo 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 +pNote: See below for examples of the configuration files. Those +configuration files assume Tomcat is installed in the +codec:\jakarta-tomcat-4.0.1/code directory./p /subsection + subsection name=Using IISConfig pTomcat 4 provides extra flexability over Tomcat 3 in setting up 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
cvs commit: jakarta-tomcat-4.0/webapps/tomcat-docs/config ajp.xml
billbarker02/01/26 20:15:05 Modified:webapps/tomcat-docs/config Tag: tomcat_40_branch ajp.xml Log: Adding documentation for ApacheConfig and IISConfig. Revision ChangesPath No revision No revision 1.2.2.4 +190 -3jakarta-tomcat-4.0/webapps/tomcat-docs/config/Attic/ajp.xml Index: ajp.xml === RCS file: /home/cvs/jakarta-tomcat-4.0/webapps/tomcat-docs/config/Attic/ajp.xml,v retrieving revision 1.2.2.3 retrieving revision 1.2.2.4 diff -u -r1.2.2.3 -r1.2.2.4 --- ajp.xml 25 Jan 2002 14:54:37 - 1.2.2.3 +++ ajp.xml 27 Jan 2002 04:15:05 - 1.2.2.4 @@ -298,8 +298,9 @@ subsection name=Configuring Tomcat - pTomcat 4 won't automatically generate the Apache configuration - file at the moment./p + pTomcat 4 can be configured to automatically generate the Apache + configuration file. The next section describes how to enable + this option./p pAfter enabling the AJP 1.3 connector, you need to define workers, using a code$CATALINA_HOME/conf/workers.properties/code file. @@ -309,6 +310,100 @@ /subsection + subsection name=Using ApacheConfig + pTomcat 4 provides extra flexability over Tomcat 3 in setting up + the automatic generation of the Apache 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/mod_jk.conf/code. You can + then either + sourceInclude $CATALINA_HOME/conf/auto/mod_jk.conf/source + in your codehttpd.conf/code file./p + pTo generate the global Apache directives (e.g. + codeLoadModule/code, codeJkLogFile/code), you define a + codeServer/code Listener:/p +source + lt;Server port=8005 shutdown=SHUTDOWN debug=0gt; + lt;Listener className=org.apache.ajp.tomcat4.config.ApacheConfig /gt; + ... +/source + pTo configure the individual context information, you then either + define a codeHost/code Listener or a codeContext/code + Listener depending on if you are using virutal hosting or not. + Defining a codeHost/code Listener will generate the Apache + codelt;VirtualHostgt;/code directive and include all of + the configurations for the codeContexts/code under this host. + Using the codeContext/code Listener allows you the flexability + to configure the codeContext/code the same way even if it + is being served from several hosts./p + pExcept for the placement of the codelt;Listener ...gt;/code, + the syntax is virtualy identical for the codeHost/code + Listener and the codeContext/code Listener. The examples that + follow will demonstrate the functionality for a codeHost/code + Listener. The simplest configuration is:/p +source +lt;Host name=localhost debug=0 appbase=webapps gt; + lt;Listener className=org.apache.ajp.tomcat4.config.ApacheConfig + append=true /gt; +/source +pIt is possible to modify the output configuration file with the +following attributes:/p + attributes + attribute name=configHome required=false + Default parent directory for the following paths. If not set, this + defaults to CATALINA_HOME. Ignored whenever any of the following + paths is absolute + /attribute + attribute name=jkConfig required=false + Path to write apacke mod_jk conf file to. If not set, defaults to + conf/auto/mod_jk.conf. + /attribute + attribute name=workersConfig required=false + Path to workers.properties file used by mod_jk. If not set, + defaults to conf/jk/workers.properties. + /attribute + attribute name=modJk required=false + 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. + /attribute + attribute name=jkLog required=false + Path to log file to be used by mod_jk + /attribute + attribute name=jkDebug required=false + JK Loglevel setting. May be debug, info, error, or emerg. If not + set, defaults to no log. + /attribute + attribute name=jkWorker required=false + The desired worker. Must be set to one of the workers defined in + the workers.properties file. ajp13 or inprocess are + the workers found in the default workers.properties file. If not
cvs commit: jakarta-tomcat-4.0/webapps/tomcat-docs/config ajp.xml engine.xml
remm02/01/25 06:54:24 Modified:webapps/tomcat-docs/config ajp.xml engine.xml Log: - Update doc on AJP. - Add the 'jvmRoute' attribute to the engine. Revision ChangesPath 1.4 +7 -2 jakarta-tomcat-4.0/webapps/tomcat-docs/config/ajp.xml Index: ajp.xml === RCS file: /home/cvs/jakarta-tomcat-4.0/webapps/tomcat-docs/config/ajp.xml,v retrieving revision 1.3 retrieving revision 1.4 diff -u -r1.3 -r1.4 --- ajp.xml 1 Dec 2001 01:12:31 - 1.3 +++ ajp.xml 25 Jan 2002 14:54:24 - 1.4 @@ -26,7 +26,12 @@ better overall performance than running your applications under Tomcat stand-alone using the a href=http11.htmlHTTP/1.1 Connector/a. However, the only way to know for sure whether it will provide better - performance for strongyour/strong application is to try it both ways./p + performance for strongyour/strong application is to try it both + ways./p + + pThis connector supports load balancing when used in conjunction with + the codejvmRoute/code attribute of the + a href=engine.htmlEngine/a./p /section @@ -87,7 +92,7 @@ pThe standard implementation of strongAJP Connector/strong is strongorg.apache.ajp.tomcat4.Ajp13Connector/strong./p - pstrongThis implementation supports the AJP 1.3 protocol./strong/p + pstrongThis implementation supports the AJP 1.3 and 1.4 protocols./strong/p pIt supports the following additional attributes (in addition to the common attributes listed above):/p 1.3 +9 -0 jakarta-tomcat-4.0/webapps/tomcat-docs/config/engine.xml Index: engine.xml === RCS file: /home/cvs/jakarta-tomcat-4.0/webapps/tomcat-docs/config/engine.xml,v retrieving revision 1.2 retrieving revision 1.3 diff -u -r1.2 -r1.3 --- engine.xml26 Sep 2001 02:29:21 - 1.2 +++ engine.xml25 Jan 2002 14:54:24 - 1.3 @@ -54,6 +54,15 @@ nested immediately inside./p /attribute + attribute name=jvmRoute required=false +pIdentifier which must be used in load balancing scenarios to enable +session affinity. The indetifier, which must be unique across all +Tomcat 4 servers which participate in the cluster, will be appended to +the generated session identifier, therefore allowing the front end +proxy to always forward a particular session to the same Tomcat 4 +instance./p + /attribute + attribute name=name required=true pLogical name of this Engine, used in log and error messages./p /attribute -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
cvs commit: jakarta-tomcat-4.0/webapps/tomcat-docs/config ajp.xml engine.xml
remm02/01/25 06:54:37 Modified:webapps/tomcat-docs/config Tag: tomcat_40_branch ajp.xml engine.xml Log: - Update doc on AJP. - Add the 'jvmRoute' attribute to the engine. Revision ChangesPath No revision No revision 1.2.2.3 +5 -1 jakarta-tomcat-4.0/webapps/tomcat-docs/config/ajp.xml Index: ajp.xml === RCS file: /home/cvs/jakarta-tomcat-4.0/webapps/tomcat-docs/config/ajp.xml,v retrieving revision 1.2.2.2 retrieving revision 1.2.2.3 diff -u -r1.2.2.2 -r1.2.2.3 --- ajp.xml 1 Dec 2001 22:16:24 - 1.2.2.2 +++ ajp.xml 25 Jan 2002 14:54:37 - 1.2.2.3 @@ -28,6 +28,10 @@ However, the only way to know for sure whether it will provide better performance for strongyour/strong application is to try it both ways./p + pThis connector supports load balancing when used in conjunction with + the codejvmRoute/code attribute of the + a href=engine.htmlEngine/a./p + /section @@ -87,7 +91,7 @@ pThe standard implementation of strongAJP Connector/strong is strongorg.apache.ajp.tomcat4.Ajp13Connector/strong./p - pstrongThis implementation supports the AJP 1.3 protocol./strong/p + pstrongThis implementation supports the AJP 1.3 and 1.4 protocols./strong/p pIt supports the following additional attributes (in addition to the common attributes listed above):/p 1.1.2.2 +9 -0 jakarta-tomcat-4.0/webapps/tomcat-docs/config/engine.xml Index: engine.xml === RCS file: /home/cvs/jakarta-tomcat-4.0/webapps/tomcat-docs/config/engine.xml,v retrieving revision 1.1.2.1 retrieving revision 1.1.2.2 diff -u -r1.1.2.1 -r1.1.2.2 --- engine.xml26 Sep 2001 02:28:07 - 1.1.2.1 +++ engine.xml25 Jan 2002 14:54:37 - 1.1.2.2 @@ -54,6 +54,15 @@ nested immediately inside./p /attribute + attribute name=jvmRoute required=false +pIdentifier which must be used in load balancing scenarios to enable +session affinity. The indetifier, which must be unique across all +Tomcat 4 servers which participate in the cluster, will be appended to +the generated session identifier, therefore allowing the front end +proxy to always forward a particular session to the same Tomcat 4 +instance./p + /attribute + attribute name=name required=true pLogical name of this Engine, used in log and error messages./p /attribute -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
cvs commit: jakarta-tomcat-4.0/webapps/tomcat-docs/config ajp.xml
remm01/12/01 14:16:24 Modified:webapps/tomcat-docs/config Tag: tomcat_40_branch ajp.xml Log: - Port the AJP docs updates. Revision ChangesPath No revision No revision 1.2.2.2 +229 -2jakarta-tomcat-4.0/webapps/tomcat-docs/config/ajp.xml Index: ajp.xml === RCS file: /home/cvs/jakarta-tomcat-4.0/webapps/tomcat-docs/config/ajp.xml,v retrieving revision 1.2.2.1 retrieving revision 1.2.2.2 diff -u -r1.2.2.1 -r1.2.2.2 --- ajp.xml 2001/11/30 07:03:04 1.2.2.1 +++ ajp.xml 2001/12/01 22:16:24 1.2.2.2 @@ -144,12 +144,239 @@ section name=Configuration HOWTOs + subsection name=Apache + + subsection name=Introduction + +pThis section explains how to connect Tomcat 4 to the popular +open source web server, Apache. It was originally part of +iTomcat: A Minimalistic User's Guide/i by Gal Shachor, but +has been split off for organizational reasons. It should be +considered a bwork in progress/b. Since the Tomcat source +tree is constantly changing, the information herein may be out +of date. The only definitive reference at this point is the a +href=http://jakarta.apache.org/site/sourceindex.html;source +code/a./p + + /subsection + + subsection name=Installation + +subsection name=Needed Components + + pIn a nutshell a web server is waiting for client HTTP requests. + When these requests arrive the server does whatever is needed to + serve the requests by providing the necessary content. Adding a + servlet container may somewhat change this behavior. Now the web + server needs also to perform the following:/p + + ul +liLoad the servlet container adapter library +and initialize it (prior to serving requests). /li +liWhen a request arrives, it needs to check and see if a certain +request belongs to a servlet, if so it needs to let the adapter +take the request and handle it./li + /ul + + pThe adapter on the other hand needs to know what requests it is + going to serve, usually based on some pattern in the request URL, + and to where to direct these requests./p + + pThings are even more complex when the user wants to set + a configuration that uses virtual hosts, or when they want multiple + developers to work on the same web server but on different servlet + container JVMs. We will cover these two cases + in the advanced sections./p + +/subsection + +subsection name=mod_jk Terminology + + pThe following terms are used in this section:/p + + ul + listrongWorker process/strong - A worker is a Tomcat + instance that is running to serve servlet requests coming + from the web server. In most cases there is only a single worker + (the one and only Tomcat process) but sometimes you will run + multiple workers to achieve load balancing or site partitioning. + Each worker is identified to the web server by the host were + it is located, the port where it listens and the communication + protocol used to exchange messages./li + listrongIn-Process Worker/strong - This is a special + worker. Instead of working with a Tomcat process residing on + another process, the web server opens a JVM and executes + Tomcat inside the web server process address space. + Our discussion in this document is not going to get into this + special worker. Note: Tomcat 4 can't be run as this type of + worker at the moment./li + listrongWeb Server Plug-in/Tomcat Redirector/strong - + For Tomcat to cooperate with any web server it needs an agent + to reside in the web server and send him servlet requests. + This is the web server plug-in, and in our case the web server + plug-in is mod_jk. The redirector usually comes in the shape of + a DLL or shared object module that you plug into + the web server./li + listrongPlug-in Configuration/strong - We need to + configure the web server plug-in so that it knows where + the different Tomcat workers are and to which of them + it should forward requests. This information, accompanied with + some internal parameter, such as the log level, comprises + the plug-in
cvs commit: jakarta-tomcat-4.0/webapps/tomcat-docs/config ajp.xml
remm01/11/30 17:12:31 Modified:webapps/tomcat-docs/config ajp.xml Log: - Merge some of the relevant documentation. Please review and expand. Revision ChangesPath 1.3 +229 -2jakarta-tomcat-4.0/webapps/tomcat-docs/config/ajp.xml Index: ajp.xml === RCS file: /home/cvs/jakarta-tomcat-4.0/webapps/tomcat-docs/config/ajp.xml,v retrieving revision 1.2 retrieving revision 1.3 diff -u -r1.2 -r1.3 --- ajp.xml 2001/11/30 06:23:13 1.2 +++ ajp.xml 2001/12/01 01:12:31 1.3 @@ -144,12 +144,239 @@ section name=Configuration HOWTOs + subsection name=Apache + + subsection name=Introduction + +pThis section explains how to connect Tomcat 4 to the popular +open source web server, Apache. It was originally part of +iTomcat: A Minimalistic User's Guide/i by Gal Shachor, but +has been split off for organizational reasons. It should be +considered a bwork in progress/b. Since the Tomcat source +tree is constantly changing, the information herein may be out +of date. The only definitive reference at this point is the a +href=http://jakarta.apache.org/site/sourceindex.html;source +code/a./p + + /subsection + + subsection name=Installation + +subsection name=Needed Components + + pIn a nutshell a web server is waiting for client HTTP requests. + When these requests arrive the server does whatever is needed to + serve the requests by providing the necessary content. Adding a + servlet container may somewhat change this behavior. Now the web + server needs also to perform the following:/p + + ul +liLoad the servlet container adapter library +and initialize it (prior to serving requests). /li +liWhen a request arrives, it needs to check and see if a certain +request belongs to a servlet, if so it needs to let the adapter +take the request and handle it./li + /ul + + pThe adapter on the other hand needs to know what requests it is + going to serve, usually based on some pattern in the request URL, + and to where to direct these requests./p + + pThings are even more complex when the user wants to set + a configuration that uses virtual hosts, or when they want multiple + developers to work on the same web server but on different servlet + container JVMs. We will cover these two cases + in the advanced sections./p + +/subsection + +subsection name=mod_jk Terminology + + pThe following terms are used in this section:/p + + ul + listrongWorker process/strong - A worker is a Tomcat + instance that is running to serve servlet requests coming + from the web server. In most cases there is only a single worker + (the one and only Tomcat process) but sometimes you will run + multiple workers to achieve load balancing or site partitioning. + Each worker is identified to the web server by the host were + it is located, the port where it listens and the communication + protocol used to exchange messages./li + listrongIn-Process Worker/strong - This is a special + worker. Instead of working with a Tomcat process residing on + another process, the web server opens a JVM and executes + Tomcat inside the web server process address space. + Our discussion in this document is not going to get into this + special worker. Note: Tomcat 4 can't be run as this type of + worker at the moment./li + listrongWeb Server Plug-in/Tomcat Redirector/strong - + For Tomcat to cooperate with any web server it needs an agent + to reside in the web server and send him servlet requests. + This is the web server plug-in, and in our case the web server + plug-in is mod_jk. The redirector usually comes in the shape of + a DLL or shared object module that you plug into + the web server./li + listrongPlug-in Configuration/strong - We need to + configure the web server plug-in so that it knows where + the different Tomcat workers are and to which of them + it should forward requests. This information, accompanied with + some internal parameter, such as the log level, comprises + the plug-in configuration./li + listrongWeb Server Configuration/strong -
cvs commit: jakarta-tomcat-4.0/webapps/tomcat-docs/config ajp.xml project.xml
remm01/11/29 18:52:08 Modified:webapps/tomcat-docs/config project.xml Added: webapps/tomcat-docs/config ajp.xml Log: - Start adding some docs on AJP support. - Add the IIS HOWTO, contributed by Rajan Gupta. Revision ChangesPath 1.5 +1 -0 jakarta-tomcat-4.0/webapps/tomcat-docs/config/project.xml Index: project.xml === RCS file: /home/cvs/jakarta-tomcat-4.0/webapps/tomcat-docs/config/project.xml,v retrieving revision 1.4 retrieving revision 1.5 diff -u -r1.4 -r1.5 --- project.xml 2001/08/25 20:06:30 1.4 +++ project.xml 2001/11/30 02:52:08 1.5 @@ -24,6 +24,7 @@ menu name=Connectors item name=HTTP/1.1 href=http11.html/ item name=Warp href=warp.html/ +item name=AJP href=ajp.html/ /menu menu name=Containers 1.1 jakarta-tomcat-4.0/webapps/tomcat-docs/config/ajp.xml Index: ajp.xml === ?xml version=1.0? !DOCTYPE document [ !ENTITY project SYSTEM project.xml ] document project; properties author email=[EMAIL PROTECTED]Remy Maucherat/author titleThe AJP Connector/title /properties body section name=Introduction pThe strongAJP Connector/strong element represents a strongConnector/strong component that communicates with a web connector via the codeAJP/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 Tomcat stand-alone using the a href=http11.htmlHTTP/1.1 Connector/a. However, the only way to know for sure whether it will provide better performance for strongyour/strong application is to try it both ways./p /section section name=Attributes subsection name=Common Attributes pAll implementations of strongConnector/strong support the following attributes:/p attributes attribute name=className required=true pJava class name of the implementation to use. This class must implement the codeorg.apache.catalina.Connector/code interface. You must specify the standard value defined below./p /attribute attribute name=enableLookups required=false pSet to codetrue/code if you want calls to coderequest.getRemoteHost()/code to perform DNS lookups in order to return the actual host name of the remote client. Set to codefalse/code to skip the DNS lookup and return the IP address in String form instead (thereby improving performance). By default, DNS lookups are enabled./p /attribute attribute name=redirectPort required=false pIf this strongConnector/strong is supporting non-SSL requests, and a request is received for which a matching codelt;security-constraintgt;/code requires SSL transport, Catalina will automatically redirect the request to the port number specified here./p /attribute attribute name=scheme required=false pSet this attribute to the name of the protocol you wish to have returned by calls to coderequest.getScheme()/code. For example, you would set this attribute to codehttps/code for an SSL Connector. The default value is codehttp/code. See a href=#SSL SupportSSL Support/a for more information./p /attribute attribute name=secure required=false pSet this attribute to codetrue/code if you wish to have calls to coderequest.isSecure()/code to return codetrue/code for requests received by this Connector (you would want this on an SSL Connector). The default value is codefalse/code./p /attribute /attributes /subsection subsection name=Standard Implementation pThe standard implementation of strongAJP Connector/strong is strongorg.apache.ajp.tomcat4.Ajp13Connector/strong./p pstrongThis implementation supports the AJP 1.3 protocol./strong/p pIt supports the following additional attributes (in addition to the common attributes listed above):/p attributes attribute name=acceptCount required=false pThe maximum queue length for incoming connection requests when all possible request processing threads are in use. Any requests received when the queue is full will be refused. The default value is 10./p /attribute attribute name=debug required=false
cvs commit: jakarta-tomcat-4.0/webapps/tomcat-docs/config ajp.xml project.xml
remm01/11/29 23:03:04 Modified:webapps/tomcat-docs/config Tag: tomcat_40_branch project.xml Added: webapps/tomcat-docs/config Tag: tomcat_40_branch ajp.xml Log: - Port the AJP documentation to the 4.0 branch. Revision ChangesPath No revision No revision 1.4.2.1 +1 -0 jakarta-tomcat-4.0/webapps/tomcat-docs/config/project.xml Index: project.xml === RCS file: /home/cvs/jakarta-tomcat-4.0/webapps/tomcat-docs/config/project.xml,v retrieving revision 1.4 retrieving revision 1.4.2.1 diff -u -r1.4 -r1.4.2.1 --- project.xml 2001/08/25 20:06:30 1.4 +++ project.xml 2001/11/30 07:03:04 1.4.2.1 @@ -24,6 +24,7 @@ menu name=Connectors item name=HTTP/1.1 href=http11.html/ item name=Warp href=warp.html/ +item name=AJP href=ajp.html/ /menu menu name=Containers No revision No revision 1.2.2.1 +0 -0 jakarta-tomcat-4.0/webapps/tomcat-docs/config/ajp.xml Index: ajp.xml === RCS file: /home/cvs/jakarta-tomcat-4.0/webapps/tomcat-docs/config/ajp.xml,v retrieving revision 1.2 retrieving revision 1.2.2.1 diff -u -r1.2 -r1.2.2.1 -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
