Tomcat is the servlet container that is used in the official Reference Implementation for the Java Servlet and JavaServer Pages technologies. The Java Servlet and JavaServer Pages specifications are developed by Sun under the Java Community Process. From the authors point of view: | ||
--jakarta.apache.org |
Tomcat is the successor of jserv which is no longer developed. Tomcat supports the latest jsp and servlet-APIs defined by sun. Unfortunately Tomcat is very difficult to build from source, because it is using its own building-system called "ant". There is also a very long list of prerequisites if you want to build from source. See http://jakarta.apache.org/tomcat/tomcat-4.0-doc/BUILDING.txt for more details - Good luck, and give some feedback to the author.
In the meantime the HOWTO is providing some basic support for Tomcat installed from binaries.
The Author is searching for some volunteers who tries to build Tomcat from source and tells what steps are required
Please see java.sun.com
Too much for this HOWTO, please see http://java.sun.com/j2se/1.3/docs/relnotes/features.html
Go to http://java.sun.com/j2se/1.3/ [1],choose your platform and follow the steps on the site.
Execute the binary:
chmod +x j2sdk-1_3_1_02-linux-i386.bin ./2sdk-1_3_1_02-linux-i386.bin |
After accepting the license, unpack the stuff and move the resulting directory to /usr/lib and set an appropriate symbolic link
Origin-Site: http://jakarta.apache.org/builds/jakarta-tomcat-4.0/release/v4.1.18/src/jakarta-tomcat-4.1.18-src.tar.gz
cd /usr/local tar -xvzf jakarta-tomcat-4.1.8.tar.gz cd jakarta-tomcat-4.1.8 cd bin rm *.bat echo export JAVA_HOME=/usr/lib/java/ >> /etc/profile . /etc/profile |
To enable the Tomcat manager, you need to modify /usr/local/jakarta-tomcat-4.1.8/conf/tomcat-users.xml add a user »admin« or with the role »manager«. The result should look like this:
<?xml version='1.0' encoding='utf-8'?> <tomcat-users> <role rolename="manager"/> <role rolename="tomcat"/> <role rolename="role1"/> <user username="admin" password="secret" roles="manager"/> <user username="tomcat" password="tomcat" roles="tomcat"/> <user username="role1" password="tomcat" roles="role1"/> <user username="both" password="tomcat" roles="tomcat,role1"/> </tomcat-users> |
Now you should be able to startup tomcat:
/usr/local/apache/jakarta-tomcat-4.1.8/bin/startup.sh |
You should now be able to connect to: http://localhost:8080/index.jsp
If you like to have a native interface into your Apache Webserver, you need to build mod_jk with must be downloaded separately here: http://jakarta.apache.org/builds/jakarta-tomcat-4.0/release/v4.1.18/src/jakarta-tomcat-connectors-4.1.18-src.tar.gz.
tar -xvzf jakarta-tomcat-connectors-4.1.18-src.tar.gz cd jakarta-tomcat-connectors-4.1.18-src/jk/native ./buildconf ./configure --with-apxs=/usr/local/apache/bin/apxs make make install |
Now follows the annoying part, the customizing of the config files. First edit /usr/local/jakarta-tomcat-connectors-4.1.18-src/jk/conf/workers.properties, and copy the file to /usr/local/apache/conf
I made a sample workers.properties that works with the example JSPs and servlets that comes with the Tomcat distribution. It is based on the sample workers.properties from Tomcat
Example 8. workers.properties
workers.tomcat_home=/usr/local/jakarta-tomcat-4.1.18 # workers.java_home should point to your Java installation. Normally # you should have a bin and lib directories beneath it. # workers.java_home=/usr/lib/java2 # You should configure your environment slash... ps=\ on NT and / on UNIX # and maybe something different elsewhere. # ps=/ # The workers that your plugins should create and work with # worker.list=worker1 #------ DEFAULT ajp13 WORKER DEFINITION ------------------------------ #--------------------------------------------------------------------- # Defining a worker named ajp13 and of type ajp13 # Note that the name and the type do not have to match. # worker.worker1.port=8009 worker.worker1.host=localhost worker.worker1.type=ajp13 #------ CLASSPATH DEFINITION ----------------------------------------- #--------------------------------------------------------------------- # Additional class path components. # worker.inprocess.class_path=$(workers.tomcat_home)$(ps)lib$(ps)tomcat.jar # The JVM that we are about to use # # Unix - Sun VM or blackdown worker.inprocess.jvm_lib=$(workers.java_home)$(ps)jre$(ps)lib$(ps)i386$(ps)classic$(ps)libjvm.so # Setting the place for the stdout and stderr of tomcat # worker.inprocess.stdout=$(workers.tomcat_home)$(ps)logs$(ps)inprocess.stdout worker.inprocess.stderr=$(workers.tomcat_home)$(ps)logs$(ps)inprocess.stderr |
Next, you need to configure your apache config file httpd.conf. The following example matches the examples provided by Tomcat.
LoadModule jk_module libexec/mod_jk.so AddModule mod_jk.c JkWorkersFile /usr/local/apache/conf/workers.properties JkLogFile /var/log/httpd/mod_jk.log JkLogLevel info JkLogStampFormat "[%a %b %d %H:%M:%S %Y] " JkOptions +ForwardKeySize +ForwardURICompat -ForwardDirectories JkRequestLogFormat "%w %V %T" JkMount /examples/servlet/* worker1 JkMount /examples/*.jsp worker1 |
After restarting Apache, you should now be able to connect to your JSP's via Apache. I.e: http://localhost/examples/jsp/num/numguess.jsp
For the further steps like installing your servlets and jsp-files, you are responsible by yourself...
Environment Variables | |
---|---|
If Tomcat fails to start and/or your servlets could not be started the most common error made is having not all needed classes in the CLASSPATH variable. |
[1] | There is also version 1.4.1 of Java available, but Tomcat seems not to run with that version of Java. |