JServ

Apache JServ is a pure Java Servlet container. It includes a C module for the Apache web server that permits the use of multiple simultaneous servlet zones on multiple hosts. Various security schemes are also provided.

Apache JServ is an Open Source servlet container which is available in source and pre-compiled binary forms. Although initial configuration takes a fair amount of work, the results are very maintainable. There are two active components to JServ: the web server module (also called the "C" side) and the servlet engine (also called the "Java" side).

The web server module can be loaded dynamically (using Apache's DSO) or can be compiled into the web server. My experience has always been to compile the module into the web server. The web server module requires additional entries in the httpd.conf file or the inclusion of a jerv.conf file. The web server can be configured to automatically start and stop one instance of JServ as long as that instance is on the same physical server as the web server. The web server module configuration permits setting up various connections to JServ instances and servlet zones. File name extensions (such as ".weld") can be mapped to specific servlets to avoid the need to specify the servlet in the URL.

Each JServ instance needs a jserv.properties file. One of the parameters in this file is the "wrapper.classpath". Include the jacl.jar, tcljava.jar, and weld.jar in the wrapper.classpath.

Every servlet zone needs a zone.properties file. Each instance of the weld servlet (whose formal name is "us.oh.state.common.utility.TemplateProcessor") needs an "initArgs" setting for a "config" parameter. The initArgs=config=<file name> should be the absolute path to the WELD properties file, which details the configuration of WELD.

Contents

System Administration

Installing on UNIX

JServ

Previous: Apache | Next: Directories

Modified: Wed Apr 19 15:34:09 EDT 2000