<?xml version="1.0" encoding="UTF-8"?>
<!-- Example Server Configuration File --><!-- Note that component elements are nested corresponding to their     parent-child relationships with each other --><!-- A "Server" is a singleton element that represents the entire JVM,     which may contain one or more "Service" instances.  The Server     listens for a shutdown command on the indicated port.     Note:  A "Server" is not itself a "Container", so you may not     define subcomponents such as "Valves" or "Loggers" at this level. --><Server port="8005" shutdown="SHUTDOWN">  <!-- Comment these entries out to disable JMX MBeans support used for the        administration web application -->  <Listener className="org.apache.catalina.core.AprLifecycleListener"/>  <Listener className="org.apache.catalina.mbeans.ServerLifecycleListener"/>  <Listener className="org.apache.catalina.mbeans.GlobalResourcesLifecycleListener"/>  <Listener className="org.apache.catalina.storeconfig.StoreConfigLifecycleListener"/>  <!-- Global JNDI resources -->  <GlobalNamingResources>    <!-- Test entry for demonstration purposes -->    <Environment name="simpleValue" type="java.lang.Integer" value="30"/>    <!-- Editable user database that can also be used by         UserDatabaseRealm to authenticate users -->    <Resource auth="Container" description="User database that can be updated and saved" factory="org.apache.catalina.users.MemoryUserDatabaseFactory" name="UserDatabase" pathname="conf/tomcat-users.xml" type="org.apache.catalina.UserDatabase"/>  </GlobalNamingResources>  <!-- A "Service" is a collection of one or more "Connectors" that share       a single "Container" (and therefore the web applications visible       within that Container).  Normally, that Container is an "Engine",       but this is not required.       Note:  A "Service" is not itself a "Container", so you may not       define subcomponents such as "Valves" or "Loggers" at this level.   -->  <!-- Define the Tomcat Stand-Alone Service -->  <Service name="Catalina">    <!-- A "Connector" represents an endpoint by which requests are received         and responses are returned.  Each Connector passes requests on to the         associated "Container" (normally an Engine) for processing.         By default, a non-SSL HTTP/1.1 Connector is established on port 8080.         You can also enable an SSL HTTP/1.1 Connector on port 8443 by         following the instructions below and uncommenting the second Connector         entry.  SSL support requires the following steps (see the SSL Config         HOWTO in the Tomcat 5 documentation bundle for more detailed         instructions):         * If your JDK version 1.3 or prior, download and install JSSE 1.0.2 or           later, and put the JAR files into "$JAVA_HOME/jre/lib/ext".         * Execute:             %JAVA_HOME%\bin\keytool -genkey -alias tomcat -keyalg RSA (Windows)             $JAVA_HOME/bin/keytool -genkey -alias tomcat -keyalg RSA  (Unix)           with a password value of "changeit" for both the certificate and           the keystore itself.         By default, DNS lookups are enabled when a web application calls         request.getRemoteHost().  This can have an adverse impact on         performance, so you can disable it by setting the         "enableLookups" attribute to "false".  When DNS lookups are disabled,         request.getRemoteHost() will return the String version of the         IP address of the remote client.    -->    <!-- Define a non-SSL HTTP/1.1 Connector on port 8080 -->    <Connector acceptCount="100" connectionTimeout="20000" disableUploadTimeout="true" enableLookups="false" maxHttpHeaderSize="8192" maxSpareThreads="75" maxThreads="150" minSpareThreads="25" port="8080" redirectPort="8443"/>    <!-- Note : To disable connection timeouts, set connectionTimeout value     to 0 -->		<!-- Note : To use gzip compression you could set the following properties :				   compression="on" 			   compressionMinSize="2048" 			   noCompressionUserAgents="gozilla, traviata" 			   compressableMimeType="text/html,text/xml"	-->    <!-- Define a SSL HTTP/1.1 Connector on port 8443 -->    <!--    <Connector port="8443" maxHttpHeaderSize="8192"               maxThreads="150" minSpareThreads="25" maxSpareThreads="75"               enableLookups="false" disableUploadTimeout="true"               acceptCount="100" scheme="https" secure="true"               clientAuth="false" sslProtocol="TLS" />    -->    <!-- Define an AJP 1.3 Connector on port 8009 -->    <Connector enableLookups="false" port="8009" protocol="AJP/1.3" redirectPort="8443"/>    <!-- Define a Proxied HTTP/1.1 Connector on port 8082 -->    <!-- See proxy documentation for more information about using this. -->    <!--    <Connector port="8082"                maxThreads="150" minSpareThreads="25" maxSpareThreads="75"               enableLookups="false" acceptCount="100" connectionTimeout="20000"               proxyPort="80" disableUploadTimeout="true" />    -->    <!-- 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). -->    <!-- You should set jvmRoute to support load-balancing via AJP ie :    <Engine name="Standalone" defaultHost="localhost" jvmRoute="jvm1">             -->              <!-- Define the top level container in our container hierarchy -->    <Engine defaultHost="localhost" name="Catalina">      <!-- The request dumper valve dumps useful debugging information about           the request headers and cookies that were received, and the response           headers and cookies that were sent, for all requests received by           this instance of Tomcat.  If you care only about requests to a           particular virtual host, or a particular application, nest this           element inside the corresponding <Host> or <Context> entry instead.           For a similar mechanism that is portable to all Servlet 2.4           containers, check out the "RequestDumperFilter" Filter in the           example application (the source for this filter may be found in           "$CATALINA_HOME/webapps/examples/WEB-INF/classes/filters").           Request dumping is disabled by default.  Uncomment the following           element to enable it. -->      <!--      <Valve className="org.apache.catalina.valves.RequestDumperValve"/>      -->      <!-- Because this Realm is here, an instance will be shared globally -->      <!-- 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"/>      <!-- Comment out the old realm but leave here for now in case we           need to go back quickly -->      <!--      <Realm className="org.apache.catalina.realm.MemoryRealm" />      -->      <!-- Replace the above Realm with one of the following to get a Realm           stored in a database and accessed via JDBC -->      <!--      <Realm  className="org.apache.catalina.realm.JDBCRealm"             driverName="org.gjt.mm.mysql.Driver"          connectionURL="jdbc:mysql://localhost/authority"         connectionName="test" connectionPassword="test"              userTable="users" userNameCol="user_name" userCredCol="user_pass"          userRoleTable="user_roles" roleNameCol="role_name" />      -->      <!--      <Realm  className="org.apache.catalina.realm.JDBCRealm"             driverName="oracle.jdbc.driver.OracleDriver"          connectionURL="jdbc:oracle:thin:@ntserver:1521:ORCL"         connectionName="scott" connectionPassword="tiger"              userTable="users" userNameCol="user_name" userCredCol="user_pass"          userRoleTable="user_roles" roleNameCol="role_name" />      -->      <!--      <Realm  className="org.apache.catalina.realm.JDBCRealm"             driverName="sun.jdbc.odbc.JdbcOdbcDriver"          connectionURL="jdbc:odbc:CATALINA"              userTable="users" userNameCol="user_name" userCredCol="user_pass"          userRoleTable="user_roles" roleNameCol="role_name" />      -->      <!-- Define the default virtual host           Note: XML Schema validation will not work with Xerces 2.2.       -->      <Host appBase="webapps" autoDeploy="true" name="localhost" unpackWARs="true" xmlNamespaceAware="false" xmlValidation="false">        <!-- Defines a cluster for this node,             By defining this element, means that every manager will be changed.             So when running a cluster, only make sure that you have webapps in there             that need to be clustered and remove the other ones.