September 2008 Migration Guide

Download 1.14 Mb.
Hajmi1.14 Mb.
  1   2   3   4   5   6   7   8   9   10   11


P-UX Web Server

September 2008

Migration Guide


M igration Guide

HP-UX WSS 2.x to


Sept 18, 2008

Table of Contents

Legal Notices

1 Using this Guide 7

2 Quick Guide to Migration Solutions 8

2.1 Quick Guide Assumptions 8

2.2 Preliminary Steps 8

2.2.1 HP-UX Web Server Suite Requirements 8

2.2.2 HP-UX Web Server Suite Installation 8

and HP-UX Web Server Suite on the same machine 8

2.3.1 Solution A: Running on the SAME machine but at DIFFERENT times. 8

2.3.2 Solution B: Running on the SAME machine at the SAME time. 8

2.4 Modifying httpd.conf 9

2.4.1 Solution C: Migrating to HP-UX Web Server Suite using the NEW HP-UX Web Server Suite

configuration files as a base 9

base. 9

2.4.3 Directives Common to C & D Solutions 11

2.5 Start 12

2.6 Verify 12

3 Getting More Information 13

4 What’s New and Changed in HP-UX Web Server Suite 15

4.1 File Location Differences Between HP Apache 4.2 Version and Module Numbers 16

4.3 New Multi-Processing Module in HP-UX Apache-based Web Server 17

4.4 Summary of New Features in the HP-UX Web Server Suite 17

5 Preparing for Installing HP-UX Web Server Suite 24

5.1 Hardware and Software Requirements 24

5.2 Disk Space Requirements 24

5.3 Perl Requirements 24

5.4 Java Development Kit (JDK) Requirements 25

5.5 Java Servlet Development Kit (JSDK 2.x) 25

6 Installing HP-UX Web Server Suite 26

6.1 Installing HP-UX Web Server Suite on a Server Where 7.1 Migrating the HP Apache Core 31

7.1.1 Migrating Process Handling 31

7.1.2 Migrating Module Loading 33

Migrating Logging 34

7.1.4 Migrating the Printing of Error Messages 34

7.1.5 Migrating Port Number Assignments 35

7.1.6 Migrating Access to Configuration Files 36

7.2 Migrating Included Modules 37

7.2.1 Migrating mod_proxy 37

7.2.2 Migrating How Documents are Cached by Proxy Servers 37

7.3 Migrating Security 37

7.3.1 Migrating SSL 37

7.3.2 Migrating Chroot 38

7.4 Migrating Scripting Modules 38

7.4.1 Migrating PHP 39

7.4.2 PHP Oracle support in HP-UX Apache-based Web Server 39

7.4.3 Migrating Perl 39

7.4.4 Migrating Common Gateway Interface (CGI) 40

7.4.5 Migrating Server-Side Includes (SSI) 40

7.5 Migrating Java 41

7.5.1 Migrating Tomcat with modjserv to Tomcat with modjk 41

7.5.2 Migrating JServ to Tomcat 43

7.5.3 Methods to Enable Servlets in Tomcat 45

7.6 Other Migration Tasks 45

7.6.1 Migrating the Selection of Server Type 45

7.6.2 Migrating Webmin 46

7.7 Migrating the Printing of Virtual Host Configuration 52

7.8 Writing 2.x Modules 52

7.8.1 Module Configuration 52

7.8.2 Handlers 56

7.8.3 Directives List 57

7.8.4 Initialization and Exiting 57

7.8.5 Functions and Types 58

7.8.6 Header files 60

7.8.7 Bibliography 60

7.9 Miscellaneous Changes 61

8 Tuning HP-UX Web Server Suite Performance 62

8.1 Basic HTTP 62

8.2 SSL 62

8.3 PHP 62

8.4 Tomcat 63

9 Verifying the Migration 65

10 Appendix 66

10.1 Directive Changes by Name 66

10.2 Module Changes 66

10.2.1 Core 66

10.2.2 auth _ldap 66

10.2.3 mod_auth_dbm 66

10.2.4 mod_auth_digest 66

10.2.5 mod_autoindex 66

10.2.6 mod_case_filter and mod_case_filterjn 66

10.2.7 mod_cgid 66

10.2.8 mod_dav and mod_dav_fs 66

10.2.9 mod_define 66

10.2.10 mod_echo 66

10.2.11 mod_env 66

10.2.12 mod_ext_filter 66

10.2.13 mod_headers 66

10.2.14 mod _include 66

10.2.15 modjk 66

10.2.16 modjserv 66

10.2.17 mod_log_agent 66

10.2.18 mod_log_config 66

10.2.19 mod_log_referer 66

10.2.20 mod_mime 66

10.2.21 mod_negotiation 66

10.2.22 mod_perl 66

10.2.23 mod_proxy, mod_cache, mod_disk_cache, and mod_file_cache 66

10.2.24 mod_file_cache 66

10.2.25 mod_setenvif 66

10.2.26 mod_ssl 66

10.2.27 mod_suexec 66

10.2.28 mod_usertrack 66

10.2.29 mod_vhost_alias 66

Sept 18, 2008

Version 1



Apache Software Foundation


Certificate Authority


HP-UX Web Server Suite

HP Apache

HP Apache-based Web Server


Itanium Processor Family


Internet Protocol Version 6


Java Development Kit


Java Runtime Environment


Lightweight Directory Access Protocol


Multi-Processing Module


Precision Architecture, Reduced Instruction Set Computing


PHP Hypertext Preprocessor


RSA Security Inc.


Web-based Distributed Authoring and Versioning

Document History

Legal Notices

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 (

This product includes software developed by the OpenLDAP Project (

This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (http://www.openssl .org).

This product includes cryptographic software written by Eric Young (eay(ã

This product includes software developed by the Java Apache Project for use in the Apache JServ Servlet Engine (

This product includes software developed by Ralf S. Engelschall (rse(ã for use in the mod_ssl project (

This product includes software developed by Ralf S. Engelschall (rse(ã This product includes PHP, available from (

1 Using this Guide

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

  1. 2.x refers to HP Apache-based Web Server Suite 2.x.

hpuxws refers to HP-UX Web Server Suite 3.x.

  1. 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
= /opt/hpws22/webmin
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 " -h" for help with the script)

  1. 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.

  • Perl 5.8.8

  • Java JDK or later

2.2.2 HP-UX Web Server Suite Installation

To install the HP-UX Web Server Suite, perform the following procedure:

  1. Stop Apache.

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

  1. Verify that all httpd processes have stopped:

ps -e | grep httpd

C. Install the suite using the HP SW Depot Web Release: - Featured Products- HP-UX Apache-based Web Server. OR 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 .

Here we are documenting how you can change the port number by taking Apache 2.2.x as an example.

Please enter the 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:

Apache: /opt/hpws22/apache/conf/httpd. Apache(SSL):/opt/hpws22/apache/conf/extra/ssl.conf

LDAP: /opt/hpws22/apache/conf/ldap.

Tomcat: /opt/hpws22/tomcat/conf/server.

mod_jk: /opt/hpws22/apache/conf/mod_jk.conf

mod_jk: /opt/hpws22/apache/conf/

Webmin: /opt/hpws/webmin/conf/miniserv.conf

The following ports have been identified as used for a server:

HTTP port: HTTPS port: Tomcat ports: Webmin port: LDAP port:

80 443 8005 10000 389



Go to each file and manually change the port numbers. For example:

HTTP port:


HTTPS port:

8443 (note 1)

Tomcat ports:


Webmin port:


LDAP port:

389 (note 2)

Note 1. Your SSL URL must be in the form because you are no longer using the standard SSL port.

Note 2. The LDAP port does not change because it is the LDAP server's port. The HP Apache-based Web Server or HP-­UX Apache-based Web Server is an LDAP client.

2.4 Modifying httpd.conf

Solutions C and D are migration methods based on opposite philosophies. Method C edits the new configuration files to correspond to your needs. Method D edits copies of your old files.

2.4.1 Solution C: Migrating to HP-UX Web Server Suite using the NEW HP-UX Web Server Suite configuration files as base.

  1. Save a copy of /opt/hpws22/apache/conf/httpd.conf .

  2. Find the differences between the configuration files. For example:

diff /opt/hpws/apache/conf/httpd.conf /opt/hpws22/apache/conf/httpd.conf

  1. Edit the /opt/hpws22/apache/conf/httpd.conf file based on differences.

  2. Edit the /opt/hpws/apache/conf/httpd.conf file.

  3. Skip to the Directives Common to C & D Solutions section.

2.4.2 Solution D: Migrating to HP-UX Web Server Suite using the OLD 2.0.x configuration files as base.

  1. Save a copy of /opt/hpws22/apache/conf/httpd.conf

  2. Copy your 2.0 httpd.conf file to the /opt/hpws22/apache/conf/httpd.conf.old.

  3. Find the differences between the old and new configuration files.

  4. Edit /opt/hpws22/apache/conf/httpd.conf based on the differences.

  5. LoadModule

The module location has changed from the libexec to modules directory. Therefore, you must replace libexec with modules in the "Dynamic Shared Object (DSO) Support" section.

  1. mod _dav

This module enables "Web-based Distributed Authoring and Versioning" (webDAV)

For more information, see the FAQ at

  1. mod _perl

The process to enable Perl has been modified. In the HP-UX Apache-based Web Server "ModPerl: :" has replaced "Apache::". The new method is:

PerlModule ModPerl: :Registry

SetHandler perl-script

PerlHandler ModPerl: :Registry: :handler

Options ExecCGI

PerlOptions ParseHeaders

  1. mod_php

Enabling PHP has changed. For example, in 2.0.x, you entered:

AddType application/x-httpd-php . php

AddType application/x-httpd-php-source .phps

However, in the HP-UX Apache-based Web Server, enter:

SetOutputFilter PHP

SetInputFilter PHP

In addition, to use PATH_INFO, you must explicitly set the AcceptPathInfo directive, otherwise a 404 response is returned.

  1. mod _proxy

The method of invoking mod_proxy has changed.

See proxy.html.

For example in 2.0.x you do:


But in HP-UX Apache-based Web Server you do:


  1. mod _suexec

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 suexec.html.

  1. mod_jk

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 .

L. AddCharset

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, 

2.0/mod/mod mime.html#addcharset

  1. AddHandler type-map var

This command was commented out earlier. This is now enabled, by default, to allow the Apache "It Worked" page ( to be distributed in multiple languages.

  1. ErrorDocument

The ASF documentation states that this directive must now have a closing quote. For example: ErrorDocument 403 “Some Message”

Currently, if you omit the closing quote, no error is reported but this may change in the future.

  1. BrowserMatch

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.

  1. IndexOptions

The new VersionSort option enables numerical sorting rather than alphabetical sorting. IndexOptions FancyIndexing VersionSort

  1. 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.

  1. 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.

  1. ServerType

The ServerType directive has been eliminated because the HP-UX Web Server Suite can only be ServerType standalone.

  1. Port

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.

  1. ServerName

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 80.

  1. 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.

  • MaxClients

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.

  • MaxRequestsPerChild

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.

  1. 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.

  1. Authn/Authz

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.

  1. mod_authnz_ldap

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.

  1. mod_authz_owner

A new module that authorizes access to files based on the owner of the file on the file system

  1. mod_version

A new module that allows configuration blocks to be enabled based on the version number of the running server.

  1. mod_info

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.

  1. mod_ssl

Added a support for RFC 2817, which allows connections to upgrade from clear text to TLS encryption.

  1. mod_imagemap

mod_imap has been renamed to mod_imagemap to avoid user confusion.

  1. mod_auth_digest

mod_digest has been renamed to mod_auth_digest.

  1. 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.

  1. mod _cgi.

For more information, see Migrating Common Gateway Interface (CGI) and cgid.html.

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.

Scriptsock logs/cgisock

  1. mod_define

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.

  1. Logging directives.

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.

  • Logging directives have changed

SSLLog and SSLLogLevel have been removed. Use Apache logging directives ErrorLog and LogLevel instead.

2.5 Start

To start Apache, as root type:

/opt/hpws22/apache/bin/apachectl start

2.6 Verify

In a browser enter the URL:

Download 1.14 Mb.
  1   2   3   4   5   6   7   8   9   10   11

Download 1.14 Mb.

Bosh sahifa

    Bosh sahifa

September 2008 Migration Guide

Download 1.14 Mb.