|Configuring the JMS server||Configuring and administering the Apache Geronimo Server||Customizing server assemblies|
The Web container in a Geronimo server is an integrated Tomcat or Jetty server. You can configure the embedded web container by using different GBeans. This can be done either from the administration console or by editing configuration files.
Starting from v2.2, Geronimo leverages
server.xml from Tomcat for ease usability. Configurations to Web listeners, Clustering, and Tomcat Engine can be achieved through the same process as for a standalone Tomcat Web container. However, for configurations such as Valves, virtual hosts, JNDI and so on, you will use the GBean approach just like in Geronimo v2.1.
- Adding new listeners — From this portlet, you can add new listeners and change the status (stop, start, delete) of the existing ones.
- Configuring session manager of Tomcat — you can swap inactive sessions to a file or just forget them. You can keep a certain number of sessions in main memory configurable via System configuration as follows.
- Configuring virtual host — Geronimo provides different distribution with Web Contaniners such as Tomcat and Jetty. You can look into the following pages to learn how to configure virtual host together with Geronimo.
- Managing Valve — In Tomcat, a valve is a Java class that can be inserted into the request processing pipeline. A valve executes as part of Tomcat's servlet container and is independent of the Web application.