Helma Logo
main list history

Configuring Jetty in Helma 1.x

Due to the recent update to Jetty 6.1 in Helma the options described in this document only apply to Helma versions <=1.6.3.

To obtain better control over Jetty in a Helma installation the following patch enables Jetty to be configured from an XML file called jetty.xml in Helma's installation directory.

An example file is provided, too, configuring a NCSA log file, a generic listener on port 8080, an AJP listener on port 8009, a static context for Helma's static directory, a password protected context running two Jetty servlets as well as an SSL listener on port 8443.

For the latter one, you also need the jetty.keystore file which contains two self-signed certificates for the host names and localhost.

To try it out apply the patch to the Helma source and drop the other two attached files into the Helma installation directory. You should disable any definitions of HTTP or AJP ports in the start script or properties file to avoid interference with Helma's settings.

The patch adds the argument -c defining the location of the configuration file to the launcher.jar command-line invocation:

   java -jar launcher.jar -c jetty.xml

Note: Starting with Helma 1.6.3 the -c switch is officially available. Applying the patch is only necessary if you are using an older version.

After restarting Helma you still should be able to connect to Helma either directly via http://localhost:8080 or from within Apache (e.g. using mod_jk or mod_proxy_ajp) via http://localhost:8009

The secure server should be available via https://localhost:8443 – you probably need to define some security exceptions in your browser due to the self-signed certificates.

More information about the XML configuration capabilities is available at the Jetty 5 site. I did not find official API docs for this version, only these ones at http://www.dpml.net/api/jetty/5.1.6/.

jetty.xmlundefined bytes
jetty.keystoreundefined bytes
jettyXmlConfiguration.patchundefined bytes