|Home > Documentation > Configuring and administering > Configuring and administering the Apache Geronimo Server > Configuring a remote Apache HTTP server|
|Clustering and farming||Configuring and administering the Apache Geronimo Server||Configuring EJB Containers|
At the time of writing this article, the Apache mod_jk Configuration portlet provided in the Geronimo Administration Console presented some unconsistencies recognizing the already installed web applications. As a workaround, this article covers two alternative ways to configure a remote Apache HTTP server.
Apache Geronimo comes in two flavors depending on the Web container you decide to use. You can choose between the Tomcat or Jetty distributions. 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.
As we already mentioned, this article covers two different ways on how Apache HTTPd can be configured to forward client requests to Geronimo, which is configuring it as a reverse proxy by using the "built-in" mod_proxy module or configuring the Jakarta Tomcat Connector mod_jk available with the Apache Tomcat source.
Based on these two alternatives, this article is organized in the following sections:
In order to set a common ground for this configuration example, here is a list with the versions tested: