Editing Apache Tomcat (section)

==Components==
Tomcat 4.x was released with Catalina (a servlet container), Coyote (an HTTP connector) and Jasper (a [[JSP engine]]).

===Catalina===
Catalina is Tomcat's [[Web container|servlet container]]. Catalina implements [[Sun Microsystems]]' specifications for [[Java servlet|servlet]] and JavaServer Pages (JSP). In Tomcat, a Realm element represents a "database" of usernames, passwords, and roles (similar to [[Unix]] groups) assigned to those users. Different implementations of Realm allow Catalina to be integrated into environments where such authentication information is already being created and maintained, and then use that information to implement Container Managed Security as described in the Servlet Specification.<ref>{{cite web|url=http://tomcat.apache.org/tomcat-5.5-doc/config/realm.html |title=Apache Tomcat Configuration Reference - The Realm Component |publisher=Tomcat.apache.org |access-date=2013-11-01}}</ref>

===Coyote===
Coyote is a Connector component for Tomcat that supports the HTTP 1.1 and 2 protocol as a web server. This allows Catalina, nominally a Java Servlet or JSP container, to also act as a plain web server that serves local files as HTTP documents.<ref>[http://tomcat.apache.org/tomcat-4.1-doc/config/coyote.html The Coyote HTTP/1.1 Connector], Apache</ref> Coyote listens for incoming connections to the server on a specific [[Transmission Control Protocol|TCP]] port and forwards the request to the Tomcat Engine to process the request and send back a response to the requesting client. Another Coyote Connector, Coyote JK, listens similarly but instead forwards its requests to another web server, such as Apache, using the [[Apache JServ Protocol|JK Protocol]].<ref>{{cite web|url=http://tomcat.apache.org/tomcat-4.1-doc/config/coyotejk.html|title=Server Configuration Reference - The Coyote JK Connector|website=tomcat.apache.org|access-date=24 August 2018}}</ref> This usually offers better performance.{{citation needed|date=September 2016}}

===Jasper===
Jasper is Tomcat's JSP Engine. Jasper [[Parsing|parses]] [[JavaServer Pages|JSP]] files to compile them into Java code as servlets (that can be handled by Catalina). At runtime, Jasper detects changes to JSP files and recompiles them.

As of version 5, Tomcat uses Jasper 2, which is an implementation of the Sun Microsystems' JSP 2.0 specification. From Jasper to Jasper 2, important features were added:
* JSP Tag library pooling – Each tag markup in JSP file is handled by a tag handler class. Tag handler class objects can be pooled and reused in the whole JSP servlet.
* Background JSP compilation – While recompiling modified JSP Java code, the older version is still available for server requests. The older JSP servlet is deleted once the new JSP servlet has finished being recompiled.
* Recompile JSP when included page changes – pages can be inserted and included into a JSP at runtime. The JSP will not only be recompiled with JSP file changes but also with included page changes.
* JDT Java compiler – Jasper 2 can use the Eclipse JDT (Java Development Tools) Java compiler instead of [[Apache Ant|Ant]] and <code>[[javac]]</code>.

Three new components were added with the release of Tomcat 7:

===Cluster===
This component has been added to manage large applications. It is used for [[Load balancing (computing)|load balancing]] that can be achieved through many techniques. Clustering support currently requires the JDK version 1.5 or higher.

===High availability===
A high-availability feature has been added to facilitate the scheduling of system upgrades (e.g. new releases, change requests) without affecting the live environment. This is done by dispatching live traffic requests to a temporary server on a different port while the main server is upgraded on the main port. It is very useful in handling user requests on high-traffic web applications.<ref>{{cite web |last1=King |first1=Graham |date=2004-12-20 |df=mdy |url=https://www.infoworld.com/article/2073121/high-availability-tomcat.html |title=High availability Tomcat |work=[[JavaWorld]] |access-date=2020-07-21}}</ref>