Top Level Elements
The Engine Container
The Engine element represents the entire request
processing machinery associated with a particular Catalina
Service. It receives and processes
all requests from one or more Connectors,
and returns the completed response to the Connector for ultimate
transmission back to the client.
Exactly one Engine element MUST be nested inside
a Service element, following all of the
corresponding Connector elements associated with this Service.
All implementations of Engine
support the following attributes:
Java class name of the implementation to use. This class must
If not specified, the standard value (defined below) will be used.
The default host name, which identifies the
Host that will process requests directed
to host names on this server, but which are not configured in
this configuration file. This name MUST match the
attributes of one of the Host elements
nested immediately inside.
Identifier which must be used in load balancing scenarios to enable
session affinity. The indetifier, which must be unique across all
Tomcat 4 servers which participate in the cluster, will be appended to
the generated session identifier, therefore allowing the front end
proxy to always forward a particular session to the same Tomcat 4
Logical name of this Engine, used in log and error messages.
The standard implementation of Engine is
It supports the following additional attributes (in addition to the
common attributes listed above):
The level of debugging detail logged by this Engine
to the associated Logger. Higher numbers
generate more detailed output. If not specified, the default
debugging detail level is zero (0).
You can nest one or more Host elements inside
this Engine element, each representing a different virtual
host associated with this server. At least one Host
is required, and one of the nested Hosts MUST
have a name that matches the name specified for the
defaultHost attribute, listed above.
You can optional nest a DefaultContext
element inside this Engine element, to define the default
characteristics of web applications that are automatically deployed.
You can nest at most one instance of the following utility components
by nesting a corresponding element inside your Engine
- Logger -
Configure a logger that will receive
and process all log messages for this Engine, plus
messages from Connectors associated with this Engine
in the surrounding Service. In addition, this Logger will log messages
from subordinate Hosts and
Contexts, unless overridden by a
Logger configuration at a lower level.
- Realm -
Configure a realm that will allow its
database of users, and their associated roles, to be shared across all
Hosts and Contexts
nested inside this Engine, unless overridden by a
Realm configuration at a lower level.