The following requirements exist for building Apache JServ:
The complete Apache JServ installation requires less than 2Mb of hard disk space. The compiled, not-compressed jar archive is more or less 100Kb.
Apache JServ 1.1 works only with the Apache HTTP Server (only version 1.3.x is supported).
A fully compliant Java 1.1 or greater Runtime Environment is required for Apache JServ to execute. The official list of compatible ports is found on Sun's Java web site. The list of supported platforms and Java ports can be found here.
Note: since Apache JServ uses only standard Java APIs (
please, do not submit a bug report if your Java virtual machine fails to execute Apache
JServ because of broken compliance. Send it to your Java virtual machine implementers.
The JavaSoft JSDK 2.0 is required by Apache JServ for proper servlet execution. This package is freely available from Sun's Java Servlet web site
NOTE: this version of Apache JServ requires exactly the 2.0 version of the JSDK in order to operate properly. Any other version (past, present or future and including the version that comes with the Java Server Pages (JSP) jar file) is not supported.
Any compiler compatible with the Java 1.1 or greater specification. A list of supported Java compilers may be found here.
NOTE: to build servlets, a Java compiler is needed. The Jikes compiler from IBM is a fast and easy to use replacement for Sun's slower javac compiler.
Make sure you have an ANSI-C compiler installed and relative Make tools. The GNU C compiler (GCC version 2.7.2 is fine) or the EGCS C compiler (the future of the GCC compiler) and GNU Make (make preferably version 3.75) from the Free Software Foundation (FSF) is recommended. If you don't have GCC then at least make sure your vendors compiler is ANSI compliant. You can find the homepage of GNU at http://www.gnu.org/ and the GCC distribution under http://www.gnu.org/order/ftp.html . EGCS is available from http://egcs.cygnus.com/
See your Apache documentation for more information on how to add DSO support and if your system is supported. You will need to make sure that Perl 5.004 or later is installed in order to build DSO modules because of the dependency on the Apache apxs module.
There are two choices:
If you are using a source distribution then you have to configure Apache first (some generated header files are needed for Apache JServ to pass its configure checks). You do not need to worry about specifying the Apache JServ module for this first run.
Thus, a first time configure line to build a static version of Apache would look like this:
If you are using DSO then you can ignore this step. If you have a source distribution and would like to build it with DSO support and install it for use by Apache JServ then use the following options when configuring Apache:
Thus, a first time configure line to build a DSO version of Apache would look like this:
Now you are ready to configure Apache JServ. To do this you may (or may not) need to specify quite a few arguments to configure. The options to pass to Apache JServ's configure are described below with complete examples at the very bottom of this section.
For DSO use:
Note: The configure script will check a the default installation directory, /usr/local/apache. If you have Apache already installed in there, you may leave this argument out.
For a static compile use:
Note: Do not try to use both --with-apxs and --with-apache-src options at the same time. Also, Apache JServ 1.0, used --with-apache-install. This has been deprecated and you should now use --with-apxs instead.
'make install' will copy the documentation and Apache JServ .jar file into the directory that you specify with this option:
The default value for this option is /usr/local/jserv
By default configure will first look at the JDK_HOME and JAVA_HOME environment variables, if they aren't set then configure will check your PATH environment variable. The results from using the PATH can be overriden by:
If they are not found, configure will tell you and default back to whatever is in your PATH.
It is also possible to specify the locations of the java binaries and force Java 2 usage with the following options:
--with-java-platform=1 or 2 (generally no need to specify this)
Note: By default, debugging symbols are left out of the Apache JServ classes, you can put them back in by using this option:
Note: By default the jar file is not compressed, this can be changed like so:
Apache JServ needs to know where your servlet classes are. You will need to specify them like so:
If you are using mod_ssl, then you should enable EAPI support by adding:
An example configure line for STATIC compilation is:
An example configure line for DSO compilation is:
Once you have configured Apache JServ you can run make.
Run 'make install' to make a .jar file, and copy it and the docs into the directory you specified as --prefix. If you are building the DSO version, this will compile the shared object. If you are building the static version, this will just build the Java classes.
If you are using an Apache source distribution then you also have to run 'make install' in the Apache source directory to build Apache with Apache JServ support in it. To do this, you will need to add the following line to the static configure line in section 3 above:
This is an example of building a default Apache installation with Apache JServ support added:
You can see if Apache has loaded the mod_jserv module by executing '/path/to/apache/installation/bin/httpd -l'.
At this point, you must configure the Apache JServ directives for Apache. There are example configuration files in the conf and example directories that come with the Apache JServ package that help with this process. The files in the example directory will help you configure a default zone named "example" so that your URL's will look like this:<http://www.yourserver.com/example/Hello>
There are three different types of configuration files for Apache JServ, the first one should be included in your httpd.conf file with the Apache "Include" directive. For example, in your httpd.conf file, you should have a line like this: "Include /path/to/jserv.conf".
Within your "jserv.conf" file, there is a line that gives the path to the second type of configuration file, the "jserv.properties" file. The line in the jserv.conf file looks like this: "ApJServProperties /path/to/jserv.properties".
Lastly, within the "jserv.properties" file is a line that points to your zone configuration file. If you have a zone called "example", then you will need to have an "example.properties" file and the location to this file is then defined with this line in your "jserv.properties" file: "example.properties=/path/to/file/example.properties"
Thus, the configuration file path looks like this:
"->" sounds like "points to"
httpd.conf -> jserv.conf -> jserv.properties -> example.properties
You should make sure to edit all of these files and fill in the appropriate information according to the comments provided in each of the files. If you have questions about the definitions, you should consult section 8 below, the documentation in the docs directory, on the website, FAQ-O-Matic and/or the Java Apache Users mailing list.
First, look in the various log files for errors. If you are not getting log files created, then this is generally a result of incorrect permissions on the log files. Make sure that the user (ie: nobody) that the Apache httpd is running as can write to the log files.
Next, read the FAQ-O-Matic and documentation to see if your issues have already been covered (there is a good chance that they have been).
Configuration errors and questions are not considered bugs and those should be directed to the Java Apache Users mailing list.
If think that you have found a bug, please report it to the Apache Bug Database at:
Copyright (c) 1997-99 The Java Apache Project.
$Id: howto.unix_install.html,v 1.9 1999/12/10 23:25:45 admin Exp $
All rights reserved.