从Tomcat的server.xml文件看Tomcat的组件结构

server.xml的基本结构如下：

<Server> 顶层类元素：可以包括多个Service <Service> 顶层类元素：可以包括一个Engine，多个Connector。 <Connector/> 连接器元素：代表通信接口 <Engine> 容器类元素：为特定的Service组件处理客户请求，可以包含多个Host <Host> 容器类元素：为特定的虚拟主机组件处理客户请求，可以包含多个Context <Context> 容器类元素：为特定的Web应用处理所有客户请求 </Contrext> </Host> </Engine> </Service> </Server> 

下面是对各元素的一些说明：

<Server>

每个<Server>中可以有多个<Service>，而<Service>大约对应一个IP地址，这样Tomcat就可以同时管理多个IP地址，也就是说它有建立服务器集群的能力。

<Service>

每个<Service>原色由一个或多个Connector组成，另外还包括一个Engine，负责处理所有Connector所获得的客户请求。

简单地说<Service>对应一个IP地址。

<Connector>

每个<Service>z中可以包括多个Connector，每个Connector监听<Service>所对应IP地址的IP的一个端口。默认端口为8080，另一个常监听的端口是8009，用于监听来自其它Web Server(Apache)的Servlet/JSP代理请求。

<Engine>

每个<Service>中只有一个<Engine>。<Engine>负责处理Connector所获得的客户请求。简单地说，一个Engine对应一个IP地址和几个端口号组成的地址。

这几个端口号与<Connector>所监听的端口号相对应。

<Host>

Host代表一个虚拟主机，每个虚拟主机和一个域名相匹配。每个虚拟主机下都可以部署一个或多个Web App，每个

Web App对应一个Context。

<Context>

每个<Context>元素对应一个Web Applcation（大约就是一个Web工程），每个Web App由一个或多个Servlet组成。（JSP实质上也是Servlet，会被Tomcat转换成Servlet）。Context在创建的时候将根据配置文件$CATALINA_HOME/conf/web.xml和$WEBAPP_HOME/WEB-INF/web.xml载入Servlet。

一句话总结：

 

1. IP地址与域名不一样，多个域名可以解析到同一个IP地址上。
2. <Engine>对应一个IP地址+多个端口，可以有多个<Host>（域名）。
3. <Host>对应一个域名（Domain Name），可以有多个Context（工程）。
4. <Context>对应一个工程（Web App）。

一份Tomcat默认的server.xml文件

<!-- Note: A "Server" is not itself a "Container", so you may not define subcomponents such as "Valves" at this level. Documentation at /docs/config/server.html --> <Server port="8005" shutdown="SHUTDOWN"> <!--APR library loader. Documentation at /docs/apr.html --> <Listener className="org.apache.catalina.core.AprLifecycleListener" SSLEngine="on" /> <!--Initialize Jasper prior to webapps are loaded. Documentation at /docs/jasper-howto.html --> <Listener className="org.apache.catalina.core.JasperListener" /> <!-- JMX Support for the Tomcat server. Documentation at /docs/non-existent.html --> <Listener className="org.apache.catalina.mbeans.ServerLifecycleListener" /> <Listener className="org.apache.catalina.mbeans.GlobalResourcesLifecycleListener" /> <!-- Global JNDI resources Documentation at /docs/jndi-resources-howto.html --> <GlobalNamingResources> <!-- Editable user database that can also be used by UserDatabaseRealm to authenticate users --> <Resource name="UserDatabase" auth="Container" type="org.apache.catalina.UserDatabase" description="User database that can be updated and saved" factory="org.apache.catalina.users.MemoryUserDatabaseFactory" pathname="conf/tomcat-users.xml" /> </GlobalNamingResources> <!-- A "Service" is a collection of one or more "Connectors" that share a single "Container" Note: A "Service" is not itself a "Container", so you may not define subcomponents such as "Valves" at this level. Documentation at /docs/config/service.html --> <Service name="Catalina"> <!--The connectors can use a shared executor, you can define one or more named thread pools--> <!-- <Executor name="tomcatThreadPool" namePrefix="catalina-exec-" maxThreads="150" minSpareThreads="4"/> --> <!-- A "Connector" represents an endpoint by which requests are received and responses are returned. Documentation at : Java HTTP Connector: /docs/config/http.html (blocking & non-blocking) Java AJP Connector: /docs/config/ajp.html APR (HTTP/AJP) Connector: /docs/apr.html Define a non-SSL HTTP/1.1 Connector on port 8081 --> <Connector port="80" protocol="HTTP/1.1" connectionTimeout="20000" redirectPort="8443" /> <!-- A "Connector" using the shared thread pool--> <!-- <Connector executor="tomcatThreadPool" port="8080" protocol="HTTP/1.1" connectionTimeout="20000" redirectPort="8443" /> --> <!-- Define a SSL HTTP/1.1 Connector on port 8443 This connector uses the JSSE configuration, when using APR, the connector should be using the OpenSSL style configuration described in the APR documentation --> <!-- <Connector port="8443" protocol="HTTP/1.1" SSLEnabled="true" maxThreads="150" scheme="https" secure="true" clientAuth="false" sslProtocol="TLS" /> --> <!-- Define an AJP 1.3 Connector on port 8009 --> <Connector port="8009" protocol="AJP/1.3" redirectPort="8443" /> <!-- An Engine represents the entry point (within Catalina) that processes every request. The Engine implementation for Tomcat stand alone analyzes the HTTP headers included with the request, and passes them on to the appropriate Host (virtual host). Documentation at /docs/config/engine.html --> <!-- You should set jvmRoute to support load-balancing via AJP ie : <Engine name="Standalone" defaultHost="localhost" jvmRoute="jvm1"> --> <Engine name="Catalina" defaultHost="localhost"> <!--For clustering, please take a look at documentation at: /docs/cluster-howto.html (simple how to) /docs/config/cluster.html (reference documentation) --> <!-- <Cluster className="org.apache.catalina.ha.tcp.SimpleTcpCluster"/> --> <!-- The request dumper valve dumps useful debugging information about the request and response data received and sent by Tomcat. Documentation at: /docs/config/valve.html --> <!-- <Valve className="org.apache.catalina.valves.RequestDumperValve"/> --> <!-- This Realm uses the UserDatabase configured in the global JNDI resources under the key "UserDatabase". Any edits that are performed against this UserDatabase are immediately available for use by the Realm. --> <Realm className="org.apache.catalina.realm.UserDatabaseRealm" resourceName="UserDatabase"/> <!-- Define the default virtual host Note: XML Schema validation will not work with Xerces 2.2. --> <Host name="localhost" appBase="webapps" unpackWARs="true" autoDeploy="true" xmlValidation="false" xmlNamespaceAware="false"> <!-- SingleSignOn valve, share authentication between web applications Documentation at: /docs/config/valve.html --> <!-- <Valve className="org.apache.catalina.authenticator.SingleSignOn" /> --> <!-- Access log processes all example. Documentation at: /docs/config/valve.html --> <!-- <Valve className="org.apache.catalina.valves.AccessLogValve" directory="logs" prefix="localhost_access_log." suffix=".txt" pattern="common" resolveHosts="false"/> --> </Host> </Engine> </Service> </Server>