Tomcat is a J2EE servlet container.

It supports JSP 2.0 and Servlet 2.4

It is also a web server.

More information is available at: http://jakarta.apache.org/tomcat/index.html

You can download it at: http://apache.towardex.com/jakarta/tomcat-5/v5.0.19/bin/ (~ 12MB)

You need a JDK 1.4.x installed to run Tomcat.

Also, the environment variable JAVA_HOME must be set correctly.

It should point to where Java 1.4.x is installed.

On Mac OS X & other unix-based systems:

set JAVA_HOME=/usr

On some unix systems, you need to point to where it is installed. For example:

set JAVA_HOME=/opt/j2sdk1.4.2

On windows, point to where you installed the JDK:

set JAVA_HOME=c:\Program Files\Java1.4\

The 'Applications' list shows you all the WAR files installed:

• 'Path' is the relative URI of the application.

• 'Running' is the status of the application.

• 'Commands' will let you manipulate the application.

WARNING: The 'Undeploy' command will delete the application files (WAR contents) from your system. Be careful!

You can upload small WAR files to install them:

1. Login to the manager at http://localhost:8080/manager/html

2. Choose the file to install in the section labeled 'WAR file to deploy'.

3. Submit the file with the 'Deploy' button directly below the file chooser.

You can the access your application at the relative URI using the base name of the WAR file.

For example, myapp.war becomes http://localhost:8080/myapp/

WARNING: You really don't want to do this with large WAR files.

For large WAR files, do the following:

1. Place the WAR file on the host running tomcat (e.g. /Users/you/yourapp.war).

2. Login to the manager at http://localhost:8080/manager/html

3. Under 'Deploy ... WAR file located on Server, do the following:

   1. In the 'WAR or Directory URL, set the location of the file as a URL:

      file:/Users/you/yourapp.war

   2. Click on the 'Deploy' button just below this text field to install the application.

4. The application may not show up immediately on the list of applications because it is still installing. To check the install, click on 'List Applications' and wait.

5. Your application should show up when the web browser returns the results of (4).

You can the access your application the same as in the previous slide.

You may experience a delay the first time you access your application.

Tomcat may be compiling and optimizing your application.

Subsequent access times should be almost immediate.

WAR - Web Application Archive

It contains all the code, documents, etc. necessary to run your application.

It is structured for auto-deployment.

You build WAR files from your source code and implementation libraries (e.g. Cocoon).

A war file is just a jar file (like a zip archive) with a standard structure.

Basic structure:

WEB-INF/ - directory for application support
   lib/ - supporting jar files
   web.xml - configuration file for the application
...

'WEB-INF' is used to package:

• Configuration

• Supporting compiled java code.

• Other non-public information.

The 'web.xml' file tells the J2EE container (Tomcat) what to do.

Everything outside of 'WEB-INF' is public content available via the web server (Tomcat).

The configuration file for an application is an XML document.

For JSP pages, you can have an empty document:

<web-app xmlns="http://java.sun.com/xml/ns/j2ee" version="2.4"/>

You can also configure servlets:

<web-app xmlns="http://java.sun.com/xml/ns/j2ee" version="2.4">

   <servlet>
      <servlet-name>MyApp</servlet-name>
      <servlet-class>edu.berkeley.cde.MyApp</servlet-class>
      <init-param>
         <param-name>test</param-name>
         <param-value>yes</param-value>
      </init-param>
      <init-param>
         <param-name>log</param-name>
         <param-value>fine</param-value>
      </init-param>
   </servlet>

</web-app>

You can also configure JSP pages to act like servlets:

<web-app xmlns="http://java.sun.com/xml/ns/j2ee" version="2.4">

   <servlet>
      <servlet-name>event.service</servlet-name>
      <jsp-file>/event.jsp</jsp-file>
      <init-param>
         <param-name>eventRepository</param-name>
         <param-value>/data/events/</param-value>
      </init-param>
   </servlet>

</web-app>

Each WAR file creates its own environment.

On the same server, you can have different versions of the same Java libraries in different applications.

In Tomcat 5, ROOT.war is automatically mapped to the root of your web server.

In Tomcat 5, ROOT.war is the only way to have something mapped to the root of your web server.

Cocoon is a servlet-based application.

Just install a cocoon distribution into your WEB-INF directory of your WAR file:

1. Copy all the distribution files/directory into the WEB-INF directory.

2. Make sure that the 'sitemap' element points to your sitemap.xmap file in the WEB-INF directory:

   <sitemap check-reload="yes" 
            config="resource://org/apache/cocoon/components/treeprocessor/treeprocessor-builtins.xml" 
            file="context://WEB-INF/sitemap.xmap" 
            logger="sitemap"/>
   

3. Setup your sitemap.xmap file in WEB-INF (see Cocoon documentation).

Cocoon has many, many extra "kits" that provide optional features.

Everything is about 31MB.

I've trimmed this down to about 15MB.