| <html><head> |
| <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"> |
| <title>13.7 Configuring the Embedded Tomcat Servlet Container</title><link rel="stylesheet" href="css/stylesheet.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="Virgo User Guide"><link rel="up" href="ch13.html" title="13. Configuration"><link rel="prev" href="ch13s06.html" title="13.6 Configuring the Kernel and User Region"><link rel="next" href="ch13s08.html" title="13.8 Configuring the Web Integration Layer"><!--Begin Google Analytics code--><script type="text/javascript"> |
| var gaJsHost = (("https:" == document.location.protocol) ? "https://ssl." : "http://www."); |
| document.write(unescape("%3Cscript src='" + gaJsHost + "google-analytics.com/ga.js' type='text/javascript'%3E%3C/script%3E")); |
| </script><script type="text/javascript"> |
| var pageTracker = _gat._getTracker("UA-2728886-3"); |
| pageTracker._setDomainName("none"); |
| pageTracker._setAllowLinker(true); |
| pageTracker._trackPageview(); |
| </script><!--End Google Analytics code--></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">13.7 Configuring the Embedded Tomcat Servlet Container</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="ch13s06.html">Prev</a> </td><th width="60%" align="center">13. Configuration</th><td width="20%" align="right"> <a accesskey="n" href="ch13s08.html">Next</a></td></tr></table><hr></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="configuring-tomcat"></a>13.7 Configuring the Embedded Tomcat Servlet Container</h2></div></div></div><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><table border="0" summary="Note"><tr><td rowspan="2" align="center" valign="top" width="25"><img alt="[Note]" src="images/note.gif"></td><th align="left">Note</th></tr><tr><td align="left" valign="top">Virgo Nano uses the default Gemini Web configuration. The details described below may still apply.</td></tr></table></div><p> |
| Virgo |
| embeds an OSGi-enhanced version of the <a class="ulink" href="http://tomcat.apache.org/" target="_top">Tomcat Servlet Container</a> |
| in order to provide support for deploying Java EE WARs and OSGi <span class="emphasis"><em>Web Application Bundles</em></span>. |
| You configure the embedded Servlet container using the standard Apache Tomcat configuration. The main difference is that the configuration file is called <code class="filename">tomcat-server.xml</code> rather than <code class="literal">server.xml</code>. As with the other Virgo configuration files, the <code class="literal">tomcat-server.xml</code> file is located in the <code class="literal">$SERVER_HOME/configuration</code> directory. |
| Another difference is that not all standard Apache Tomcat configuration is supported in Virgo Server for Apache Tomcat: the restrictions are described in the |
| remainder of this section. |
| </p><p>Here's an extract of the default configuration distributed with the VTS. |
| </p><pre class="programlisting"><<span class="hl-tag">?xml version='1.0' encoding='utf-8'?</span>> |
| <<span class="hl-tag">Server</span> <span class="hl-attribute">port</span>=<span class="hl-value">"8005"</span> <span class="hl-attribute">shutdown</span>=<span class="hl-value">"SHUTDOWN"</span>> |
| |
| <<span class="hl-tag">Listener</span> <span class="hl-attribute">className</span>=<span class="hl-value">"org.apache.catalina.core.AprLifecycleListener"</span> <span class="hl-attribute">SSLEngine</span>=<span class="hl-value">"on"</span> /> |
| <<span class="hl-tag">Listener</span> <span class="hl-attribute">className</span>=<span class="hl-value">"org.apache.catalina.core.JasperListener"</span> /> |
| <<span class="hl-tag">Listener</span> <span class="hl-attribute">className</span>=<span class="hl-value">"org.apache.catalina.mbeans.GlobalResourcesLifecycleListener"</span> /> |
| |
| <<span class="hl-tag">Listener</span> <span class="hl-attribute">className</span>=<span class="hl-value">"org.eclipse.virgo.web.tomcat.ServerLifecycleLoggingListener"</span>/> |
| |
| <<span class="hl-tag">Service</span> <span class="hl-attribute">name</span>=<span class="hl-value">"Catalina"</span>> |
| <<span class="hl-tag">Connector</span> <span class="hl-attribute">port</span>=<span class="hl-value">"8080"</span> <span class="hl-attribute">protocol</span>=<span class="hl-value">"HTTP/1.1"</span> |
| <span class="hl-attribute">connectionTimeout</span>=<span class="hl-value">"20000"</span> |
| <span class="hl-attribute">redirectPort</span>=<span class="hl-value">"8443"</span> /> |
| |
| <<span class="hl-tag">Connector</span> <span class="hl-attribute">port</span>=<span class="hl-value">"8443"</span> <span class="hl-attribute">protocol</span>=<span class="hl-value">"HTTP/1.1"</span> <span class="hl-attribute">SSLEnabled</span>=<span class="hl-value">"true"</span> |
| <span class="hl-attribute">maxThreads</span>=<span class="hl-value">"150"</span> <span class="hl-attribute">scheme</span>=<span class="hl-value">"https"</span> <span class="hl-attribute">secure</span>=<span class="hl-value">"true"</span> |
| <span class="hl-attribute">clientAuth</span>=<span class="hl-value">"false"</span> <span class="hl-attribute">sslProtocol</span>=<span class="hl-value">"TLS"</span> |
| <span class="hl-attribute">keystoreFile</span>=<span class="hl-value">"configuration/keystore"</span> |
| <span class="hl-attribute">keystorePass</span>=<span class="hl-value">"changeit"</span>/> |
| |
| <<span class="hl-tag">Connector</span> <span class="hl-attribute">port</span>=<span class="hl-value">"8009"</span> <span class="hl-attribute">protocol</span>=<span class="hl-value">"AJP/1.3"</span> <span class="hl-attribute">redirectPort</span>=<span class="hl-value">"8443"</span> /> |
| |
| <<span class="hl-tag">Engine</span> <span class="hl-attribute">name</span>=<span class="hl-value">"Catalina"</span> <span class="hl-attribute">defaultHost</span>=<span class="hl-value">"localhost"</span>> |
| <<span class="hl-tag">Realm</span> <span class="hl-attribute">className</span>=<span class="hl-value">"org.apache.catalina.realm.JAASRealm"</span> <span class="hl-attribute">appName</span>=<span class="hl-value">"virgo-kernel"</span> |
| <span class="hl-attribute">userClassNames</span>=<span class="hl-value">"org.eclipse.virgo.kernel.authentication.User"</span> |
| <span class="hl-attribute">roleClassNames</span>=<span class="hl-value">"org.eclipse.virgo.kernel.authentication.Role"</span>/> |
| |
| <<span class="hl-tag">Host</span> <span class="hl-attribute">name</span>=<span class="hl-value">"localhost"</span> <span class="hl-attribute">appBase</span>=<span class="hl-value">"webapps"</span> |
| <span class="hl-attribute">unpackWARs</span>=<span class="hl-value">"false"</span> <span class="hl-attribute">autoDeploy</span>=<span class="hl-value">"false"</span> |
| <span class="hl-attribute">deployOnStartup</span>=<span class="hl-value">"false"</span> <span class="hl-attribute">createDirs</span>=<span class="hl-value">"false"</span>> |
| |
| <<span class="hl-tag">Valve</span> <span class="hl-attribute">className</span>=<span class="hl-value">"org.apache.catalina.valves.AccessLogValve"</span> <span class="hl-attribute">directory</span>=<span class="hl-value">"serviceability/logs/access"</span> |
| <span class="hl-attribute">prefix</span>=<span class="hl-value">"localhost_access_log."</span> <span class="hl-attribute">suffix</span>=<span class="hl-value">".txt"</span> <span class="hl-attribute">pattern</span>=<span class="hl-value">"common"</span> <span class="hl-attribute">resolveHosts</span>=<span class="hl-value">"false"</span>/> |
| |
| <<span class="hl-tag">Valve</span> <span class="hl-attribute">className</span>=<span class="hl-value">"org.eclipse.virgo.web.tomcat.ApplicationNameTrackingValve"</span>/> |
| <<span class="hl-tag">/Host</span>> |
| <<span class="hl-tag">/Engine</span>> |
| <<span class="hl-tag">/Service</span>> |
| <<span class="hl-tag">/Server</span>></pre><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="overview-tomcat-servlet-container"></a>Description of the Default Apache Tomcat Configuration</h3></div></div></div><p> |
| The following bullets describe the main elements and attributes in the default <code class="literal">tomcat-server.xml</code> file; for details about updating this file to further configure the embedded Apache Tomcat server, see the <a class="ulink" href="http://tomcat.apache.org/tomcat-7.0-doc/config/index.html" target="_top">Apache Tomcat Configuration Reference</a>. |
| </p><div class="tip" style="margin-left: 0.5in; margin-right: 0.5in;"><table border="0" summary="Tip: Relative paths"><tr><td rowspan="2" align="center" valign="top" width="25"><img alt="[Tip]" src="images/tip.gif"></td><th align="left">Relative paths</th></tr><tr><td align="left" valign="top"><p>If the configured path to a directory or file does not represent an absolute path, Virgo typically interprets it as a path relative to the <code class="filename">$SERVER_HOME</code> directory.</p></td></tr></table></div><div class="itemizedlist"><ul type="disc"><li><p>The root element of the <code class="literal">tomcat-server.xml</code> file is <code class="literal"><Server></code>. The attributes of this element represent the characteristics of the entire embedded Tomcat servlet container. The <code class="literal">shutdown</code> attribute specifies the command string that the shutdown port number receives via a TCP/IP connection in order to shut down the servlet container. The <code class="literal">port</code> attribute specifies the TCP/IP port number that listens for a shutdown message.</p></li><li><p>The <code class="literal"><Listener></code> XML elements specify the list of lifecycle listeners that monitor and manage the embedded Tomcat servlet container. Each listener class is a Java Management Extensions (JMX) MBean that listens to a specific component of the servlet container and has been programmed to do something at certain lifecycle events of the component, such as before starting up, after stopping, and so on.</p><p> The first four <code class="literal"><Listener></code> elements configure standard Tomcat lifecycle listeners. The listener implemented by the <code class="literal">org.eclipse.virgo.web.tomcat.ServerLifecycleLoggingListener</code> class is specific to Virgo Server for Apache Tomcat and manages server lifecycle logging. |
| </p></li><li><p>The <code class="literal"><Service></code> XML element groups together one or more connectors and a single engine. Connectors define a transport mechanism, such as HTTP, that clients use to to send and receive messages to and from the associated service. There are many transports that a client can use, which is why a <code class="literal"><Service></code> element can have many <code class="literal"><Connector></code> elements. The engine then defines how these requests and responses that the connector receives and sends are in turn handled by the servlet container; you can define only a single <code class="literal"><Engine></code> element for any given <code class="literal"><Service></code> element.</p><p> The sample <code class="literal">tomcat-server.xml</code> file above includes three <code class="literal"><Connector></code> elements: one for the HTTP transport, one for the HTTPS transport, and one for the AJP transport. The file also includes a single <code class="literal"><Engine></code> element, as required. |
| </p></li><li><p>The first connector listens for HTTP requests at the <code class="literal">8080</code> TCP/IP port. The connector, after accepting a connection from a client, waits for a maximum of 20000 milliseconds for a request URI; if it does not receive one from the client by then, the connector times out. If this connector receives a request from the client that requires the SSL transport, the servlet container automatically redirects the request to port <code class="literal">8443</code>. </p></li><li><p>The second connector is for HTTPS requests. The TCP/IP port that users specify as the secure connection port is <code class="literal">8443</code>. Be sure that you set the value of the <code class="literal">redirectPort</code> attribute of your non-SSL connectors to this value to ensure that users that require a secure connection are redirected to the secure port, even if they initially start at the non-secure port. The <code class="literal">SSLEnabled</code> attribute specifies that SSL is enabled for this connector. The <code class="literal">secure</code> attribute ensures that a call to <code class="literal">request.isSecure()</code> from the connecting client always returns <code class="literal">true</code>. The <code class="literal">scheme</code> attribute ensures that a call to <code class="literal">request.getScheme()</code> from the connecting client always returns <code class="literal">https</code> when clients use this connector. </p><p>The <code class="literal">maxThreads</code> attribute specifies that the servlet container creates a maximum of 150 request processing threads, |
| which determines the maximum number of simultaneous requests that can be handled. |
| The <code class="literal">clientAuth</code> attribute specifies that the servlet container does not require a certificate chain |
| unless the client requests a resource protected by a security constraint that uses CLIENT-CERT authentication. |
| </p><p>The <code class="literal">keystoreFile</code> attribute specifies the name of the file that contains the servlet container’s |
| private key and public certificate used in the SSL handshake, encryption, and decryption. |
| You use an alias and password to access this information. |
| In the example, this file is <code class="literal">$SERVER_HOME/configuration/keystore</code>. |
| The <code class="literal">keystorePass</code> attributes specify the password used to access the keystore. |
| </p></li><li><p>The third AJP Connector element represents a Connector component that communicates with a web connector via the AJP protocol. |
| </p></li><li><p>The engine has a logical name of <code class="literal">Catalina</code>; |
| this is the name used in all log and error messages so you can easily identify problems. |
| The value of the <code class="literal">defaultHost</code> attribute refers to the name of a <code class="literal"><Host></code> |
| child element of <code class="literal"><Engine></code>; |
| this host processes requests directed to host names on this servlet container. |
| </p></li><li><p>The <code class="literal"><Realm></code> child element of <code class="literal"><Engine></code> represents a database of |
| users, passwords, and mapped roles used for authentication in this service. Virgo Web Server uses an implementation of the Tomcat 6 Realm interface that authenticates users through the Java Authentication and Authorization Service (JAAS) framework which is provided as part of the standard J2SE API.</p><p>With the JAASRealm, you can combine practically any conceivable security realm with Tomcat's container managed authentication. For details, see <a class="ulink" href="http://tomcat.apache.org/tomcat-7.0-doc/realm-howto.html" target="_top">Realm Configuration</a>.</p></li><li><p>The <code class="literal"><Host></code> child element represents a virtual host, |
| which is an association of a network name for a server (such as <code class="literal">www.mycompany.com</code>) with the particular |
| server on which Catalina is running. |
| The servlet container unpacks Web applications into a directory hierarchy if they are deployed as WAR files. |
| </p><p> |
| Note that multiple <code class="literal"><Host></code> elements are not supported in Virgo Server for Apache Tomcat. |
| </p></li><li><p>Finally, the <code class="literal">org.apache.catalina.valves.AccessLogValve</code> valve creates log files |
| in the same format as those created by standard web servers. |
| The servlet container creates the log files in the <code class="literal">$SERVER_HOME/serviceability/logs/access</code> directory. |
| The log files are prefixed with the string <code class="literal">localhost_access_log.</code>, have a suffix of <code class="literal">.txt</code>, |
| use a standard format for identifying what should be logged, and do not include DNS lookups of the IP address of the remote host. |
| </p></li></ul></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="configuring-tomcat-connectors"></a>Connector Configuration</h3></div></div></div><p> The Virgo Server for Apache Tomcat supports the configuration of any connector supported by Apache Tomcat. |
| See the default configuration above for syntax examples, and for further details of the configuration properties |
| supported for various <code class="literal"><Connector></code> implementations, |
| consult the official <a class="ulink" href="http://tomcat.apache.org/tomcat-7.0-doc/config/http.html" target="_top">Tomcat HTTP Connector</a> documentation. |
| </p><div class="tip" style="margin-left: 0.5in; margin-right: 0.5in;"><table border="0" summary="Tip: Configuring SSL for Tomcat"><tr><td rowspan="2" align="center" valign="top" width="25"><img alt="[Tip]" src="images/tip.gif"></td><th align="left">Configuring SSL for Tomcat</th></tr><tr><td align="left" valign="top"><p> The Virgo Server for Apache Tomcat distribution includes a preconfigured <code class="filename">$SERVER_HOME/configuration/keystore</code> |
| file that contains a single self-signed SSL Certificate. |
| The password for this <code class="filename">keystore</code> file is <code class="literal">changeit</code>. |
| This <code class="filename">keystore</code> file is intended for testing purposes only. |
| For detailed instructions on how to configure Tomcat’s SSL support, |
| consult the official <a class="ulink" href="http://tomcat.apache.org/tomcat-7.0-doc/ssl-howto.html" target="_top">Tomcat SSL Configuration HOW-TO</a>. |
| </p></td></tr></table></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="configuring-tomcat-clustering"></a>Cluster Configuration</h3></div></div></div><p> |
| Virgo Server for Apache Tomcat supports standard Apache Tomcat cluster configuration. |
| By default, clustering of the embedded servlet container is disabled, |
| and the default configuration does not include any clustering information. |
| See <a class="ulink" href="http://tomcat.apache.org/tomcat-7.0-doc/cluster-howto.html" target="_top">Tomcat Clustering/Session Replication HOW-TO</a> |
| for detailed information about enabling and configuring clustering. |
| </p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="configuring-default-web-xml"></a>Default web.xml Configuration</h3></div></div></div><p> |
| Java Servlet specification enables web applications to provide deployment descriptor (<code class="literal">web.xml</code>) in the <code class="literal">WEB-INF</code> directory. |
| Apache Tomcat introduces a default <code class="literal">web.xml</code> which is similar to web application's <code class="literal">web.xml</code>, but provides configurations that are applied to all web applications. |
| When deploying a web application, Apache Tomcat uses the default <code class="literal">web.xml</code> file as a base configuration. |
| If the web application provides its own configurations via <code class="literal">web.xml</code> (the one located in the web application's <code class="literal">WEB-INF</code>) or annotations, they overwrite the default ones. |
| In Virgo Server for Apache Tomcat you can also provide default configurations for all web applications. |
| If you want to change/extend the default configurations, you can provide the default <code class="literal">web.xml</code> file located in the <code class="literal">VTS_HOME/configuration</code> directory. |
| </p><p> |
| </p><div class="tip" style="margin-left: 0.5in; margin-right: 0.5in;"><table border="0" summary="Tip"><tr><td rowspan="2" align="center" valign="top" width="25"><img alt="[Tip]" src="images/tip.gif"></td><th align="left">Tip</th></tr><tr><td align="left" valign="top">Be careful when changing/extending the default <code class="literal">web.xml</code> as this will affect all web applications.</td></tr></table></div><p> |
| </p><p> |
| Here's an extract of the default configuration distributed with the VTS. |
| </p><pre class="programlisting"><<span class="hl-tag">?xml version="1.0" encoding="ISO-8859-1"?</span>> |
| <<span class="hl-tag">web-app</span> <span class="hl-attribute">xmlns</span>=<span class="hl-value">"http://java.sun.com/xml/ns/javaee"</span> |
| <span class="hl-attribute">xmlns:xsi</span>=<span class="hl-value">"http://www.w3.org/2001/XMLSchema-instance"</span> |
| <span class="hl-attribute">xsi:schemaLocation</span>=<span class="hl-value">"http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_3_0.xsd"</span> |
| <span class="hl-attribute">version</span>=<span class="hl-value">"3.0"</span>> |
| |
| <<span class="hl-tag">servlet</span>> |
| <<span class="hl-tag">servlet-name</span>>default<<span class="hl-tag">/servlet-name</span>> |
| <<span class="hl-tag">servlet-class</span>>org.apache.catalina.servlets.DefaultServlet<<span class="hl-tag">/servlet-class</span>> |
| <<span class="hl-tag">init-param</span>> |
| <<span class="hl-tag">param-name</span>>debug<<span class="hl-tag">/param-name</span>> |
| <<span class="hl-tag">param-value</span>>0<<span class="hl-tag">/param-value</span>> |
| <<span class="hl-tag">/init-param</span>> |
| <<span class="hl-tag">init-param</span>> |
| <<span class="hl-tag">param-name</span>>listings<<span class="hl-tag">/param-name</span>> |
| <<span class="hl-tag">param-value</span>>false<<span class="hl-tag">/param-value</span>> |
| <<span class="hl-tag">/init-param</span>> |
| <<span class="hl-tag">load-on-startup</span>>1<<span class="hl-tag">/load-on-startup</span>> |
| <<span class="hl-tag">/servlet</span>> |
| |
| <<span class="hl-tag">servlet</span>> |
| <<span class="hl-tag">servlet-name</span>>jsp<<span class="hl-tag">/servlet-name</span>> |
| <<span class="hl-tag">servlet-class</span>>org.apache.jasper.servlet.JspServlet<<span class="hl-tag">/servlet-class</span>> |
| <<span class="hl-tag">init-param</span>> |
| <<span class="hl-tag">param-name</span>>fork<<span class="hl-tag">/param-name</span>> |
| <<span class="hl-tag">param-value</span>>false<<span class="hl-tag">/param-value</span>> |
| <<span class="hl-tag">/init-param</span>> |
| <<span class="hl-tag">init-param</span>> |
| <<span class="hl-tag">param-name</span>>xpoweredBy<<span class="hl-tag">/param-name</span>> |
| <<span class="hl-tag">param-value</span>>false<<span class="hl-tag">/param-value</span>> |
| <<span class="hl-tag">/init-param</span>> |
| <<span class="hl-tag">load-on-startup</span>>3<<span class="hl-tag">/load-on-startup</span>> |
| <<span class="hl-tag">/servlet</span>> |
| |
| <<span class="hl-tag">servlet-mapping</span>> |
| <<span class="hl-tag">servlet-name</span>>default<<span class="hl-tag">/servlet-name</span>> |
| <<span class="hl-tag">url-pattern</span>>/<<span class="hl-tag">/url-pattern</span>> |
| <<span class="hl-tag">/servlet-mapping</span>> |
| |
| <<span class="hl-tag">servlet-mapping</span>> |
| <<span class="hl-tag">servlet-name</span>>jsp<<span class="hl-tag">/servlet-name</span>> |
| <<span class="hl-tag">url-pattern</span>>*.jsp<<span class="hl-tag">/url-pattern</span>> |
| <<span class="hl-tag">/servlet-mapping</span>> |
| |
| <<span class="hl-tag">servlet-mapping</span>> |
| <<span class="hl-tag">servlet-name</span>>jsp<<span class="hl-tag">/servlet-name</span>> |
| <<span class="hl-tag">url-pattern</span>>*.jspx<<span class="hl-tag">/url-pattern</span>> |
| <<span class="hl-tag">/servlet-mapping</span>> |
| |
| <<span class="hl-tag">session-config</span>> |
| <<span class="hl-tag">session-timeout</span>>30<<span class="hl-tag">/session-timeout</span>> |
| <<span class="hl-tag">/session-config</span>> |
| |
| <<span class="hl-tag">mime-mapping</span>> |
| <<span class="hl-tag">extension</span>>abs<<span class="hl-tag">/extension</span>> |
| <<span class="hl-tag">mime-type</span>>audio/x-mpeg<<span class="hl-tag">/mime-type</span>> |
| <<span class="hl-tag">/mime-mapping</span>> |
| ...... |
| <<span class="hl-tag">mime-mapping</span>> |
| <<span class="hl-tag">extension</span>>ppt<<span class="hl-tag">/extension</span>> |
| <<span class="hl-tag">mime-type</span>>application/vnd.ms-powerpoint<<span class="hl-tag">/mime-type</span>> |
| <<span class="hl-tag">/mime-mapping</span>> |
| |
| <<span class="hl-tag">welcome-file-list</span>> |
| <<span class="hl-tag">welcome-file</span>>index.html<<span class="hl-tag">/welcome-file</span>> |
| <<span class="hl-tag">welcome-file</span>>index.htm<<span class="hl-tag">/welcome-file</span>> |
| <<span class="hl-tag">welcome-file</span>>index.jsp<<span class="hl-tag">/welcome-file</span>> |
| <<span class="hl-tag">/welcome-file-list</span>> |
| |
| <<span class="hl-tag">/web-app</span>> |
| </pre><p> |
| The following bullets describe the main elements in the default <code class="literal">web.xml</code> file. |
| </p><div class="itemizedlist"><ul type="disc"><li><p>The <code class="literal"><Servlet></code> XML element declares a given servlet and its configurations. The sample <code class="literal">web.xml</code> file above includes two <Servlet> elements.</p><div class="itemizedlist"><ul type="circle"><li><p> |
| The default servlet serves static resources and processes the requests that are not mapped to any servlet. |
| For details about default servlet configuration, see the <a class="ulink" href="http://tomcat.apache.org/tomcat-7.0-doc/default-servlet.html" target="_top">Apache Tomcat Default Servlet Reference.</a>. |
| </p></li><li><p> |
| The jsp servlet serves the requests to JavaServer Pages. It is mapped to the URL pattern "*.jsp" and "*.jspx". |
| For details about jsp servlet configuration, see the <a class="ulink" href="http://tomcat.apache.org/tomcat-7.0-doc/jasper-howto.html" target="_top">Apache Tomcat Jasper 2 JSP Engine.</a>. |
| </p></li></ul></div></li><li><p>The <code class="literal"><servlet-mapping></code> XML element specifies the mapping between the servlet and URL pattern.</p></li><li><p> |
| The <code class="literal"><session-config></code> XML element defines the session configuration for one web application. |
| The sample <code class="literal">web.xml</code> file above specifies that the session timeout for all web applications will be 30 minutes by default. |
| </p></li><li><p> |
| The <code class="literal"><mime-mapping></code> XML element defines a mapping between a filename extension and a mime type. |
| When serving static resources, a "Content-Type" header will be generated based on these mappings. |
| </p></li><li><p> |
| The <code class="literal"><welcome-file-list></code> XML element specifies a list of welcome files. |
| When a request URI refers to a directory, the default servlet looks for a "welcome file" within that directory. |
| If the "welcome file" exists it will be served, otherwise 404 status or directory listing will be returned, depending on the default servlet configuration. |
| </p></li></ul></div><p> |
| </p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="configuring-tomcat-contexts"></a>Context Configuration</h3></div></div></div><p> |
| Virgo Server for Apache Tomcat supports standard Apache Tomcat web application context configuration. |
| The <a class="ulink" href="http://tomcat.apache.org/tomcat-7.0-doc/config/index.html" target="_top">Apache Tomcat Configuration Reference</a> has a section on |
| <a class="ulink" href="http://tomcat.apache.org/tomcat-7.0-doc/config/context.html" target="_top">The Context Container</a> which describes the mechanism that |
| is used in VTS for searching context configuration files and details the context configuration properties. |
| </p><p> |
| Context configuration files may be placed in the following locations, |
| where <code class="literal">[enginename]</code> is the name of Tomcat's engine ('Catalina' by default) and <code class="literal">[hostname]</code> names |
| a virtual host ('localhost' by default), both of which are configured in <code class="literal">tomcat-server.xml</code>: |
| </p><div class="itemizedlist"><ul type="disc"><li><p> |
| <code class="literal">$SERVER_HOME/configuration/context.xml</code> provides the default context configuration file for all web applications. |
| </p></li><li><p> |
| The <code class="literal">$SERVER_HOME/configuration/[enginename]/[hostname]</code> directory may contain: |
| </p><div class="itemizedlist"><ul type="circle"><li><p> |
| The default context configuration for all web applications of a given virtual host in the file <code class="literal">context.xml.default</code>. |
| </p></li><li><p> |
| Individual web applications' context configuration files as described in the Apache Tomcat Configuration Reference. |
| For example, the context for a web application with |
| context path <code class="literal">foo</code> may be configured in <code class="literal">foo.xml</code>. |
| </p></li></ul></div><p> |
| </p></li></ul></div><p> |
| </p><p> |
| Note that the following context configuration features are not supported in Virgo Server for Apache Tomcat: |
| </p><div class="itemizedlist"><ul type="disc"><li><p> |
| Custom class loaders. |
| </p></li><li><p> |
| Specifying the context path. This is specified using the <code class="literal">Web-ContextPath</code> header in the web application's |
| <code class="literal">MANIFEST.MF</code> file. |
| </p></li><li><p> |
| Specifying the document base directory. |
| </p></li></ul></div><p> |
| </p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="configuring-jsp-compilation"></a>JSP Compilation</h3></div></div></div><p> |
| By default Apache Tomcat compiles JSP files in web applications agains Java 1.6. |
| In order to enable JSP compilation against Java 1.7 for your web application, |
| additional init parameters (<code class="literal">compilerSourceVM</code> and <code class="literal">compilerTargetVM</code>) should be added for the <code class="literal">org.apache.jasper.servlet.JspServlet</code> configuration. |
| For details about <code class="literal">org.apache.jasper.servlet.JspServlet</code> configuration, see the <a class="ulink" href="http://tomcat.apache.org/tomcat-7.0-doc/jasper-howto.html" target="_top">Apache Tomcat Jasper 2 JSP Engine</a>. |
| <code class="literal">org.apache.jasper.servlet.JspServlet</code> configuration can be provided with the web application's web.xml. |
| </p><pre class="programlisting"><<span class="hl-tag">?xml version="1.0" encoding="ISO-8859-1"?</span>> |
| <<span class="hl-tag">servlet</span>> |
| <<span class="hl-tag">servlet-name</span>>jsp<<span class="hl-tag">/servlet-name</span>> |
| <<span class="hl-tag">servlet-class</span>>org.apache.jasper.servlet.JspServlet<<span class="hl-tag">/servlet-class</span>> |
| <<span class="hl-tag">init-param</span>> |
| <<span class="hl-tag">param-name</span>>compilerSourceVM<<span class="hl-tag">/param-name</span>> |
| <<span class="hl-tag">param-value</span>>1.7<<span class="hl-tag">/param-value</span>> |
| <<span class="hl-tag">/init-param</span>> |
| <<span class="hl-tag">init-param</span>> |
| <<span class="hl-tag">param-name</span>>compilerTargetVM<<span class="hl-tag">/param-name</span>> |
| <<span class="hl-tag">param-value</span>>1.7<<span class="hl-tag">/param-value</span>> |
| <<span class="hl-tag">/init-param</span>> |
| <<span class="hl-tag">init-param</span>> |
| <<span class="hl-tag">param-name</span>>fork<<span class="hl-tag">/param-name</span>> |
| <<span class="hl-tag">param-value</span>>false<<span class="hl-tag">/param-value</span>> |
| <<span class="hl-tag">/init-param</span>> |
| <<span class="hl-tag">init-param</span>> |
| <<span class="hl-tag">param-name</span>>xpoweredBy<<span class="hl-tag">/param-name</span>> |
| <<span class="hl-tag">param-value</span>>false<<span class="hl-tag">/param-value</span>> |
| <<span class="hl-tag">/init-param</span>> |
| <<span class="hl-tag">load-on-startup</span>>3<<span class="hl-tag">/load-on-startup</span>> |
| <<span class="hl-tag">/servlet</span>> |
| <<span class="hl-tag">servlet-mapping</span>> |
| <<span class="hl-tag">servlet-name</span>>jsp<<span class="hl-tag">/servlet-name</span>> |
| <<span class="hl-tag">url-pattern</span>>*.jsp<<span class="hl-tag">/url-pattern</span>> |
| <<span class="hl-tag">url-pattern</span>>*.jspx<<span class="hl-tag">/url-pattern</span>> |
| <<span class="hl-tag">/servlet-mapping</span>> |
| </pre></div></div><!--Begin LoopFuse code--><script src="http://loopfuse.net/webrecorder/js/listen.js" type="text/javascript"></script><script type="text/javascript"> |
| _lf_cid = "LF_48be82fa"; |
| _lf_remora(); |
| </script><!--End LoopFuse code--><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="ch13s06.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="ch13.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="ch13s08.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">13.6 Configuring the Kernel and User Region </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> 13.8 Configuring the Web Integration Layer</td></tr></table></div></body></html> |
