CSWS_JAVA for HP Secure Web Server for OpenVMS (based on Apache) Installation Guide and Release Notes

This document provides an Installation Guide and Release Notes for CSWS_JAVA Version 3.0 for HP Secure Web Server for OpenVMS (Alpha and I64), released November 2005. It is based on Apache Tomcat 5.5.9.

Key Components and Features: CSWSJAVA integrates Apache Tomcat (Catalina), Ant, and Jspc to provide a robust Java servlet container and JSP environment. Version 3.0 supports JavaServer Pages 2.0 and Java Servlet 2.4, offering improved performance, scalability, stability, and enhanced platform integration. It can run as an extension to the HP Secure Web Server or as a standalone server. The MOD_JK and MOD_JK2 adapters facilitate communication between Apache and Tomcat. A key architectural requirement is that CSWSJAVA must be installed on an ODS-5 enabled disk to properly handle case-sensitive and long filenames, preventing servlet namespace collisions, although the Secure Web Server can remain on an ODS-2 disk.

Prerequisites: Installation requires OpenVMS Alpha 7.3-2 or higher (or I64 8.2 or higher), Secure Web Server Version 1.3-1 or 2.1 or higher (though Tomcat can run standalone), and the Java SDK for OpenVMS Platform v1.4.2 (with all required patches).

Installation & Configuration: The installation process involves several pre-installation steps such as shutting down existing web services, removing previous CSWS_JAVA or Apache JServ versions (support for JServ was retired since V2.0), and then using the PRODUCT INSTALL CSWS_JAVA command to install it on the designated ODS-5 volume. Post-installation, the APACHE$JAKARTA_CONFIG utility is crucial for setup, including:

• Changing the Jakarta directory ownership (e.g., to APACHE$WWW) for secure web server integration.
• Configuring MOD_JK2 support to link Apache and Tomcat.
• Adjusting Java Virtual Machine (JVM) parameters and CLASSPATH entries, typically via a .TOMCATRC file. Manual modification of APACHE$JAKARTA_CONFIG.COM is required if using Java SDK v1.5.0 instead of the officially supported v1.4.2.

Important Notes & Troubleshooting:

• Users may need to increase OpenVMS system quotas (FILLM, PGFLQUO, BYTLM) for optimal Java application performance.
• The initial invocation of the Tomcat server can be slow as it deploys all applications; this can be mitigated by deleting unnecessary subdirectories in the webapps directory.
• Errors during initial shared memory creation on the first run are often resolved by simply restarting both CSWS and CSWS_JAVA.
• Using the -SECURITY parameter when starting CSWS_JAVA Version 3.0 will prevent the Apache Tomcat process from starting.