This topic is about how to set up intermediary services with Geronimo.
- Clustering and farming — These topics are about how to set up a cluster and perform server farming.
- Configuring a remote Apache HTTP server — If you want to place a Apache HTTP server (HTTPd) in front of Geronimo, you will have to configure it in such a way that it can forward client requests to Geronimo.
- Configuring EJB Containers — An Enterprise JavaBeans(EJB) container is used to provide a runtime environment for enterprise beans within the application server. The container handles operation of EJBs and also acts as an intermediary between the business logic layer and the rest of the Java EE environment.
- Configuring JAX-WS engine — Apache Geronimo is distributed with two JAX-WS engines: Apache Axis2 http://ws.apache.org/axis2/ and Apache CXF http://incubator.apache.org/cxf/.
- Configuring the JMS server — To configure the JMS Server, select JMS Server on the Console Navigation menu on the left side. You will get a list of JMS brokers available in the server and their status in the JMS Server Manager portlet. You will also be presented with the JMS Network Listeners portlet that displays all JMS network connectors.
- Configuring the Web Container — 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.
- Customizing server assemblies — Geronimo has always been a flexible, component-based server environment that allowed lightweight server images to be custom built for specific application environments – minimizing server footprint and reducing server startup time.