Previous | Top | Next
JDK Tomcat Ant CVS

# 2. INSTALLATION

## 2.1 Java Development Kit

Tomcat will operate under any Java Development Kit (JDK) environment that provides a JDK 1.1, JDK 1.2 (also known as Java2 Standard Edition, or J2SE) or later platform. You will need a Java Development Kit, as opposed to a Java Runtime Environment, so that your servlets, other classes, and JSP pages can be compiled.

Compatible JDKs for many platforms (or links to where they can be found) are available at http://java.sun.com/j2se/.

## 2.2 Jakarta Tomcat

Binary downloads of the Tomcat server are available from the http://jakarta.apache.org/downloads/binindex.html page. This manual assumes you are using the most recent milestone, beta, or release of Tomcat 3.1 -- many of the deployment details have changed since Tomcat 3.0 was released, although the general concepts are very similar.

The shell command line examples in this manual assume that you have set up your environment as follows:

- The `JAVA_HOME` environment variable points at the base directory where you have installed the JDK (for example, `/usr/local/jdk1.2.2`).
- You have added directory `$JAVA_HOME/bin` to your `PATH` environment variable, so that the `java` command is recognized and executed.
- The `TOMCAT_HOME` environment variable points at the base directory where you have installed Tomcat (for example, `/opt/tomcat` or `/usr/local/tomcat`).

Normally, any changes required to the `CLASSPATH` environment variable are handled for you by the development scripts. However, if you are defining your own scripts, you may need to add file `$JAVA_HOME/lib/tools.jar` to your `CLASSPATH`.

## 2.3 Jakarta Ant

Although Tomcat includes a binary distribution of the Ant development tool, it does not include the Ant developer documentation. This can be acquired by downloading the complete Ant release from http://jakarta.apache.org/site/binindex.html page. The example application build scripts assume that you have Ant 1.2 or later.

## 2.4 Concurrent Version System (CVS)

Besides the required tools described above, you are strongly encouraged to download and install a source code control system, such as CVS, to maintain historical versions of the source files that make up your web application. Besides the server, you will also need appropriate client tools to check out source code files, and check in modified versions.

Detailed instructions for installing and using source code control applications is beyond the scope of this manual. However, CVS server and client tools for many platforms (along with documentation) can be downloaded from http://www.cvshome.org.