The content you have selected is available exclusively to Terracotta, Ehcache, and Quartz community members. If you are already a member, please login. If not, please take a moment to become one. Please sign up to join the Terracotta, Ehcache, and Quartz communities. Membership is free and only requires you to complete the form below. In addition to full documentation access, you will also be eligible to attend product briefings, download select early access product releases before the general public, post forum questions, file bug reports, submit patches and receive other member benefits still to come.
(But you're not quite done—you still need to validate your account. Please check your email!)
Thanks for joining the Terracotta and Ehcache community. You will recieve an e-mail shortly containing instructions for validating your account and downloading Ehcache EX.
After you validate your account, you will have full access to all Terracotta and Ehcache community resources, such as:
This document shows how to cluster web applications with Terracotta Web Sessions.
Terracotta clusters web applications based on a number of popular web containers (or application servers). See Platform Support for certified containers and supported versions.
To install Web Sessions, see Web Sessions Express Installation.
The following diagram shows the architecture of a typical Terracotta-enabled web application.

The load balancer parcels out HTTP requests from the Internet to each application server. To maximize the locality of reference of the clustered HTTP session data, the load balancer uses HTTP session affinity so all requests corresponding to the same HTTP session are routed to the same application server. However, with a Terracotta-enabled web application, any application server can process any request.
The application servers run both your web application and the Terracotta client software, and are called "clients" in a Terracotta cluster. As many application servers may be deployed as needed to handle your site load.
For more information on sizing and deployment concerns, see the Deployment Guide and the Operations Guide .
A Terracotta cluster can be deployed with one or more Terracotta servers, which act as the data store for HTTP session data and coordinate access by the application servers to that session data. For more information on setting up a Terracotta cluster, see Configuring Terracotta For High Availability and Terracotta Server Arrays.
Top of 4 Clustering Web Applications with Terracotta Web Sessions