Abstract
Tomcat is a servlet and JavaServer Pages (JSP) container that is used in the official Reference Implementation for the Java servlet and JSP technologies. The Java servlet and JSP specifications are developed by Sun under the Java Community Process.
Tomcat is developed in an open and participatory environment. It is released under the Apache Software License. Tomcat is intended to be a collaboration of the best-of-breed developers from around the world.
The iSeries server supports Tomcat Version 3.2.4 as a component of the IBM HTTP Server for iSeries (5722-DG1). It is maybe not so surprising that the HTTP Server (powered by Apache) Admin graphical user interface (GUI) also uses the built-in Jakarta Tomcat servlet container engine at Version 3.2.4 to generate the content.
Why would you spend extra time and effort to bring Tomcat Version 4.1 to your iSeries?
Tomcat 4.1, in comparison to Version 3.2, brings a lot of enhancements to your iSeries server. It implements the Servlet 2.3 and JSP 1.2 specifications as well as HTTP 1.1, AJP 1.3 and Java Native Interface (JNI) support. For a complete listing of the old and new functions, see the Jakarta Tomcat home page at:
http://jakarta.apache.org/tomcat
Jakarta Tomcat Version 4.1 on the iSeries server is not supported by IBM. This tip provides the instructions for you to download a public domain open-source copy of ASF Tomcat so you can implement the new functions on your iSeries server. This tip also documents what you need, to bring the new version of Tomcat to your iSeries server.
Contents
The following information was extracted from HTTP Server (powered by Apache): An Integrated Solution for IBM ~ iSeries Servers, SG24-6716, which is currently a draft redbook (Redpiece). This redbook has more details and provides step-by-step instructions. You can access the latest version from the IBM Redbooks Web site at:
Search for SG24-6716.
Software prerequisites
At the time this tip was written, the latest available version of Jakarta Tomcat was Version 4.1.24, which we use for this implementation. Here is a detailed list of all software requirements:
- 5722-SS1, OS/400 at V5R2 (although the same basic steps should work on an iSeries server at V5R1)
- 5722-SS1 Option 30, OS/400 - Qshell Interpreter
Note: An OS/400 program temporary fix (PTF) corrects several Qshell problems. We recommend that you install the following PTF for your server release:
- V5R1: SI08114
- V5R2: SI08117
- 5722-DG1, IBM HTTP Server for iSeries: This is not mandatory, because Jakarta Tomcat Version 4 has a built-in Web server that can serve the included examples. Nevertheless we highly recommend it, so that you can configure your HTTP Server (powered by Apache) to connect to the Tomcat servlet engine.
- 5722-JV1, Developer Kit for Java
- 5722-JV1 Option 5, Java Developer Kit 1.3: The Jakarta Tomcat server needs this in order to run.
- Binary distribution of Jakarta Tomcat Version 4.1.24: You can download this from the Web at:
http://jakarta.apache.org/builds/jakarta-tomcat-4.0/release/v4.1.24/bin/
Tip: We used the binary ZIP distribution (file named jakarta-tomcat-4.1.24.zip) of Tomcat 4 for the installation. We encountered errors that cannot be reproduced when using the .tar.gz distribution. If you do not have ZIP available on your iSeries server, see "Bringing Zip and Unzip to OS/400 PASE and Qshell Environments”, TIPS0283.
- Jakarta Tomcat connector mod_jk for AJP 1.3 on your iSeries server: You can download this as a ready made savefile from:
http://jakarta.apache.org/builds/jakarta-tomcat-connectors/jk/release/
Select the version of mod_jk that you need. We tested with V1.2.3. Version V1.2.4 was just made available. Click bin/ -> iseries/ to find the zipped iSeries savefile.
Tip: There are differences between your choice of V1.2.3, V1.2.4, and V1.2.5 that should be coming soon. For example, starting with mod_jk V1.2.3, mod_deflate works well with mod_jk (at least when using AddOutputFilterByType). This combination can make the output of your Tomcat 4 servlets and JSPs very small. For details, read the documentation found at the Jakarta Tomcat connector Web site (mentioned earlier in this point).
Special Notices
This material has not been submitted to any formal IBM test and is published AS IS. It has not been the subject of rigorous review. IBM assumes no responsibility for its accuracy or completeness. The use of this information or the implementation of any of these techniques is a client responsibility and depends upon the client's ability to evaluate and integrate them into the client's operational environment.