Binaries are available for Linux and Win32 under the bin directory where you obtained the Tomcat distribution file. For Linux, mod_jk is available as mod_jk.so. For Win32, -mod_jk is available as mod_jk.dll. If there isn't a prebuilt mod_jk available or +mod_jk is available as mod_jk.dll. + +

If there isn't a prebuilt mod_jk available or you wish to build your own copy, you can build it yourself from the source. -First, download the Source Distribution for Tomcat. There are a large number -of files in the download directory, but the only one you need is jakarta-tomcat. +First, download the Source Distribution for Tomcat. There are a large number +of files in the download directory, but the only one you need is +jakarta-tomcat[.zip|.tar.Z|.tar.gz].

On NT

@@ -237,9 +240,35 @@

For Apache

Make sure you have Perl 5 installed. The apxs script used to build the module is written in Perl. -
Change directory to jakarta-tomcat/src/native/apache1.3 (or apache2.0). -
Run the apxs command that came with your apache distribution (hint: look in /usr/local/apache/bin, /usr/sbin, or wherever you intalled apache). Type the command all on one line.

+
Make sure you have Perl 5 installed. The apxs script + used to build the module is written in Perl. + +
Change directory to + jakarta-tomcat/src/native/apache1.3 (or apache2.0). + +
Build mod_jk.so.

+ + Following are three alternate techniques you can try, in order of + simplicity. + +
- Option 1: Run ./build-unix.sh . This script will set some + variables, call apxs as below, and try to copy mod_jk.so to + $APACHE_HOME/libexec. If it fails, you may need to do the following: +
  - set JAVA_HOME in your shell, e.g. "set JAVA_HOME=/usr/local/jdk1.2.2; export JAVA_HOME"
  - set APACHE_HOME in your shell, e.g. "set APACHE_HOME=/usr/local/apache; export APACHE_HOME"
  - uncomment the following line in the build-unix.sh file, + replacing "linux" with the name of your platform as specified in the + Java include directory for your installation +
    +# JAVA_INCLUDE="-I ${JAVA_HOME}/include -I ${JAVA_HOME}/include/linux" +
    +
- Option 2: If build-unix.sh fails, you may have better luck with the + Makefiles in the same directory. E.g. "make -f Makefile.linux mod_jk.so" +
- Option 3: Finally, you can try to build it manually. Run the apxs command that came with your apache distribution (hint: look in /usr/local/apache/bin, /usr/sbin, or wherever you intalled apache). Type the command all on one line.
  
  For Solaris:
  
  apxs -o mod_jk.so -DSOLARIS -I../jk -I/usr/java/include -I/usr/java/include/solaris -c *.c ../jk/*.c
  On some systems, this will build the module correctly, but will fail at runtime with a "symbol "fdatasync" not found". To fix, add -lposix4 just before the -c in the above command.
  
  @@ -247,8 +276,12 @@
  apxs -o mod_jk.so -I../jk -I/usr/local/jdk/include -I/usr/local/jdk/include/linux -c *.c ../jk/*.c
  Your build may fail because the object files from the ../jk directory have been compiled to the current directory, rather than their source directory. Running gcc -shared -o mod_jk.so *.o should finish the build.
  
  (If you've installed Java in another directory, adjust accordingly). For other *nixes you should be able to work it out, but remember that the order of the arguments to apxs is important!. +
- Copy mod_jk.so to Apache's libexec directory
Copy mod_jk.so to Apache's libexec directory. (Note that + build-unix.sh attempts to do this, but you may have to "su root" + first.)

For other Webservers

@@ -268,7 +301,7 @@ <Parameter name="port" value="8009"/> </Connector> -The servlet.xml file already has a block similar to this for Ajp12 connections on port 8007 (as delivered by mod_jserv). Even if you think you're only using Ajp13, you probably don't want to delete this connector - it's required to shut down Tomcat. +The server.xml file already has a block similar to this for Ajp12 connections on port 8007 (as delivered by mod_jserv). Even if you think you're only using Ajp13, you probably don't want to delete this connector - it's required to shut down Tomcat.

Tomcat 3.3: The default location of mod_jk.conf and +mod_jk.conf-auto has changed. They are now in +TOMCAT_HOME/conf/jk/mod_jk.conf and +TOMCAT_HOME/conf/jk/mod_jk.conf-auto. +

On NT

For Apache

For other Webservers

4. Defining "workers"

Configuring workers manually.