Apache Tomcat 7 implements the Java Servlet 3.0 and JSP 2.0 specification
from Sun Microsystems/Oracle and provides a pure Java HTTP web server.
- app-servers ›
Apache Tomcat is an open source implementation of
the Java Servlet and JavaServer Pages (JSP) specifications, and provides a
"pure Java" HTTP web server environment for Java web applications to run.
Apache Tomcat 7 implements the Java Servlet 3.0 and JSP 2.2 specifications
from the Java Community Process.
Known Limitations and Issues
The tomcat7 charm has been replaced by another charm with more features. The
tomcat charm contains all
features of the tomcat7 charm with additional functionality and additional
configuration options. We recommend switching to this new charm, this charm is
in the charm store for historical reasons.
A simple deployment consists of a Tomcat service:
juju deploy tomcat7
That deploys Apache Tomcat version 7 on an Ubuntu image.
To expose Tomcat to the Internet:
juju expose tomcat7
You can then browse to http://tomat7-ip-address:8080 to see the default Tomcat
The Apache Tomcat software contains a Web Application Manager that allows
remote deployment of web applications. This process requires authentication
and this charm defaults to username='admin' password='admin'
This charm allows the configuration of the admin username and admin password.
The manager webapp is password protected
juju set tomcat7 admin_username=<username> juju set tomcat7
Go to http://tomcat7-ip-address:8080/manager to access the Tomcat Web
Application Manager. Authenticate with the admin username and password that
was set in the tomcat7 configuration.
Got to http://tomcat7-ip-address:8080/host-manager for the Tomcat Virtual Host
Manager. Authenticate with the admin username and password set in the
Scale out Usage
You can deploy the tomcat7 charm in a cluster by using multicast. By default,
static membership is used over multicast based membership which means units
depend on local cluster configuration to determine cluster groups. Multicast
uses multicast UDP packets on a pre-determined address/port to determine
cluster groups. Where a cloud provider such as EC2 disables multicast traffic
between instances, static membership must be used. Where multicast traffic is
allowed, it is preferred and may be enabled as follows:
# enable multicast clustering juju set tomcat7 multicast=True # set multicast address juju set tomcat7 multicast_address=18.104.22.168 # set multicast port juju set tomcat7 multicast_port=34569
This charm was originally created by Juan Negron firstname.lastname@example.org.
Apache Tomcat Project Information
- (string) Password to use to access manager and admin applications
- (string) Username to use to access manager and admin applications
- (boolean) Use multicast networking for clustering This has the advantage that is does not require restarts of the tomcat7 instances when units are added or removed from a deployed service. However multicast is not supported in all environments (like ec2) in which case static configuration and restarts of tomcat7 instances will be used instead. Valid values include True or False
- (string) Multicast network address to use if using multicast for clustering. Always ensure that this is a private multicast address in the range 22.214.171.124 through 126.96.36.199 and use different addresses and/or ports for multiple tomcat7 services within the same environment or network.
- (int) Multicast network port to use if using multicast for clustering - see notes above about how to use multicast configuration to seperate tomcat7 clusters.