The information in this document is subject to change without notice.
Warranty Disclaimer. HEWLETT-PACKARD MAKES NO WARRANTY OF ANY KIND WITH REGARD TO THIS INFORMATION, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. Hewlett-Packard shall not be liable for errors contained herein or for direct, indirect, special, incidental or consequential damages in connection with the furnishing, performance
or use of this material.
Restricted Rights Legend. Use, duplication or disclosure by the U.S. Government is subject to restrictions as set forth in subparagraph (c) (1) (ii) of the Rights in Technical Data and Computer Software clause at DFARS 252.227-7013 for DOD agencies. Rights for non-DOD U.S. Government Department and Agencies are as set forth in FAR 52.227-19 (c)(1,2).
Copyright Notices. Copyright Hewlett-Packard Company 2001-2008. This document contains information which is protected by copyright. All Rights Reserved. Reproduction, adaptation, or translation without prior written
permission is prohibited, except as allowed under the copyright laws.
Trademark Notices. UNIX is a registered trademark in the United States and other countries, licensed exclusively through X/Open Company Limited.
Intel® ItaniumTM Processor Family is a trademark of Intel Corporation in the U.S. and other countries and is used under license.
Java and all Java-based trademarks and logos are trademarks or registered trademarks of Sun Microsystems, Inc. in the U.S. and other countries.
Microsoft®, Windows®, MS Windows® and Windows NT ® are U.S. registered trademarks of Microsoft Corp. Netscape is a U.S. trademark of Netscape Communications Corporation.
Oracle ® is a registered U.S. trademark of Oracle Corporation, Redwood City, California.
Acknowledgements. This product includes software developed by the Apache Software Foundation
This documentation is based on information from the Apache Software Foundation (http://www.apache.org).
This product includes software developed by the OpenLDAP Project (http://www.openldap.org).
This guide covers the migration from HP Apache-based Web Server Suite 2.x to HP-UX Web Server Suite 3.x on servers running 11i (PA-RISC) and HP-UX 11i Version 2 or later, Itanium Processor Family (IPF).
This guide can be used to:
Understand the differences between HP Apache-based Web Server Suite 2.x and HP-UX Web Server Suite3.x.
Install the HP-UX Web Server Suite3.x.
Migrate the configuration of your HP Apache-based Web Server from Version 2.x to HP-UX Web Server Suite3.x.
Verify that your HP-UX Web Server Suite migration was successful.
The guide is broadly divided in to three sections:
Section 2: Quick guide to migration solutions
Section 3-7: Detailed Installation and Migration steps
Appendixes: A complete listing of module changes
2 Quick Guide to Migration Solutions
This section includes four solutions to migrate from the HP UX Web Server Suite 2.x to the HP-UX Web Server Suite 3.x. Solutions A and B are simple installations that require basic knowledge of Apache. If you have customized Apache, see the detailed sections later in the document. Solutions C and D are complex; you must be familiar with Apache's configuration files.
2.1 Quick Guide Assumptions
2.x refers to HP Apache-based Web Server Suite 2.x.
hpuxws refers to HP-UX Web Server Suite 3.x.
Files are in their default locations. For example:
2.x is installed in the default locations:
= /opt/hpws22/apache and = /opt/hpws22/tomcat
HP-UX Web Server Suite 3.x is installed in the following default locations:
= /opt/hpws22/apache = /opt/hpws22/tomcat
The Apache documents are available at /hpws_docs and
/opt/hpws22/hp _docs /apache.
The Tomcat documents are available at /hpws_docs and /opt/hpws22/hp_docs/tomcat. The Webmin documents are available at /opt/hpws22/hp_docs/webmin.
(Note: The file /opt/hpws22/util/altroot. sh can be used to move Apache's root. Type "altroot.sh -h" for help with the script)
The customer does not need IPv6 support.
2.2 Preliminary Steps
2.2.1 HP-UX Web Server Suite 3.x Requirements The minimum requirements are:
11i, 11i version 1.5, or later.
90 MB of disk. 190MB of disk space for all four components installed.
To install the HP-UX Web Server Suite, perform the following procedure:
For example, if you are using HP Apache 2.x. then enter as the root user: /opt/hpws/apache/bin/apachectl/opt/apache/bin/apachectl stop
Verify that all httpd processes have stopped:
ps -e | grep httpd
C. Install the suite using the HP SW Depot Web Release:
software.hp.com/ - Featured Products- HP-UX Apache-based Web Server. OR software.hp.com/ search for "HP Apache-based Web Server". The latest versions are always available online from the HP SW Depot.
The latest versions are always available online from the HP SW Depot.
You can also install using the HP-UX 11 iv2 or v3 Application Release CDs (when available).
2.3 Running WSS 2.x and WSS 3.x on a single system
Solutions A and B are two methods of installation.
2.3.1 Solution A: Running the server on a single system consecutively
No additional steps are required if you have installed the HP-UX WSS 3.x on a system that already has WSS 2.x. Both of them can coexist on a single system. However, because they use the same port assignments, they cannot be run at the same time without conflicting with each other. You could run both the versions of WSS on the same machine by following the steps mentioned in the section below.
2.3.2 Solution B: Running the server on a single system concurrently
In order to run both Apache 2.2.x and Apache 2.0.x at the same time, you would have the change the ports on which they get executed so that the two Apaches do not conflict with each other. By default both these versions using the same port. Here is how you can change the port number using ports.sh .
Here we are documenting how you can change the port number by taking Apache 2.2.x as an example.
Please enter the posts.sh command as mentioned below:
The following output is displayed which whill show the information about the server configuration files :
Apache installed at /opt/hpws22/apache Tomcat installed at /opt/hpws22/tomcat Webmin installed at /opt/hpws/webmin
Default locations of configuration files are displayed as:
In addition, to use PATH_INFO, you must explicitly set the AcceptPathInfo directive, otherwise a 404 response is returned.
The method of invoking mod_proxy has changed.
See http://httpd.apache.org/docs/2.2/mod/mod_httpd.apache.org/docs-2.0/mod/mod proxy.html.
For example in 2.0.x you do:
But in HP-UX Apache-based Web Server you do:
To enable suexec, you must load the mobile with
LoadModule suexec _module module s/mod _suexec. so
Also, setup the following directive:
SuexecUserGroup TheUser TheUsersGroup
See http://httpd.apache.org/docs/2.2/mod/mod_httpd.apache.org/docs-2.0/mod/mod suexec.html.
This module is the connector used by Apache to communicate with the Tomcat servlet container. Modjk replaces the modjserv connector, which is used by the Apache JServ servlet engine. To enable this, uncomment the line #Include conf/mod_jk.conf in
/opt/hpws /apache / conf/httpd. conf.
For more information, see http://tomcat.apache.org/connectors-doc/ .
Many new character sets have been added to the HP-UX Apache-based Web Server. There were 8 character sets earlier and now there are 28. For more information, http://httpd.apache.org/docs/2.2/mod/mod_see httpd.apache.org/docs
AddHandler type-map var
This command was commented out earlier. This is now enabled, by default, to allow the Apache "It Worked" page (http://yourserver.com/index.html) to be distributed in multiple languages.
The ASF documentation states that this directive must now have a closing quote. For example: ErrorDocument 403 “Some Message”
You must enable the following if you want to use "Web-based Distributed Authoring and Versioning" (WebDAV) methods with Microsoft WebFolders.
BrowserMatch "Microsoft Data Access Internet Publishing Provider" redirect-carefully BrowserMatch " ^WebDrive" redirect-carefully
See mod _dav above.
The new VersionSort option enables numerical sorting rather than alphabetical sorting. IndexOptions FancyIndexing VersionSort
ReadmeName and HeaderName
These directives determine the filename to be appended and prepended to the directory listing. The defaults have been changed from README and HEADER to README.html and HEADER.html.
Continue with the "Directives Common to C & D Solutions" section below.
2.4.3 Directives Common to C & D Solutions The following directives apply to Solutions C and D.
The ServerType directive has been eliminated because the HP-UX Web Server Suite can only be ServerType standalone.
The Listen directive is now required and the Port directive has been eliminated. For example, if you had set Port 80 earlier, change it to Listen 80.
The ServerName directive now supercedes the functionality of the Port directive. If no ServerName or associated port number is indicated, Apache will try to deduce them. For reliablity and predictability purposes, you must explicitly set the servername and port. For example:
ServerName yourserver.com: 80.
Process handling directives.
See Migrating Process Handling.
StartServers and ThreadsPerChild
These values have not been changed because the number of child processes is dynamically set based on load.
This is the maximum number of simultaneous client connections. Performance is based on transactions per second and is indirectly related to MaxClients. Therefore, this value remains the same.
This directive sets the limit on the number of requests that an individual child server process will handle. After the MaxRequestsPerChild directive requests, the child process will die. If it is set to 0, the process will never die. If you load modules that are not distributed by HP, you may have memory leaks. To prevent memory leaks, set the MaxRequestsPerChild directive to, for example, 500 so that the process will die and the memory will be freed. To maximize the performance of the HP-UX Apache-based Web Server, set it to 0.
MinSpareThreads and MaxSpareThreads
Child processes are created until the number of idle threads is greater than MinSpareThreads. Child processes are killed until the number of idle threads is less than MaxSpareThreads. The default values are compatible with most servers. If you have extremely high loads, increase the values of MinSpareThreads and MaxSpareThreads. This does not increase the number of transactions per second but it will lower the impact of especially demanding transactions on other less demanding ones.
MinSpareServers and MaxSpareServers
These have been replaced with MinSpareThreads and MaxSpareThreads.
Modules not in HP-UX Apache-based Web Server distribution
Verify that you have the same modules in LoadModule as you had in 2.0.x. The modules are not compatible with the HP-UX Web Server Suite and will need to be recompiled.
rewritten. For more information, see Writing 2.x Modules in the aaa directory have been renamed and offer better support for digest authentication. For example, mod_auth is now split into mod_auth_basic and mod_authn_file; mod_auth_dbm is now called mod_authn_dbm; mod_access has been renamed mod_authz_host. There is also a new mod_authn_alias module for simplifying certain authentication configurations.
This module is a port of the 2.0 mod_auth_ldap module to the 2.2 Authn/Authz framework. New features include using LDAP attribute values and complicated search filters in the Require directive.
A new module that authorizes access to files based on the owner of the file on the file system
A new module that allows configuration blocks to be enabled based on the version number of the running server.
Added a new ?config argument which will show the configuration directives as parsed by Apache, including their file name and line number. The module also shows the order of all request hooks and additional build information, similar to httpd -V.
Added a support for RFC 2817, which allows connections to upgrade from clear text to TLS encryption.
mod_imap has been renamed to mod_imagemap to avoid user confusion.
mod_digest has been renamed to mod_auth_digest.
mod_proxy, mod_cache, mod_disk_cache, and mod _file _cache
mod_proxy has been decomposed to a more logical structure with separate modules. The cache functionality has been split to other cache modules, such as mod_cache, mod_disk_cache, and mod_file_cache. Generally, these modules use similar cache directives as used in the old mod_proxy.
For more information, see Migrating Common Gateway Interface (CGI) and
You can improve CGI performance by enabling the CGI daemon (cgid) module instead of cgi: LoadModule cgid _module modules/mod _cgid. so
#LoadModule cgi _module module s/mod _cgi. so
You must enable the Scriptsock directive, which defines the UNIX socket for communicating with cgid.
mod_define has been eliminated. The Define directive enables you to set a variable for later use in the configuration file. A future module may implement this functionality.
For more information, see Migrating Logging.
AgentLog, RefererLog, and RefererIgnore
The logging directives AgentLog, RefererLog, and RefererIgnore have been removed. These directives are now replaced with the LogFormat and CustomLog directives.
K. mod _ssl
SSL configuration is in a separate configuration file called httpd-ssl . conf.
The default session cache is now:
SSLSessionCache shmcb:logs/ssl_scache (512000)
ca-bundle . crt is not distributed with the HP-UX Apache-based Web Server. You can use the certmig tool to extract ca certificates from a Netscape client. For example: /opt/hpws22/apache/util/test_certmig. sh -E -d $HOME/ .netscape
See /opt/hpws/hp _docs/apache/utilities .user. guide.