...
The communication between the HTTP server and Geronimo can be also done via AJP connectors. By default, both Apache Geronimo distributions (Jetty and Tomcat) have already predefined one AJP v13 listener, the ports where these listeners are defined varies from one distribution to the other.
- For Jetty the default AJP13 listener port is 8019
- For Tomcat the default AJP13 listener port is 8009
This section will cover the configuration for both Geronimo distributions as the steps are very similar (if not equal)AJP13 connector listening on port 8009.
The Jakarta Tomcat Connector mod_jk module is provided as a connector from Apache Tomcat source, Jetty (and obviously Tomcat) is fully compatible with this connector. This module is avaiable when you download the Tomcat source, but also is available for download separately, refer to the following URL for the proper version for your system.
http://tomcat.apache.org/download-connectors.cgi
In addition to the mod_jk you will require the a workers.properties file, also available with the Apache Tomcat source distribution. This properties file tells the mod_jk plugin how to connect to the Geronimo server. For a detailed explanation on all the available options for configuring the Jakarta Tomcat Connector visit the following URL:
http://tomcat.apache.org/connectors-doc/config/workers.html
Info |
---|
For practical purposes, the module mod_jk_1.-apache-2.6_2.03.50.dllso for Windows and the workers.properties are included in the Attachments section in this article. |
...
Download the appropriate mod_jk for your platform from the Tomcat web site, . For this particular example rename it to mod_jk.dll (or .so depending on your platform) and copy it into the <httpd_home>\modules directory. Download and extract the workers.properties from the Apache Tomcat source (alternatively, download it from the Attachments section) to the <httpd_home>\conf directory.
...
No Format | ||||
---|---|---|---|---|
| ||||
LoadModule jk_module modules/mod_jk.dllso # Loads the Jakarta Tomcat Connector module JkWorkersFile <httpd_home>\conf\workers.properties # Tells the module the location of the workers.properties file JkLogFile <httpd_home>\logs\mod_jk.log # Specifies the location for this module's specific log file JkLogLevel info # Sets the module's log level to info JkLogStampFormat "[%a %b %d %H:%M:%S %Y] " # Sets the module's log time stamp format JkAutoAlias <httpd_home>\config-store # Automatically Alias webapp context directories into the Apache document space. JkMount /console/* ajp13 # Sets a mount point from a context to a Tomcat worker. In this case will allow access (forward the request) to the console. |
...
No Format | ||||
---|---|---|---|---|
| ||||
worker.ajp13.type=ajp13 workers.java_home=<java_home> # Sets the JAVA_HOME ps=\ # For Windows systems use back slash "\" , for Unix systems use forward slash "/" worker.ajp13.port=8009 # Use default 8009 for Apache Tomcat # Change this value to 8019 for Jetty version of AJP used. The AJP listeners defined in Geronimo are AJP v13. worker.ajp13.host=localhost # Specifies the location of the Geronimo server. Use default localhost for single-tier scenarios. Specify the hostname of the Geronimo server for multi-tier environments. worker.ajp13.typeport=ajp138009 # SetsBoth theTomcat versionand ofJetty AJPcome used.with Thea AJPpredefined listenersAJP13 definedlistener inon Geronimo are AJP v13.port 8009 |
From this example note how the name of the worker is defined, look at the variables definition worker.ajp13.* , ajp13 is the worker name you specified earlier in the httpd.conf.
...
- Check Geronimo connectivity by accessing http://localhost:8080/console , you should see the Geronimo Administration Console.
- Check HTTPd connectivity by accessing http://localhost , you should see the Apache HTTPd welcome page.
- Check the HTTPd - Geronimo request forwarding by accessing http://localhost/console/ , you shoud be redirected to the Geronimo Administration Console. Note at the end of the URL there is a "/", failing to include this / will result in a Not Found error triggered by the Jakarta Tomcat Connector module.
...