Migration Guide

 

HP Apache-based Web Server Version 1.3.x to

2.xrthellaHP-UX Web Server Suite

 

 

 

 

June July 2724SeptemberDecemberJanuary 316August 128154, 20032


 

 

 

                                                                                   

 

 

 

 

 

 

 

 

 

 

 

 

 


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

2.3        Running 1.3.x 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

2.4.2     Solution D: Migrating to HP-UX Web Server Suite using your OLD 1.3.x configuration files as a 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 1.3.x and HP-UX Web Server Suite. 15

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 1.3.x is Not Running. 26

6.2        Installing HP-UX Apache-based Web Server on a Server Concurrently Running 1.3.x. 28

7      Migrating Your  Apache Configuration from 1.3.x to HP-UX Apache-based Web Server 31

7.1        Migrating the HP Apache Core. 31

7.1.1     Migrating Process Handling. 31

7.1.2     Migrating Module Loading. 33

7.1.3     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 mod_jserv to Tomcat with mod_jk. 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_filter_in. 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     mod_jk. 66

10.2.16     mod_jserv 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

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  rthellaHP-UX Web Server Suite Requirements  8

2.2.2  rthellaHP-UX Web Server Suite  Installation  8

2.3  Running 1.3.x and hpws 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 rthellaHP-UX Web Server Suite using the NEW rthellaHP-UX Web Server Suite configuration files as a base.  9

2.4.2  Solution D: Migrating to rthellaHP-UX Web Server Suite using your OLD 1.3.x configuration files as a 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 rthellaHP-UX Web Server Suite  15

4.1  File Location Differences Between HP Apache 1.3.x and rthellaHP-UX Web Server Suite  15

4.2  Version and Module Numbers  16

New Multi-Processing Module in rthellaHP-UX Web Server Suite. 18

4.3  Summary of New Features in the rthellaHP-UX Web Server Suite  18

5  Preparing for Installing rthellaHP-UX Web Server Suite  24

5.1  HP Apache 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) Requirements  25

6  Installing rthellaHP-UX Web Server Suite  26

6.1  Installing rthellaHP-UX Web Server Suite on a Server Where 1.3.x is Not Running  26

6.2  Installing rthellaHP-UX Web Server Suite on a Server Concurrently Running 1.3.x  28

7  Migrating Your HP Apache Configuration from 1.3.x to rthellaHP-UX Web Server Suite  31

7.1  Migrating the HP Apache Core  31

7.1.1  Migrating Process Handling  31

7.1.2  Migrating Module Loading  33

7.1.3  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 rthellaHP-UX Web Server Suite  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 mod_jserv to Tomcat with mod_jk  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 rthellaHP-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  70

10.2.1  Core  70

10.2.2  auth_ldap  70

10.2.3  mod_auth_dbm  71

10.2.4  mod_auth_digest  71

10.2.5  mod_autoindex  71

10.2.6  mod_case_filter and mod_case_filter_in  72

10.2.7  mod_cgid  72

10.2.8  mod_dav  and mod_dav_fs  73

10.2.9  mod_define  73

10.2.10  mod_echo  73

10.2.11  mod_env  73

10.2.12  mod_ext_filter  74

10.2.13  mod_headers  74

10.2.14  mod_include  74

10.2.15  mod_jk  75

10.2.16  mod_jserv  75

10.2.17  mod_log_agent  76

10.2.18  mod_log_config  76

10.2.19  mod_log_referer  76

10.2.20  mod_mime  76

10.2.21  mod_negotiation  77

10.2.22  mod_perl  77

10.2.23  mod_proxy, mod_cache, mod_disk_cache, and mod_file_cache  78

10.2.24  mod_file_cache  79

10.2.25  mod_setenvif  79

10.2.26  mod_ssl  80

10.2.27  mod_suexec  80

10.2.28  mod_usertrack  80

10.2.29  mod_vhost_alias  80

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  2.x Requirements  8

2.2.2  2.x Installation  8

2.3  Running 1.3.x and 2.x 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 2.x using the NEW 2.x configuration files as a base.  9

2.4.2  Solution D: Migrating to 2.x using your OLD 1.3.x configuration files as a 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 Apache-based Web Server 2.x  15

4.1  File Location Differences Between HP Apache 1.3.x and 2.x  15

4.2  Version and Module Numbers  16

4.3  New Multi-Processing Module in HP Apache 2.x  17

4.4  Summary of New Features in the HP Apache Version 2.x  17

5  Preparing for Installing HP Apache 2.x  20

5.1  HP Apache Hardware and Software Requirements  20

5.2  Disk Space Requirements  20

5.3  Perl Requirements  20

5.4  Java Development Kit (JDK) Requirements  21

5.5  Java Servlet Development Kit (JSDK 2.x) Requirements  21

6  Installing HP Apache 2.x  22

6.1  Installing HP Apache 2.x on a Server Where 1.3.x is Not Running  22

6.2  Installing HP Apache 2.x on a Server Concurrently Running 1.3.x  24

7  Migrating Your HP Apache Configuration from 1.3.x to 2.x  27

7.1  Migrating the HP Apache Core  27

7.1.1  Migrating Process Handling  27

7.1.2  Migrating Module Loading  29

7.1.3  Migrating Logging  30

7.1.4  Migrating the Printing of Error Messages  30

7.1.5  Migrating Port Number Assignments  31

7.1.6  Migrating Access to Configuration Files  33

7.2  Migrating Included Modules  33

7.2.1  Migrating mod_proxy  33

7.2.2  Migrating How Documents are Cached by Proxy Servers  33

7.3  Migrating Security  33

7.3.1  Migrating SSL  34

7.3.2  Migrating Chroot  34

7.4  Migrating Scripting Modules  34

7.4.1  Migrating PHP  35

7.4.2  PHP Oracle support in HP Apache 2.x  35

7.4.3  Migrating Perl  35

7.4.4  Migrating Common Gateway Interface (CGI)  36

7.4.5  Migrating Server-Side Includes (SSI)  36

7.5  Migrating Java  37

7.5.1  Migrating Tomcat with mod_jserv to Tomcat with mod_jk  37

7.5.2  Migrating JServ to Tomcat  39

7.5.3  Methods to Enable Servlets in Tomcat  41

7.6  Other Migration Tasks  41

7.6.1  Migrating the Selection of Server Type  41

7.6.2  Migrating Webmin  42

7.7  Migrating the Printing of Virtual Host Configuration  46

7.8  Writing 2.x Modules  46

7.8.1  Module Configuration  46

7.8.2  Handlers  50

7.8.3  Directives List  51

7.8.4  Initialization and Exiting  51

7.8.5  Functions and Types  52

7.8.6  Header files  54

7.8.7  Bibliography  54

7.9  Miscellaneous Changes  55

8  Tuning HP Apache-based Web Server 2.x Performance  56

8.1  Basic HTTP  56

8.2  SSL  56

8.3  PHP  56

8.4  Tomcat  57

9  Verifying the Migration  59

10  Appendix  60

10.1  Directive Changes by Name  60

10.2  Module Changes  64

10.2.1  Core  64

10.2.2  auth_ldap  64

10.2.3  mod_auth_dbm  65

10.2.4  mod_auth_digest  65

10.2.5  mod_autoindex  65

10.2.6  mod_case_filter and mod_case_filter_in  66

10.2.7  mod_cgid  66

10.2.8  mod_dav  and mod_dav_fs  67

10.2.9  mod_define  67

10.2.10  mod_echo  67

10.2.11  mod_env  67

10.2.12  mod_ext_filter  68

10.2.13  mod_headers  68

10.2.14  mod_include  68

10.2.15  mod_jk  69

10.2.16  mod_jserv  69

10.2.17  mod_log_agent  70

10.2.18  mod_log_config  70

10.2.19  mod_log_referer  70

10.2.20  mod_mime  70

10.2.21  mod_negotiation  71

10.2.22  mod_perl  71

10.2.23  mod_proxy, mod_cache, mod_disk_cache, and mod_file_cache  72

10.2.24  mod_file_cache  73

10.2.25  mod_setenvif  73

10.2.26  mod_ssl  74

10.2.27  mod_suexec  74

10.2.28  mod_usertrack  74

10.2.29  mod_vhost_alias  74

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  2.x Requirements  8

2.2.2  2.x Installation  8

2.3  Running 1.3.x and 2.x 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 2.x using the NEW 2.x configuration files as a base.  9

2.4.2  Solution D: Migrating to 2.x using your OLD 1.3.x configuration files as a 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 Apache-based Web Server 2.x  15

4.1  File Location Differences Between HP Apache 1.3.x and 2.x  15

4.2  Version and Module Numbers  16

4.3  New Multi-Processing Module in HP Apache 2.x  17

4.4  Summary of New Features in the HP Apache Version 2.x  17

5  Preparing for Installing HP Apache 2.x  20

5.1  HP Apache Hardware and Software Requirements  20

5.2  Disk Space Requirements  20

5.3  Perl Requirements  20

5.4  Java Development Kit (JDK) Requirements  21

5.5  Java Servlet Development Kit (JSDK 2.x) Requirements  21

6  Installing HP Apache 2.x  22

6.1  Installing HP Apache 2.x on a Server Where 1.3.x is Not Running  22

6.2  Installing HP Apache 2.x on a Server Concurrently Running 1.3.x  24

7  Migrating Your HP Apache Configuration from 1.3.x to 2.x  27

7.1  Migrating the HP Apache Core  27

7.1.1  Migrating Process Handling  27

7.1.2  Migrating Module Loading  29

7.1.3  Migrating Logging  30

7.1.4  Migrating the Printing of Error Messages  30

7.1.5  Migrating Port Number Assignments  31

7.1.6  Migrating Access to Configuration Files  33

7.2  Migrating Included Modules  33

7.2.1  Migrating mod_proxy  33

7.2.2  Migrating How Documents are Cached by Proxy Servers  33

7.3  Migrating Security  33

7.3.1  Migrating SSL  34

7.3.2  Migrating Chroot  34

7.4  Migrating Scripting Modules  34

7.4.1  Migrating PHP  34

7.4.2  PHP Oracle support in HP Apache 2.x  35

7.4.3  Migrating Perl  35

7.4.4  Migrating Common Gateway Interface (CGI)  36

7.4.5  Migrating Server-Side Includes (SSI)  36

7.5  Migrating Java  37

7.5.1  Migrating Tomcat with mod_jserv to Tomcat with mod_jk  37

7.5.2  Migrating JServ to Tomcat  38

7.5.3  Methods to Enable Servlets in Tomcat  40

7.6  Other Migration Tasks  41

7.6.1  Migrating the Selection of Server Type  41

7.6.2  Migrating Webmin  41

7.7  Migrating the Printing of Virtual Host Configuration  45

7.8  Writing 2.x Modules  46

7.8.1  Module Configuration  46

7.8.2  Handlers  49

7.8.3  Directives List  50

7.8.4  Initialization and Exiting  50

7.8.5  Functions and Types  51

7.8.6  Header files  53

7.8.7  Bibliography  53

7.9  Miscellaneous Changes  54

8  Tuning HP Apache-based Web Server 2.x Performance  55

8.1  Basic HTTP  55

8.2  SSL  55

8.3  PHP  55

8.4  Tomcat  56

9  Verifying the Migration  58

10  Appendix  59

10.1  Directive Changes by Name  59

10.2  Module Changes  63

10.2.1  Core  63

10.2.2  auth_ldap  63

10.2.3  mod_auth_dbm  64

10.2.4  mod_auth_digest  64

10.2.5  mod_autoindex  64

10.2.6  mod_case_filter and mod_case_filter_in  65

10.2.7  mod_cgid  65

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  67

10.2.13  mod_headers  67

10.2.14  mod_include  67

10.2.15  mod_jk  68

10.2.16  mod_jserv  68

10.2.17  mod_log_agent  69

10.2.18  mod_log_config  69

10.2.19  mod_log_referer  69

10.2.20  mod_mime  69

10.2.21  mod_negotiation  70

10.2.22  mod_perl  70

10.2.23  mod_proxy, mod_cache, mod_disk_cache, and mod_file_cache  71

10.2.24  mod_file_cache  72

10.2.25  mod_setenvif  72

10.2.26  mod_ssl  73

10.2.27  mod_suexec  73

10.2.28  mod_usertrack  73

10.2.29  mod_vhost_alias  73

 


Glossary

 

ASF

Apache Software Foundation

CA

Certificate Authority

hpuxws

HP-UX Web Server Suite

HP Apache

HP Apache-based Web Server

IPF

Itanium Processor Family

IPv6

Internet Protocol Version 6

JDK

Java Development Kit

JRE

Java Runtime Environment

LDAP

Lightweight Directory Access Protocol

MPM

Multi-Processing Module

PA-RISC

Precision Architecture, Reduced Instruction Set Computing

PHP

PHP PHP: Hypertext Preprocessor

RSA

RSA Security Inc.

WebDAV

Web-based Distributed Authoring and Versioning

For other acronyms see www.scis.hp.com/scis/mms/egad/Egadr.html

Revision History

 

SeptemberDecember 3January 106, 20023

Version 19

Updated mod_perl DSO, auth_ldap 1.6 for HP Apache 1.3.26.06

 

 

 


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 1997-2001-20032.  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® Itanium 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 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@cryptsoft.com).

 

This product includes software developed by the Java Apache Project for use in the Apache JServ Servlet Engine (http://java.apache.org/).
 
This product includes software developed by Ralf S. Engelschall (rse@engelschall.com) for use in the mod_ssl project (http://www.modssl.org/).
 
This product includes software developed by Ralf S. Engelschall (rse@engelschall.com).

 

This product includes PHP, freely available from (http://www.php.net).

 


 

1         Using this Guide

 

 

This guide covers the migration from HP Apache-based Web Server Version 1.3.x to VersionrthellaHP-UX Web Server Suite 2.x on servers running HP-UX 11.0 (PA-RISC), 11i (PA-RISC) and HP-UX 11i Version 1.5 or later, Itanium Processor Family (IPF).

 

This guide can be used to:

 

·         Understand the differences between HP Apache HP Apache-based Web Server Version 1.3.x and HP Apache VersionrthellaHP-UX Web Server Suite 2.x..

·         Install the HP Apache-based Web Server VerrthellaHP-UX Web Server Suitesion 2.x.

·         Migrate the configuration of your HP Apache-based web Web Sserver from Version 1.3.x to rthellaHP-UX Web Server Suite 2.x.

·         Verify that your HP Apache VersionrthellaHP-UX Web Server Suite 2.xhpws migration was successful.

 

There are three basic sections to the guide.

 

·         Section 2: Quick Guide to Migration Solutions
For many users this will be the only section required.

·         Sections 3-7: Detailed Installation and Migration Steps
For users who want a more detailed discussion of a particular step.

·         Appendices: A complete listing of module changes
For users who want an exhaustive overview of all changes to modules, directives, and options.

 


 

2         Quick Guide to Migration Solutions

Four alternative solutions are presented. Solutions A & B are simple installations that require little knowledge of Apache. If you have heavily customized any part of Apache you should refer to the detailed sections later in the document. Solutions C & D are more complex and assume a familiarity with Apache's configuration files.

 

2.1        Quick Guide Assumptions

A.      1.3.x refers to HP Apache-based Web Server 1.3.x.
2.xhpuxwshpws----- refers to HP Apache-based Web Server 2.xrthellaHP-UX Web Server Suite.

B.      Files are in their default locations. For example:
1.3.x is installed in the default locations:
<apache root> = /opt/apache    and   <tomcat root> = /opt/tomcat
2.xrthellaHP-UX Web Server Suite is installed in the default locations:
<apache root> = /opt/hpapache2  hpws/apache  and   <tomcat root> = /opt/hpapache2hpws/tomcat

<webmin root> = /opt/hpws/webmin and <xmltools root> = /opt/hpws/xmltools

C.      The Apache documents are available at  root is <apache root>/hpws_docstdocs and /opt/hpws/hp_docs/apache.
The Tomcat documents are root isavailable at 
<tomcat root>/webappshpws_docs and /opt/hpws/hp_docs/tomcat. The XmlML Tools documents are available at /opt/hpws/hp_docs/xmltools. The Webmin documents are available at /opt/hpws/hp_docs/webmin.                                                                                                                                                        

(Note: The file /opt/hpws/apache2/util/altroot.sh can be used to move Apache's root. Type "altroot.sh -h" for help with the script)

D.      The customer does not need IPv6 support.

 

2.2        Preliminary Steps

2.2.1        rthellaHP-UX Web Server Suite2.x Requirements

HP-UX 11.0, 11i, 11i version 1.5, or later.
90 MB of disk space without XML Tools installed. 190MB of disk space for all four components installed.

Perl 5.6.1

Java JDK 1.2.2.4 or later

 

2.2.2        2.xrthellaHP-UX Web Server Suite  Installation

A.      Stop Apache. For example if you are using HP Apache 1.3.x. then as root type:
/opt/apache/bin/apachectl stop

B.      Verify that all httpd processes have stopped by typing:
ps -e | grep httpd

C.      Install 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 HP SW Depot.

Or install using the HP-UX 11.0/11i Application Release CDs (when available).

 

2.3        Running 1.3.x and 2.xrthellaHP-UX Web Server Suite on the same machine

Solutions A & B are two simple alternative installations.

 

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

If you installed 2.xrthellaHP-UX Web Server Suite on a machine that has 1.3.x then you are done. No additional steps are required. HP Apache 2.xrthellaHP-UX Web Server Suite and HP Apache 1.3.x can coexist on the same machine. However because they use the same port assignments, they cannot be run at the same time without conflicting with each other.

 

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

You need to change the port assignments so that the two Apaches don't conflict. The utility script /opt/hpwsapache2/util/ports.sh can be used to list ports and files for you to manually edit.

For example type:

/opt/hpwsapache2/util/ports.sh

 

You will see output similar to the following:

Apache installed at /opt/hpws/apache

Tomcat installed at /opt/hpws/tomcat

Webmin installed at /opt/hpws/webmin

Xmltools installed at /opt/hpws/xmltools

 

Default locations of configuration files:

Apache:       /opt/hpws/apache/conf/httpd.conf

Apache (SSL): /opt/hpws/apache/conf/ssl.conf

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

Tomcat:       /opt/hpws/tomcat/conf/server.xml

mod_jk:       /opt/hpws/tomcat/jk/apache2/mod_jk.conf

mod_jk:       /opt/hpws/tomcat/jk/apache2/workers.properties

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

 

The following ports have been identified:

HTTP port:         80

HTTPS port:        443

Tomcat ports:      8005 8081 8009

Webmin port:       10000

LDAP port:         389

 

 Apache installed at /opt/hpapache2

 

Default locations of configuration files:

Apache:       /opt/hpapache2/conf/httpd.conf

Apache (SSL): /opt/hpapache2/conf/ssl.conf

Tomcat:       /opt/hpapache2/tomcat/conf/server.xml

mod_jk:       /opt/hpapache2/tomcat/conf/jk/workers.properties

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

LDAP:         /opt/hpapache2/conf/ldap.conf

 

The following ports have been identified:

HTTP port:         80

HTTPS port:        443

Tomcat http port:  8081

Tomcat ajp12 port: 8007

Tomcat ajp13 port: 8009

Webmin port:       10000

LDAP port:         389

 

Then go to each file and manually change the port numbers to for example:

HTTP port:         8080

HTTPS port:        8443   (note 1)

Tomcat http port:  8181

Tomcat ajp12 port: 8107

Tomcat ajp13 port: 8109ports:      8105,8181,8109

Webmin port:       10100

LDAP port:         389    (note 2)

Note 1.  Your SSL URL will need to be of the form https://yourserver.com:8443 since you are no longer using the standard SSL port.

Note 2.  The LDAP port doesn't change since it is the LDAP server's port. HP Apache-based Web Server or HP-UX Apache-based Web Server is an LDAP client.

 

2.4        Modifying httpd.conf

Solutions C & D are two alternative 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 2.xrthellaHP-UX Web Server Suite using the NEW 2.xrthellaHP-UX Web Server Suite configuration files as a base.

A.      Save a copy of /opt/hpws/apache2/conf/httpd.conf

B.      Find the differences between the old and new configuration files. For example:
diff /opt/apache/conf/httpd.conf /opt/hpws/apache2/conf/httpd.conf

C.      Edit /opt/hpws/apache2/conf/httpd.conf

D.      Skip to the "Directives Common to C & D Solutions" section below.

 

2.4.2        Solution D: Migrating to 2.xrthellaHP-UX Web Server Suite using your OLD 1.3.x configuration files as a base.

A.      Save a copy of /opt/hpws/apache2/conf/httpd.conf

B.      Copy your 1.3 httpd.conf file to /opt/hpws/apache2/conf/httpd.conf

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

D.      Edit /opt/hpws/apache2/conf/httpd.conf

E.      LoadModule
The module location has changed from the libexec to modules directory. So you need to replace libexec with modules in the "Dynamic Shared Object (DSO) Support" section.

F.      mmod_dav
This module enables "Web-based Distributed Authoring and Versioning" (webDAV)
See the FAQ at www.hp.com/products1/unix/webservers/apache/faqs/index.html for more details.

G.     mod_perl

   Enabling Perl has changed. In HP-UX Apache-based Web Server "ModPerl::" has replaced "Apache::".       

   The new way is:
       <IfModule mod_perl.c>
   
 PerlModule ModPerl::Registry
   <Files *.pl>
        SetHandler perl-script
        PerlHandler ModPerl::Registry::handler
        Options +ExecCGI

        PerlOptions +ParseHeaders

        </Files>
      </IfModule>

H.      mod_php

      Enabling PHP has changed. For example in 1.3.x you did:

           A  AddType application/x-httpd-php .php
 
AddType application/x-httpd-php-source .phps
But in HP-UX Apache-based Web Server you do:
           <Files *.php>     
   
  SetOutputFilter PHP
   
  SetInputFilter PHP
     </Files>

      In addition, to use PATH_INFO, you must explicitly set directive AcceptPathInfo, otherwise a 404 response will     be returned.mod_perl
Enabling Perl has changed. In 2.xrthellaHP-UX Web Server Suite "ModPerl::" has replaced "Apache::". The new way is:
<IfModule mod_perl.c>
    PerlModule ModPerl::Registry
    <Files *.pl>
        SetHandler perl-script
        PerlHandler ModPerl::Registry::handler
        Options ExecCGI

 

mod_php
Enabling PHP has changed. For example in 1.3.x you did:
    AddType application/x-httpd-php .php
    AddType application/x-httpd-php-source .phps
But in 2.xrthellaHP-UX Web Server Suite you do:
<Files *.php>     
    SetOutputFilter PHP
    SetInputFilter PHP
</Files>

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

I.         mod_proxy
The method of invoking mod_proxy has changed radically.
See httpd.apache.org/docs-2.0/mod/mod_proxy.html.
For example in 1.3.x you do:
  <Directory proxy: *>
      ...
  </Directory >
But in 2.xrthellaHP-UX Apache-based Web Server Suite you do:
  <Proxy *>
      ...
  </Proxy>

J.       mod_suexec
To enable suexec you need to load the module with
LoadModule suexec_module modules/mod_suexec.so
And you need to setup the following directive:
<IfModule mod_suexec.c>
    SuexecUserGroup TheUser TheUsersGroup
</IfModule>
This is new HP Apache 2.xrthellaHP-UX Web Server Suite functionality.

      See httpd.apache.org/docs-2.0/mod/mod_suexec.html.

K.      mod_jk 

This module is the connector used by Apache to communicate with   Tomcat servlet container. Mod_jk replaces  the mod_jserv connector which is used by the Apache JServ servlet engine To enable this uncomment the line #Include /opt/hpws/tomcat/jk/apache2/mod_jk.conf in /opt/hpws/apache/conf/httpd.conf. See http://jakarta.apache.org/tomcat/tomcat-4.1-doc/jk2/jk/aphowto.html for more information.

L.       AddCharset
You may wish to take advantage of the many new character sets added to 2.xrthellaHP-UX  Apache-based Web Server Suite. Previously there were 8 now there are 28. See httpd.apache.org/docs-2.0/mod/mod_mime.html#addcharset.

M.     AddHandler type-map var
Previously this was commented out. It is now enabled by default to allow the Apache "It Worked" page (http://yourserver.com/index.html) to be distributed in multiple languages.

N.      ErrorDocument
ASF documentation says that this directive must now have a closing quote. For example
ErrorDocument 403 “Some Message”
Currently if you leave off the closing quote no error is reported but this may change in the future.

O.     BrowserMatch
You need to enable the following if you are going 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.

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

Q.     ReadmeName and HeaderName
These directives determine the filename to be appended and prepended to the directory listing. The defaults have been change from README and HEADER to README.html and HEADER.html.

R.      Continue with the "Directives Common to C & D Solutions" section below.

 

2.4.3        Directives Common to C & D Solutions

These apply to both Solutions C and D.

A.      ServerType
The ServerType directive has been eliminated since 2.xrthellaHP-UX Web Server Suite can only be ServerType standalone.

B.      Port
The Listen directive is now required and the Port directive has been eliminated. For example if you had set Port 80 you should change it to Listen 80.

C.      ServerName
The ServerName directive now supercedes the functionality of the Port directive. If no ServerName  or associated port number is indicated then Apache will try to deduce them. For reliablity and predictability you should explicitly set the servername and port. For example:
ServerName yourserver.com:80.

D.      Process handling directives.
See Migrating Process Handling.
¨StartServers and ThreadsPerChild
There is not much reason to change these values since 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 only indirectly related to MaxClients so you normally won't change this value.
¨MaxRequestsPerChild
This directive sets the limit on the number of requests that an individual child server process will handle. After MaxRequestsPerChild requests, the child process will die. If it is set to 0 then the process will never die. If you load modules that are not distributed by HP, you may have memory leaks. In that case you may want to set MaxRequestsPerChild to, for example, 500 so that the process will die and the memory will be freed. In order to maximize performance HP Apache or HP-UX Apache-based Web Server sets it to 0.
¨MinSpareThreads and MaxSpareThreads
Child processes are created until the number of idle threads are greater than MinSpareThreads. Child processes are killed until the number of idle threads are less than MaxSpareThreads. The defaults should work well with most servers. If you have extremely high loads then increase MinSpareThreads and MaxSpareThreads. This will not increase 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.

E.      Modules not in HP Apache 2.xrthellaHP-UX Apache-based Web Server Suite distribution
Check that you have the same modules in LoadModule as you had in 1.3.x. 1.3.x modules will not work with 2.xrthellaHP-UX Web Server Suite and will need to be rewritten. See Writing 2.x Modules.

F.      mod_auth_digest
mod_digest
has been renamed to mod_auth_digest.

G.     mod_proxy, mod_cache, mod_disk_cache, and mod_file_cache
mod_proxy has been decomposed into a more logical structure with separate modules. The cache functionality has been split out into other cache modules such as mod_cache, mod_disk_cache, and mod_file_cache. Generally they use similar cache directives as used in the old mod_proxy.

H.      mod_cgi. 
See Migrating Common Gateway Interface (CGI) and
httpd.apache.org/docs-2.0/mod/mod_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 modules/mod_cgi.so
Scriptsock <path>
You need to enable the Scriptsock directive which defines the UNIX socket for communicating with cgid.
Scriptsock            logs/cgisock

I.         mod_define
mod_define
has been eliminated. The Define directive allowed you to set a variable for later use in the configuration file. A future module may implement this functionality.

J.       Logging directives.
See Migrating Logging
AgentLog
, RefererLog, and RefererIgnore
The logging directives AgentLog, RefererLog, and RefererIgnore have been eliminated. They can be replaced with LogFormat and CustomLog directives.

A.      mod_ssl
¨SSL configuration is in a separate configuration file called ssl.conf.
¨The default session cache is now:
SSLSessionCache        shmcb:logs/ssl_scache(512000)
¨ca-bundle.crt is not distributed with 2.xrthellaHP-UX Apache-based Web Server Suite. You can use the certmig tool to extract ca certificates from a Netscape client. For example:
/opt/hpws/apache2/binutil/test_certmig.sh -E -d $HOME/.netscape
See /opt/hpws/apache2/hpws_apache_docs/apache/utilities.user.guide.

K.       

¨       Logging directives have changed

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

 

 

2.5        Start

To start Apache, aAs root type ::

/opt/hpws/apache/bin2/apachectl start

 

2.6        Verify

In a browser enter the URL:

http://yourserver.com

 


 

3         Getting More Information

 

The HP Apache-based Web Server  or HP-UX Web Server Suite is built on the open source Apache Web HTTP Server software developed by the Apache Software Foundation (ASF) with additional open source components and HP proprietary content integrated and bundled by HP.

 

The following table lists resources for HP Apache-based Web Server Apache or HP-UX Web Server Suite.  For the latest HP Apache-based Web Server Apache or HP-UX Web Server Suite information, see www.hp.com/go/webserver. 

 

HP Apache-based Web Server or HP-UX Web Server Suite Resources

Resources

Location

HP Apache-based Web Server Apache  or HP-UX Web Server Suite information library, technical tips, FAQs

www.hp.com/products1/unix/webservers/apache/index.html

HP Apache-based Web Server or HP-UX Web Server Suite product bundle

software.hp.com/
   
àFeatured Products
       
àHP Apache-based Web Server

OR

software.hp.com/    www.hp.com/go/webserver
    search for "HP Apache-based Web Server"Click  “downloads”

 

HP Apache or HP-UX web Server Suite product bundle for IPv6

software.hp.com/
    search for "IPv6"

HP Developer & Solution Partner Portal

www.hp.com/
    search for "HP Apache-based Web Server"

 

Integrated Applications

Resources

Location

HP-UX Workload Manager

www.hp.com/go/wlm

BEA Weblogic connector to Apache (mod_wl)HP Application Server (HP-AS) connector to HP Apache
(mod_lbb, Load Balance Broker). Formerly “Total-e-Server”, TeS, “Sapphire” by Bluestone.

www.bea.comhttp://www.hp.com/products1/softwareproducts/middleware_businessprocess/index.html     search for “HP-AS”

 

BroadVision connector to HP Apache (mod_bv)

www.broadvision.com

 

The following table lists general information about Apache and the open source add-on products bundled by HP into the HP Apache-based Web Server or HP-UX Web Server Suite.

 

 

Apache Open Source Resources

Resources

Location

    General

Apache HTTP Web Server General Information

httpd.apache.org/

Apache Software Foundation (ASF)

www.apache.org/

Apache 1.3 User’s Guide

httpd.apache.org/docs/

Apache 2 User’s Guide

httpd.apache.org/docs-2.0/

Developer resources

dev.apache.org

    IPv6

IPv6 Home Page

www.ipv6.org

    LDAP authentication

OpenLDAP

www.openldap.org/

auth_ldap

www.rudedog.org/auth_ldap

    Perl

Perl Interpreter

www.software.hp.com/, search for “Perl v.5.6.1”

General information on the mod_perl module

perl.apache.org/

    PHP

PHP User's Guide

www.php.net/docs.php

General information on PHP

www.php.net

    Servlets

Tomcat User's Guide

jakarta.apache.org/tomcat/tomcat-4.1-doc/index.htmljakarta.apache.org/tomcat/tomcat-3.3-doc/index.htmlhttp://jakarta.apache.org/tomcat/tomcat-4.1-doc/index.html

Apache JServ - Servlets Development Kit 2.0 for developing servlets. Later versions may work but they have not been tested. This is required by JServ in HP Apache 1.3.x

java.sun.com/products/servlet/archive.html

    SSL

OpenSSL User's Guide

www.openssl.org/docs/

mod_ssl User's Guide

www.modssl.org/docs

    WebDAV

webDAV Home Page

www.webdav.org/

    Webmin

Webmin User's Guide

www.swelltech.com/support/webminguide/index.html

Webmin Home Page

www.webmin.com/

 XML Tools

 

Cocoon Documents

xml.apache.org/cocoon/index.html

Xerces Documents

xml.apache.org/xerces2-j/index.html

Xalan Documents

xml.apache.org/xalan-j/index.html

FOP Documents

xml.apache.org/fop/index.html

Batik Documents

xml.apache.org/batik /index.html

 


 

4         What’s New and Changed in HP Apache-based Web Server 2.xrthellaHP-UX Web Server Suite

 

This version is the first release of a more flexible HP-UX Apache-based

 Web Server Suite.  product structure. Beginning with this version, HP-UX Apache-based Web Server, HP-UX

Tomcat-based Servlet Engine, and HP-UX Webmin-based Admin can be installed together (as previouslyin previous versions of HpP Apache-based Web Server) or installed  

separately as standalone components. A new feature, HP-UX xmltoolsXML Web Server Tools, has been added and it can be installed   up upseparately or with other components. Each is installed in its own

directory  with a common base root of /opt/hpws/

 

This section contains an overview of the new and changed features in HP-UX  Web Server Suite Apache-based Web Server Version 2.x.

 

4.1        File Location Differences Between HP Apache 1.3.x and 2.xrthellaHP-UX Web Server Suite

 

HP Apache 1.3.x files are located in /opt/apache. 

In HP Apache 2.xrthellaHP-UX  Apache-based Web Server  Suite these files are located in /opt/hpws under  their respective directoriesapache2.

 

The following table compares HP Apache 1.3.x and HP Apache 2.xrthellaHP-UX Web Server Suite configuration files. 

 

Configuration File Differences Between HP Apache 1.3.x and 2.xHP-UX Web Server Suite

Component

HP Apache 1.3.x

HP Apache 2.xrthellaHP-UX Web Server Suite

Apache Server (httpd)

/opt/apache/conf/httpd.conf

/opt/hpws/apache2/conf/httpd.conf

mod_ssl

 

Included inside of:
/opt/apache/conf/httpd.conf

/opt/hpws/apache2/conf/ssl.conf
New in rthellaHP-UX Web Server Suite2.x and included by httpd.conf

 

mod_file_cache

Not available

/opt/hpws/apache2/conf/cache.conf

Tomcat

/opt/tomcat/conf/server.xml

/opt/hpws/apache2/tomcat/conf/server.xml

mod_jserv

/opt/apache/conf/jserv/jserv.conf

Replaced with mod_jk

mod_jk

 

1.3.26 onlyand later:

Not available

/opt/tomcat/conf/jk/mod_jk.conf and
/opt/tomcat/conf/jk/

   workers.properties

/opt/hwspapache2/tomcat/jk/apache2conf/jk/mod_jk.conf and
/opt/hpwsapache2/tomcat/conf/jk/apache2/
   workers.properties

Webmin

/opt/apache/webmin/conf/
  
miniserv.conf

/opt/hpwsapache2/webmin/conf/miniserv.conf

auth_ldap

Not available1.3.26.06 and later:
/opt/apache/conf/ldap.conf

/opt/hpws/apache2/conf/ldap.conf

Note: If you do no't need the functionality then you can comment out the corresponding "include" directive. For example if you do no't need ldap authentication then the line would look like:

#include Include /opt/hpws/apache2/apache/conf/ldap.conf


4.2        Version and Module Numbers

 

 

Version Numbers of HP Apache and HP-UX Web Server Suite Components

Component

HP Apache 1.3.2619.23 on 11.0/11i and

Version 1.5 or later (PA-RISC & IPF)

HP Apache 2.0.00rthellaHP-UX Web Server Suite
on 11.0/11i and
11i Version 1.5 or later
(PA-RISC & IPF)

Apache Web Servermod_ssl

1.3.262.8.3

2.0.3943A standard module of ASF Apache

OpenSSL

0.9.6gc5a

0.9.6gc

mod_ssl

2.8.109

A standard module of ASF Apache

BSAFE ®

Crypto-C

PA 5.2/IPF 5.2.15.0

PA 5.2/IPF 5.2.1

Tomcat Servlet Container

3.3.13.1.1

3.3.14.1.12

Apache Connector to Tomcat

mod_jserv            / mod_jk

mod_jk

Apache JServ

1.1.1

Not available.

See preceding table row for equivalent.

mod_jk

1.20

1.20

mod_perl

1.27

1.99_07

PHP

4.2.2

4.2.3

auth_ldap

1.6

1.54

OpenLDAP SDK

Not available2.0.7

2.0.7

Stunnel

Not available3.14

3.14

Webmin

0.9800.84

0.910.9801.020

Xerces

Not available

2.2.1

Xalan

Not available

2.4.1

Batik

Not available

1.5

FOP

Not available

0.20.4

Cocoon

Not available

2.0.3

 

 

Note:

The version numbers in the preceding table are correct for the HP Apache-based Web Server 1.3.26.065x and 2.0.39HP-UX Web Server Suite initial . 050  releases shown. For later releases see the HP Apache Release Notes in the documentation directory,  in /opt/hpapache2/hp_apache_docs/hpapache.admin.guide or on the Software Depot web site:

software.hp.com/ à Featured Products à HP-UX Apache-based Web Server

 or

www.hp.com/go/webserveràClick “downloads”software.hp.com/,  search for  "HP Apache-based Web Server"

 


4.3        New Multi-Processing Module in HP Apache 2.xrthellaHP-UX Apache-based Web Server Suite

 

The Apache HTTP server 2.x can be built with one of several different multiprocessing modules (MPMs). These MPMs are beos, os2, perchild, prefork, winnt and worker. Apache 1.3.x is equivalent to "prefork". HP Apache 2.xrthellaHP-UX Apache-based Web Server Suite is built with the "worker" module. This module implements a hybrid, multiprocess, multithreaded server and provides high scalability with improved performance.

 

In the worker MPM a single control process is responsible for launching child processes. A fixed number of threads is created by each child process. This is specified in the ThreadsPerChild directive. Individual threads listen for connections and serve them when they arrive. A pool of spare, idle threads is created to be ready to handle these connections. The MinSpareThreads and MaxSpareThreads directives determine the range of this pool. Processes will be dynamically created until there are idle threads equal to at least MinSpareThreads. Processes will be destroyed until there are idle threads less than or equal to  MaxSpareThreads. The MaxRequestsPerChild directive limits the number of requests that an individual child server process will handle. It controls how frequently the server recycles processes by killing old ones and launching new ones. If MaxRequestsPerChild is set to 0 then processes are never recycled.

 

For more information on the worker MPM, see httpd.apache.org/docs-2.0/mod/worker.html.

 

 

4.4        Summary of New Features in the HP Apache Version 2.xrthellaHP-UX Web Server Suite

 

Following is a summary of the new features in HP Apache-based Web Server 2.xrthellaHP-UX Web Server Suite.

 

Threading

HP Apache 2.xrthellaHP-UX Apache-based Web Server Suite runs in a hybrid multiprocessmulti-process, multi-threaded mode for improved scalability.

Multi-protoocol Support

One of the new capabilities of Apache is support for multiple protocols. Users can write filters that implement ftp and other protocols. (mod_echo is provided as an example.)

Apache Portable Runtime (APR)

This new Apache API for modules has changed significantly for 2.xrthellaHP-UX Apache-based Web Server.  In 2.xrthellaHP-UX Apache-based Web Server module ordering is done largely automatically. Module ordering is also done per-hook to allow more flexibility. Hooks allow modules to interact with Apache at many points in Apache's processing chain. New calls have been added that provide additional module capabilities without patching the core Apache server.

Filtering

Apache modules may now be written as filters that act on the stream of content as it is delivered to or from the server. For example, the output of CGI scripts can be parsed for Server-Side Include directives by mod_include.

IPv6 Support

On systems where IPv6 is supported by the underlying OS, Apache gets IPv6 listening sockets by default. Additionally, the Listen, NameVirtualHost, and <VirtualHost> directives support IPv6 numeric address strings (e.g., "Listen [fe80::1]:8080").

Note:

a.       HP-UX Apache Web Server Suite for IPv6 is available on 11i (PA-RISC) as a separate HP –UX ApacheWeb Server Suite product and requires an additional IPv6 networking product to be installed. HP plans to have IPv6 support integrated into 11i version 2.

b.       Other HP-UX releases and IPF are not supported at this time.

WebDAV

WebDAV (“Web-based Distributed Authoring and Versioning”) is a set of extensions to the HTTP protocol whichprotocol that allows users to create, move, copy, and delete files (i.e. HTML, images, presentations) and directories on a remote server.  HP-UX Apache-based Web Server implements WebDAV using the mod_webdav and mod_webdav_fs modules, www.webdav.org/.   WebDAV is an IETF standard for collaborative authoring on the web.  With HTTP, WebDAV can use strong authentication (certificates), encryption, proxy support, and caching.

 

 

PHP to Oracle Database Connectivity (PA-RISC only)

PHP can be used to access Oracle 8.1.6. The database can reside on either the same server as Apache (local) or on a different server (remote).

LDAP Authentication

Auth_ldap is the connector between Apache and an LDAP directory server that allows Apache to authenticate HTTP clients by utilizing entries in an LDAP directory. authAuth_ldap supports iPlanet (Netscape) Directory Server and OpenLDAP Directory Server. authAuth_ldap can be configured to use the stunnel program for secure SSL queries to the LDAP server. The stunnel binary is located in /opt/hpws/apache2/stunnel/sbin. OpenLDAP SDK resides in /opt/hpws/apache2/lib/LDAP.

Webmin

Webmin has HP added functionality in administrating Apache 2.0 features, easily listing displaying default values, and and mannagingaccessing log files. You can now also generate keys and certificates for your server or for your own self signed Certificate Authority (CA).

XML Tools

 

·         Xerces provides XML parsing and generation

·         Xalan is an XSLT stylesheet processor for transforming XML documents into HTML, text, or other XML document types.

·         Cocoon is a framework for XML web publishing that brings a whole new world of abstraction and ease to consolidated web site creation and management based on the XML paradigm and related technologies.

·         FOP is a print formatter driven by XSL formatting objects. It is a Java 1.2 application that reads a formatting object tree and then turns it into a PDF document. The formatting object tree, can be in the form of an XML document (output by an XSLT engine like Xalan) or can be passed in memory as a DOM Document or (in the case of Xalan) SAX events.

·         Batik is a Java-based toolkit for applications or applets that want to use images in the Scalable Vector Graphics (SVG) format for purposes such as parsing, viewing, generation or manipulation on either the client side or the server side.

New Utilities

These utilities are found in /opt/hpwsapache2/util. For more information, please see:

/opt/hpws/hp_docs/opt/hpapache2/hp_apache_docs/utilities.user.guide   

 

a.      altroot.sh

     

Alternate Root Utility. After installing HP-UX Web Server Suite into the default

       /opt/hpws directory, this script can be used to move it into

       another directory.

 
 .
This script moves Apache from its current location to an alternate one. It changes all occurrences of old Apache root to new Apache root in all configuration files and scripts.

a.     

b.       

This interactive utility helps in the creation of cache.conf file for

use with mod_file_cache. Performance of HP-UX Apache-based Web Server can be improved for

serving of static content by using mod_file_cache. Frequently accessed

static files can be pre-loaded into memory and served directly in   order

to avoid frequent disk access. Files to be cached by mod_file_cache are

listed in cache.conf file.

 

c.       chroot_os_cp.sh

     

 This interactive utility helps in the creation of cache.conf file for use with mod_file_cache.  Performance of HP Apache can be improved for serving of static content by using mod_file_cache.

chroot_os_cp.sh

                   Chroot copy utility.  This is a helper script that sets up chroot

       by copying typical files used by HP-UX Apache-based Web Server into the chroot directory.

       The copied set of files allows demo web pages to run. A very secure        Apache may require some of these files to be deleted. If you need

       additional things to be done as part of chroot set-up, you are

       encouraged to customize this script for your site.

 

d.      mkcert.sh

 Chroot Copy utility.  This utility is provided as a support for using the chroot feature with apache.  Please refer to security.admin.guide for information on Chroot.

mkcert.sh

SSL Certificate Generation Utility.  This script generates private keys, certificate signing requests, and certificates for the CA, server, and client.   Before you use the mod_ssl, you should prepare the SSL certificate system by running the 'mkcert.sh' command.

 

e.      ports.sh

ports.sh

      
 

       Port List Utility. This script lists the ports being configured

       by the HP-UX Apache-based Web Server. In this distribution,  

       ports are configured for Apache, Apache(SSL), Tomcat, mod_jk,

       Webmin, and LDAP.

 

f.        stunnel_ctl.sh

 

 Port List Utility. This is a shell script that lists the ports that are being configured by the HP Apache-based Web Server. In this distribution, there are ports being configured for Apache, Apache(SSL), Tomcat, mod_jk, Webmin, and LDAP.

a.stunnel_ctl.sh

This is a wrapper utility for starting up the stunnel program.  Stunnel is used for SSL connections between Apache and an LDAP directory server.  More information on configuring an SSL connection is in the ldap.admin.guide.

 

g.      test_certmig.sh

 
 

       Certificate Migration Utility. This utility is a wrapper around

       certmig. It can be used to import, extract and list the certificates

       in an iPlanet 4.1.x Certificate database. For usage information,

        Type  "/opt/hpws/apache/util/test_certmig.sh -h".

 

 

 

 

 

 

A