.../index.html
.../TheTextFile.txt
.../OurSoftware/OurProgram.exe
.../OurSoftware/TheTarFile.tgz
.../something.jsp
.../spiffyapplet.class
.../somedir/someother.html
.../anotherdir/some.jsp
.../anotherdir/my.html
.../anotherdir/funny.gif
.../images/some.gif
.../images/some.jpeg
.../WEB-INF/web.xml
.../WEB-INF/lib/...
.../WEB-INF/lib/some.jar
.../WEB_INF/classes/...
.../WEB_INF/classes/com/bigcomp/servlets/ByFromUs.class
.../WEB_INF/classes/com/bigcomp/utils/SnoopUser.class
.../WEB_INF/classes/com/bigcomp/utils/FancyServlet.class

• Files to be directly served on the Web, i.e., HTML, applets, JSP, style sheets, images, text files, etc. These files are in top directory, and in ordinary directories which will be served as regular Web content in the Web document tree.
  
  
• Files located under WEB-INF directory. These files are not to be served directly by the Web server. The lib subdirectory contains jar files, with Java binary code, which will be automatically included in the Servlet Container CLASSPATH. The files under classes subdirectory represent classes and packages needed within web applications. These can be either servlets to be served or they may be utility classes or JavaBeans (needed by servlets and/or JSPs). The web.xml is an XML file which allows to set and/or modify parameters, arguments, remap names, set mime types, specify tag libraries, specify servlets to be loaded on start-up, define scopes, authentication, encryption, etc., etc., for the components of the current web application. To learn more about it, study the Bible, i.e., Java Servlet Specification, v2.2 ( http://java.sun.com/products/servlet/2.2/ ).

Include /usr/local/apache_t3.1b1/sources/build/tomcat/conf/tomcat.conf

• On which port the Tomcat is listening via ApJServDefaultPort directive.
• That the files with *.jsp extension should be handled by jserv
  AddHandler jserv-servlet .jsp,
• That certain URLs, should be directed to Tomcat for processing. For example:
  ApJServMount /DynaWeb /root
  tells Apache that URs whose path start with /DynaWeb should go to Tomcat for processing. The /root seems to be fixed at this moment, but it will probably evolve at some point to what it was in the original Apache JServ module.
• That certain paths in the Web Document Tree should be blocked from public view, e.g.:

  <Location /DynaWeb/WEB-INF/ >
       AllowOverride None
       deny from all
  </Location>

  tells Apache to deny access to the URLs which start from /DynaWeb/WEB-INF. In this case it is probably overkill, since Tomcat most likely checks and enforces that the WEB-INF directory is not served directly.
• There may be additional directives which take actions BEFORE the request is forwarded to Tomcat, e.g., rewriting URLs with Rewrite, providing Basic Authentication, as for example:

  <Location /DynaWeb>
  AuthType Basic
  AuthName "For internal users only"
  AuthUserFile /usr/local/apache/auth/htpasswd
  AuthGroupFile /usr/local/apache/auth/htgroup
  AuthType Basic
  
  <Limit GET POST>
  require group demo
  </Limit>
  </Location>

  and aliasing some locations, restricting access, etc. I am not sure if the encryption of Tomcat Apache communication is supported at this moment. Yes, the is a bleeding edge, and there is not much documentation, and you need to look up the comments in the files and source code, or simply try, to know what is happening.

  <Context path="/mytests"
   docBase="/usr/local/apache_t3.1b1/htdocs/jkltests" debug="0"
   reloadable="true" />

• path sets the path to this context in URLs, e.g., the URLs http://www.webette.com/mytests/index.jsp or http://www.webette.com/mytests/servlet/HelloWorld could be referring to this context.
• docBase points to the disk directory which holds the web application. Note that directory name does not have to be the same as the URL path. This does not have to be an absolute path. The relative paths will be appended to $TOMCAT_HOME/webapps.
• reloadable tells the Tomcat if it should reload the JSP page, when its source was changed.

      <Connector
          className="org.apache.tomcat.service.SimpleTcpConnector">
        <Parameter name="handler"
           value="org.apache.tomcat.service.http.HttpConnectionHandler"/>
        <Parameter name="port" value="8080"/>
      </Connector>

      <Connector
         className="org.apache.tomcat.service.SimpleTcpConnector">
        <Parameter name="handler"
          value="org.apache.tomcat.service.connector.Ajp12ConnectionHandler"/>
        <Parameter name="port" value="8007"/>
      </Connector>

  ApJServMount /Shop /root
  <Location /Shop/WEB-INF/>
    AllowOverride None
    deny from all
  </Location>

  <Context path="/Shop"
  docBase="/path/to/document/root/Shop"
  debug="0"
  reloadable="true">
  </Context>

  ApJServMount /Boutique /root
  <Location /Boutique/WEB-INF>
    AllowOverride None
    deny from all
  </Location>
  <Directory /path/to/document/root/Shop >
    AllowOverride None
    deny from all
  </Directory>

  <Context path="/Boutique"
  docBase="/path/to/document/root/Shop"
  debug="0"
  reloadable="true">
  </Context>

• Set environment variables (Assuming you use /bin/sh or like):

  JAVA_HOME=/usr/local/jdk1.2.2    (or /usr/java1.2 under Solaris)
  export JAVA_HOME
  TOMCAT_HOME=/usr/local/apache_t3.1b1/sources/build/tomcat
  export TOMCAT_HOME
  PATH=${PATH}:${JAVA_HOME}/bin
  export PATH
  CLASSPATH=${JAVA_HOME}/lib/tools.jar:${JAVA_HOME}/lib/dt.jar:${TOMCAT_HOME}/classes
  export CLASSPATH
  

• Compile your servlet as:

  javac MyNewServlet.java
  

============== cut ===========
  #!/bin/sh
  JAVA_HOME=/usr/local/jdk1.2.2    (or /usr/java1.2 under Solaris)
  export JAVA_HOME
  TOMCAT_HOME=/usr/local/apache_t3.1b1/sources/build/tomcat
  export TOMCAT_HOME
  PATH=${PATH}:${JAVA_HOME}/bin
  export PATH
  CLASSPATH=${JAVA_HOME}/lib/tools.jar:${JAVA_HOME}/lib/dt.jar:${TOMCAT_HOME}/classes
  export CLASSPATH
  javac $1 
============== cut ===========

  ApJServMount /mytests /root
  <Location /mytests/WEB-INF/ >
    AllowOverride None
    deny from all
  </Location>
  <Directory /home/www/jkltests >
    AllowOverride None
    deny from all
  </Dierectory>
   

      <Context path="/mytests"
         docBase="/home/www/jkltests" debug="0"
         reloadable="true" />

/home/www/jkltests:
drwxr-sr-x   3 root     www          512 Apr  1 04:56 WEB-INF
-rw-r--r--   1 root     www           39 Mar 31 15:14 junk.html
drwxr-sr-x   2 root     www          512 Apr  1 05:08 junky

/home/www/jkltests/WEB-INF:
drwxr-sr-x   3 root     www          512 Apr  1 04:36 classes
-rw-r--r--   1 root     www          939 Apr  1 04:56 web.xml

/home/www/jkltests/WEB-INF/classes:
-rw-r--r--   1 root     www         1399 Apr  1 03:07 HelloYou.class
-rw-r--r--   1 root     www         1647 Apr  1 02:59 HelloYou.java
-rw-r--r--   1 root     www         1407 Apr  1 03:01 ServletHello.class
-rw-r--r--   1 root     www         1655 Apr  1 03:01 ServletHello.java
drwxr-sr-x   2 root     www          512 Apr  1 04:35 sp

/home/www/jkltests/WEB-INF/classes/sp:
-rw-r--r--   1 root     www         1413 Apr  1 03:04 HelloJKL.class
-rw-r--r--   1 root     www         1660 Apr  1 03:04 HelloJKL.java

/home/www/jkltests/junky:
-rw-r--r--   1 root     www          146 Mar 31 22:55 junk.jsp

?xml version="1.0" encoding="ISO-8859-1"?>

<!DOCTYPE web-app
    PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.2//EN"
    "http://java.sun.com/j2ee/dtds/web-app_2.2.dtd">

<web-app>
</web-app>

  http://my.machine.org/mytests/junky/junk.jsp
  http://my.machine.org/mytests/junk.html
  http://my.machine.org/mytests/servlet/ServletHello
  http://my.machine.org/mytests/servlet/HelloYou
  http://my.machine.org/mytests/servlet/sp.HelloJKL

<?xml version="1.0" encoding="ISO-8859-1"?>

<!DOCTYPE web-app  PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.2//\EN"
    "http://java.sun.com/j2ee/dtds/web-app_2.2.dtd">

<web-app>
  <servlet>
    <servlet-name>JKL</servlet-name>
    <servlet-class>sp.HelloJKL</servlet-class>
  </servlet>
  <servlet-mapping>
    <servlet-name>JKL</servlet-name>
    <url-pattern>/JKLservlet</url-pattern>
  </servlet-mapping>
  <servlet-mapping>
    <servlet-name>JKL</servlet-name>
    <url-pattern>*.jkl</url-pattern>
  </servlet-mapping>
  <servlet>
    <servlet-name>You</servlet-name>
    <servlet-class>HelloYou</servlet-class>
  </servlet>
  <servlet-mapping>
    <servlet-name>You</servlet-name>
    <url-pattern>/YouServlet/*</url-pattern>
  </servlet-mapping>
  <servlet-mapping>
    <servlet-name>You</servlet-name>
    <url-pattern>/us/him/her</url-pattern>
  </servlet-mapping>
</web-app>

http://heechee.ccl.net/mytests/servlet/JKL
http://heechee.ccl.net/mytests/JKLservlet
http://heechee.ccl.net/mytests/servlet/sp.HelloJKL
http://heechee.ccl.net/mytests/whatever/and/so/page.jkl

http://heechee.ccl.net/mytests/servlet/HelloYou
http://heechee.ccl.net/mytests/servlet/You
http://heechee.ccl.net/mytests/YouServlet
http://heechee.ccl.net/mytests/YouServlet/whatever.html
http://heechee.ccl.net/mytests/us/him/her

Thomas Oellrich wrote:

 > Hello,
 >
 > Can anybody tell me whether it's possible to automatically load a servlet
 > on startup of Tomcat? If yes, how? If no, is this feature intended for
 > future releases? I couldn't find any information on this in the official
 > documentation.
 >

 Use the <load-on-startup> element in your web.xml file, as described in the
 Servlet 2.2 API spec.  The data value determines the order in which the
 startup servlets are loaded.

     <servlet>
         <servlet-name>MyServlet</servlet-name>
         <servlet-class>com.mycompany.servlets.MyServletClass</servlet-class>

         <init-param>
             <param-name>param1</param-name>
             <param-value>value1</param-value>
         </init-param>
         <load-on-startup>3</load-on-startup>
     </servlet>


Craig McClanahan
==============================

    bin/startup.sh -f /usr/local/mytomcat/conf/server.xml
    

• From: Andreas Siegrist <A.Siegrist@tv1.de> to tomcat-dev@jakarta.apache.org

  Tomcat 3.0
  You may get the user name (and password) by decoding the
  authorization string yourself. We are using a static method in a
  utility class:
  
  public static String getRemoteUser(HttpServletRequest request) {
      String auth = request.getHeader("authorization"); // as send by apache
      if (auth == null) return null;
  
      try {
        auth = new String((new
  BASE64Decoder()).decodeBuffer(auth.substring(6)));
      }
      catch (Exception exc) {
        exc.printStackTrace();
        return null;
      }
  
     if (auth == null)
        return null;
      int pos = auth.indexOf(":");
      if (pos < 0)
        return null;
      return auth.substring(0, pos);
  }
  

  <Location /examples>
  AuthType Basic
  AuthName "For internal users only"
  AuthUserFile /usr/local/apache/auth/avspass
  AuthGroupFile /usr/local/apache/auth/avspeople
  AuthType Basic

  <Limit GET POST>
  require group avs
  </Limit>
  </Location>

<Parameter name="port" value="XXXX"/>

• Remember that you need to run tomcat as a root if you want to use ports lower than 1024
• If you change the tomcat port 8007 (i.e., the one with which it talks to Apache Web server, you need to make the corresponding change in the tomcat.conf file (the line: ApJServDefaultPort 8007).

        <!-- New HttpServer.  -->
        <Connector className="org.apache.tomcat.service.http.HttpAdapter">
        </Connector>

<!--  Disabling web server on port 8080 by commenting out the line:
        <Connector className="org.apache.tomcat.service.http.HttpAdapter">
        </Connector>
-->

• httpd.conf
• server.xml
• tomcat.conf
• tomcat-apache.conf
• tomcat.properties

    <servlet>
      <servlet-name>myServlet</servlet-name>
      <servlet-class>myServlet</servlet-class>
      <init-param>
        <param-name>where</param-name>
        <param-value>Rome</param-value>
      </init-param>
      <init-param>
        <param-name>when</param-name>
        <param-value>66</param-value>
      </init-param>
    </servlet>

Kindly contributed by:  Viv Gregory <vivg@layer3.co.uk>
Solving "http: can't resolve symbol ap_escape_uri"
or
How to make Tomcat 3.2.1 work with Apache 1.3.3


We have a legacy web server running Redhat 4.2 with a 1.3.3 Apache, when
I tried to integrate Tomcat 3.2.1 I found that the mod_jserv.so module
which is used to link Apache to Tomcat was generating an error;

        httpd: can't resolve symbol ap_escape_uri

Out of curiosity I looked at the source to mod_jserv.so:
See:  .../jakarta-tomcat-3.2.1/src/native/apache/jserv/*.c

I found that there was only one use of the string in the code (see
jserv_ajpv12.c) and figured that it was probably calling an internal
apache function.

I checked the source to Apache 1.3.3 and could not find the string,
however by searching for escape_uri I found many similar calls.
Significantly the Apache 1.3.3 code used escape_uri and the Tomcat code
used ap_escape_uri.

I changed the source in jserv_ajpv12.c to escape_uri so it would match
Apache 1.3.3.              
install instructions.

        cd jakarta.../src/native/apache/jserv
        apxs -c *.c -o mod_jserv.so

This also initially failed producing a "command failed with rc=" type
error message, searching the web I discovered some instructions about
changing the environment variables in the apxs build program.

Here is a "diff apxs apxs.original.1.3.3" which shows the changes I made

[my changes]
< my $CFG_CFLAGS_SHLIB  = '-fpic -DSHARED_MODULE';  # substituted via
Makefile.tmpl
< my $CFG_LD_SHLIB      = 'gcc';      # substituted via Makefile.tmpl
< my $CFG_LDFLAGS_SHLIB = '-shared'; # substituted via Makefile.tmpl
---
[original 1.3.3 Apache]
> my $CFG_CFLAGS_SHLIB  = '';  # substituted via Makefile.tmpl
> my $CFG_LD_SHLIB      = '';      # substituted via Makefile.tmpl
> my $CFG_LDFLAGS_SHLIB = ''; # substituted via Makefile.tmpl

I also came across a note saying that one should in fact use the
following command to build the mod_jserv.so file.

        apxs -c -0 mod_jserv.so *.c

This worked so I then put the mod_jserv.so in the correct
.../apache/libexec area and it was then possible to start Tomcat.

>From then on I could play around with the webapps examples and generaly

fool around with some simple jsp and servlets.

Viv Gregory.(Layer3 Systems Limited)