Accelebrate

Course Number: SRV-100
GSA/Previous Course Number: 260
Duration: 2 days
view class outline

Apache Tomcat Training Overview

Apache Tomcat is the most popular platform for deploying Java-based™ Web applications. In this two days course, attendees learn how to administer the Tomcat server, deploy applications on the server, ensure the server's security, troubleshoot problems, and cluster Tomcat to ensure high availability.

Location and Pricing

Most Accelebrate courses are taught on-site at our clients' locations worldwide for groups of 3 or more attendees and are customized to their specific needs. Please visit our client list to see organizations for whom we have recently delivered training. These courses can also be delivered as live, private online classes for groups that are geographically dispersed or wish to save on the instructor's or students' travel expenses. To receive a customized proposal and price quote private training at your site or online, please contact us.

In addition, some courses are available as live, online classes for individuals. To see a schedule of online courses, please visit http://www.accelebrate.com/online_training/server.htm.

Apache Tomcat Training Prerequisites

All attendees should be familiar with general principles of Web server administration and have some experience building Web applications. Prior experience with Java as an application server administrator or developer is helpful but not required.

Hands-on/Lecture Ratio

This Tomcat training class is 70% hands-on, 30% lecture, with the longest lecture segments lasting for 20 minutes. Students "learn by doing," with immediate opportunities to apply the material they learn to real-world problems.

Apache Tomcat Training Materials

All students receive a copy of Wrox Press's Professional Apache Tomcat 6 (used as the main textbook for the course) and related courseware.

Software Needed on Each Student PC

This course can be taught either of 2 ways:

Using the Windows version of Apache Tomcat 5.0, 5.5, 6.0, 7.0, or later. The instructor brings all software needed for class on flash drives, and students install/configure the software as part of the training. Students need local administrator rights and the PCs should have at least 1GB of RAM (2GB RAM or more recommended).

Using Apache Tomcat in a Linux or Solaris virtual machine (any version of Tomcat can be taught). We would provide you with the virtual machine in advance for installation. Classroom PCs should have:

At least 1GB RAM and 10GB hard drive space (2GB RAM recommended)
The latest version of VMware Player (http://www.vmware.com/download/player/download.html)
An unzipped copy of the VMware image we provide

Apache Tomcat Training Objectives

All attendees will learn how to:

Set up and configure Apache Tomcat
Deploy Java web applications to the Tomcat server
Configure Tomcat valves for access logging, single sign-on, and access control
Monitor Tomcat via its JMX MBeans and a variety of tools, including JConsole, VisualVM, and PSI Probe
Tune Tomcat for optimal performance
Configure Tomcat logs and troubleshoot Tomcat
Secure Tomcat
Build and monitor database connection pools
Run Tomcat behind a web server, such as Apache httpd or Microsoft IIS
Build Tomcat clusters to ensure high availability

Apache Tomcat Training Outline

Introduction

Overview of the Apache Software Foundation and the Jakarta Project
Overview of Java EE as a platform
Overview of the features and functionality specifically provided by Tomcat

Installing Tomcat

Installing the Java Runtime Environment (JRE)
Tweaking the JRE for performance
Performing the actual Tomcat installation

Examining the Tomcat installation directories

bin
conf
common (Tomcat 5.5 and earlier)
lib (Tomcat 6 and later)
logs
server (Tomcat 5.5 and earlier)
shared (Tomcat 5.5 and earlier)
temp
webapps
work

Configuring Tomcat

server.xml (detailed walkthrough)
web.xml
context.xml

Tomcat Valves

AccessLog and FastCommonAccessLog
RequestFilterValve
SingleSignOnValve (by request)
RequestDumperValve (by request)

Memory management and JMX monitoring

Understanding Java garbage collection
Using JAVA_OPTS, JMX and JConsole to monitor and tune Tomcat memory usage
Sizing Tomcat's JVM memory heap
Using JMX and JConsole to configure Tomcat via Tomcat's MBeans
Updating Tomcat's configuration via JMX "on the fly" without restarting Tomcat
Load testing with JMeter
Using VisualVM (new monitoring tool built into JDK 6) and PSI Probe
Controlling JMX MBeans via Ant

Logging

JULI logging
log4j logging
Understanding exceptions and thread dumps

Connecting databases with Tomcat applications

Classic JDBC approach
Better approach: JNDI resources
Setting up and monitoring database connection pools

Security

File system security
Java security manager
Realms, authentication, and authorization
SSL

Performance tuning strategies

Additional JVM tuning tips
Enabling parallel garbage collection
Building native connectors
Disabling/removing unneeded applications
Tuning incoming connections and database connection pools
Turning off Jasper development mode
Precompiling JSPs
Preloading servlets

Tomcat 7 New Features [optional]

Memory leak prevention and detection
Servlet 3.0, JSP 2.2, and EL 2.2 support (and the practical implications of this for Tomcat admins)
Cross-site request forgery prevention (and how to configure)
How Tomcat 7's new session management features prevent session fixation attacks
Alias support (which allow static content to be stored outside the WAR file)

Running Tomcat behind Apache httpd or IIS [this section would be taught using your web server and connector module of choice]

Why run Tomcat behind Apache httpd or IIS?
Installing mod_jk (Apache or Tomcat) or mod_proxy_ajp and mod_proxy_balancer (Apache 2.2 or later only)
Proxying traffic to Tomcat via AJP
Monitoring the status of your web server’s connection to Tomcat
Load balancing Tomcat via mod_jk or mod_proxy_balancer

Tomcat Clustering

Configuring mod_jk (in Apache or IIS) or mod_proxy_balancer (Apache 2.2 or later only) as a load balancer
Hardware load balancing as an alternative to software load balancing
Sticky sessions
Configuring a shared session back-end

FileStore/JDBCStore (older approach, generally not recommended)
Using the <Cluster /> tag

Configuring the application to be distributable
Setting up and testing failover

Conclusion