• HP-UX Apache-based Web Server
• HP-UX Tomcat-based Servlet Engine
• HP-UX XML Web Server Tools
• HP-UX Webmin-based Admin

• HP-UX Apache-based Web Server combines numerous popular modules from other Open Source projects as well as provides HP value-added features for the HP-UX platform
  - Scripting capabilities: PHP, mod_perl, CGI
  - Content management: WebDAV
  - Security: authentication through an LDAP server, Chrooted environment, SSL and TLS support
• HP-UX Webmin-based Admin is a Configuration and Administration GUI with extensive enhancements for the HP-UX Apache-based Web Server.
• HP-UX Tomcat-based Servlet Engine provides customers Java-based extensions for dynamic content generation via Servlets and JavaServer Pages (JSPs).
• HP-UX XML Web Server Tools is a collection of a Java-based XML tools used for XML parsing, stylesheet and XSL processing, web-publishing and image translating from the open source projects: Xerces, Xalan, Cocoon, FOP and Batik.

HP enhances the software in the areas of performance, encryption, reliability, customization and administration. HP also ensures the suite of products work together with the HP-UX 11.x operating environment. The HP-UX Web Server Suite is supported at no additional charge for customers with HP-UX support agreements.

HP provides the HP-UX Web Server Suite with the correct hardware to match the workload and cost effectiveness requirements of the customer. The suite runs with HP-UX 11.0 and HP-UX 11i on the PA-RISC family of 64-bit RP hardware servers. It also operates with HP-UX 11i on the Intel Itanium 64-bit family of hardware servers. With this wide array of hardware to run the same HP-UX Web Server Suite, high return on IT expenditure is coupled with ease of administration.

For the latest information on the HP-UX Web Server Suite, see
www.hp.com/go/webserver
Click: "downloads".

For general information on Apache's HTTP Web Server, see:
httpd.apache.org/

For the Apache Software Foundation, see:
www.apache.org/

For the latest news on Apache, see:
www.apacheweek.com/
www.oreillynet.com/apache/
apachetoday.com
slashdot.org/index.pl?section=apache

10.20 Binaries (unsupported)
The HP-UX Porting and Archive Centre at hpux.cs.utah.edu/ has 10.20 Apache binaries available for a limited time only. As of June 2002, no new 10.20 binaries are being created. Check for versions and availability at:
hpux.cs.utah.edu/hppd/hpux/Networking/WWW/

For specific versions see the FAQ: Where can I find the version numbers for HP-UX Web Server Suite and its components?

The HP-UX Apache-based Web Server is engineered through state-of-the-art processes for the highest quality and is tailored to run smoothly on the HP-UX. The HP-UX Apache-based Web Server is a total solution for web server deployment for the enterprise. The Open Source Apache Web Server software developed by the Apache Software Foundation (Apache HTTP Server Project described at httpd.apache.org) serves as the foundation for the HP-UX Apache-based Web Server. In addition to the base HTTP server, HP has combined numerous popular modules from other Open Source projects as well as HP-developed valued features, such as performance tuning, user guides, and security modules, so the HP-UX Apache-based Web Server is highly optimized for the HP-UX environment.

To give the high scalability needed by heavy traffic web sites, HP-UX Web Server Suite adds the ability to use threads.

To support the new standard for longer IP addresses, IPv6 has been added.

To increase functionality, WebDAV has been added to support web publishing through authoring and versioning.

To help large organizations manage user authorization, auth_ldap has been added so that HP-UX Apache-based Web Server can talk to a central LDAP server where user information is maintained.

To improve the administration of HP-UX Web Server Suite, functionality has been added to HP-UX Webmin-based Admin.

Also see the FAQ:
What components does HP-UX Web Server Suite contain?
For new features in the open source Apache 2.x see:
httpd.apache.org/docs-2.0/new_features_2_0.html

You can check the installed components by typing:
swlist -R depot

If server-info is enabled you can enter the following in a browser:
http://yourserver.com/server-info
See the FAQ: How can I get information about my server from a browser?

Individual components will give you their version numbers.
For Apache use:
httpd -v or for more info httpd -V
For Tomcat view main web page:
http://yourserver.com:8081
For java use:
java -version
For Perl use:
perl -v or for more info perl -V
For PHP use the following function in a web page.
<?phpinfo()?> 
For HP-UX OS use:
uname -r

See also:
How do I start Apache in secure mode through Webmin?
How do I start and stop Webmin?
How do I start and stop Tomcat?

The output will be similar to the following:

This is ApacheBench, Version 1.3c < $Revision:="$Revision:" 1.44="1.44" $="$"> apache-1.3
Copyright © 1996 Adam Twiss, Zeus Technology Ltd, http://www.zeustech.net/
Copyright © 1998-2000 The Apache Group, http://www.apache.org/

Benchmarking yourserver.com (be patient)...INFO: POST header == --- HEAD/index.html HTTP/1.0 User-Agent: ApacheBench/1.3c Host: yourserver.com
Accept: */*

B. Here's a simple Perl script to retrieve web pages from the command line. You will need Perl 5.6.1.
Paste the following into a file called "verify.response.pl"

#!/opt/perl/bin/perl
require "getopts.pl";
use IO::Socket;

sub out {
print $s shift;
}

$port = 80;
Getopts('hw:f:p:');
if ($opt_h) {
print "Usage: $0 -w  -f  [-p ]\n";
print " hostname: Name or IP address of Web Server\n";
print " file: File name to get HEAD info on\n";
print " port: Port number the Web Server is running on (default: 80)\n";
exit;
}

if ($opt_f eq '') {
print "File name required with -f \n";
exit 1;
}

if ($opt_w eq '') {
print "Hostname required with -w \n";
exit 1;
}

if ($opt_p ne '') {
$port = $opt_p;
print "Using non-std port: $port\n";
}

$s = IO::Socket::INET->new("$opt_w:$port");
die "create socket: $!\n" if (!$s);

#$HEAD="GET " . $opt_f . " HTTP\/1.0 \n\n";
$HEAD="HEAD " . $opt_f . " HTTP\/1.0 \n\n";
print "Sending command: $HEAD ";
out "$HEAD";

print " -Reply from Server-\n";
while (< $s="$s">) {
print "$_";
}
close ($s);

The output will look like the following:

Sending command: HEAD /index.html HTTP/1.0 

-Reply from Server-
HTTP/1.1 200 OK
Date: Sun, 27 Jan 2002 21:31:03 GMT
Server: Apache/1.3.19 (Unix) mod_perl/1.25
Last-Modified: Thu, 10 Jan 2002 23:20:52 GMT
ETag: "2f6bc-1274-3c3e21d4"
Accept-Ranges: bytes
Content-Length: 4724
Connection: close
Content-Type: text/plain

791    Internet Protocol, IP
793    Transmission Control Protocol, TCP
1945   HTTP 1.0
2616   HTTP 1.1 includes status codes
2854   HTML

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

For server status
Uncomment the following lines to enable "server-status"
# <Location /server-status>
# SetHandler server-status
# Order deny,allow
# Deny from all
# Allow from yourserver.com
# < /Location>
To get more from the "server-status" handler set:
ExtendedStatus On
To test type the following in a browser:
yourserver.com/server-status
The module mod_status enables server-status. 

For server information
Uncomment the following lines to enable "server-info"
# < Location /server-info>
# SetHandler server-info
# Order deny,allow
# Deny from all
# Allow from yourserver.com
# < /Location>
To test type the following in a browser:
yourserver.com/server-info
The module mod_info enables server-info. 

See:
/opt/hpws/apache/conf/httpd.conf
For more info see:
httpd.apache.org/docs/vhosts/index.html

	go to top

Refer to the following files included with the software:
/opt/hpws/hp_docs/apache/apache.admin.guide
/opt/hpws/hp_docs/apache/ldap.admin.guide
/opt/hpws/hp_docs/apache/php.admin.guide
/opt/hpws/hp_docs/apache/ssl.admin.guide
/opt/hpws/hp_docs/apache/suexec.admin.guide
/opt/hpws/hp_docs/tomcat/tomcat.admin.guide
/opt/hpws/hp_docs/webmin/webmin.admin.guide

For specific requirements see:
Software Depot
Under "featured products" click "HP Apache-based Web Server".
Select the version of Apache that you are interested in.
Scroll down to the section called "system requirements".

For HP-UX Web Server Suite components see the following FAQs:
What are Webmin's requirements?
What are LDAP's requirements?
What are Perl's requirements?
What are PHP's requirements?
What are mod_jk's requirements?
What are Tomcat's requirements?
What are xmltool's requirements?

/opt/hpws/apache

/opt/hpws/webmin

/opt/hpws/tomcat

/opt/hpws/xmltools

B. If your classes are in a non-standard location then set "CLASSPATH" in the setClasspath.sh file:
/opt/hpws/tomcat/bin/setClasspath.sh
Change:
CLASSPATH=/path_to_classes:${CLASSPATH}

B. Move it to the desired location by typing:
/opt/hpws/util/altroot.sh /opt/hpws /path_to_hpws
For help with this script type:
/opt/hpws/util/altroot.sh -h

Note: Prior to running this script, ensure that none of processes (like Apache, Tomcat, Webmin, Stunnel, rotatelogs, logresolv) are running.

C. Set shared library path.
Some Apache binaries such as htpasswd expect shared libraries to be in standard locations. To run them you will need to set the SHLIB_PATH.
Edit the file:
/path_to_hpws/apache/bin/apachectl
Replace all occurrences of:
/opt/hpws
With:
/path_to_hpws

Manual method
A. Install the entire depot in /opt/hpws

B. Move it to the desired location
cp -pr /opt/hpws /path_to_hpws

C. Set shared library path:
Some Apache binaries such as htpasswd expect shared libraries to be in standard locations. To run them you will need to set SHLIB_PATH in your environment.Also ensure that your automatic scripts (like /path_to_hpws/apache/bin/apachectl) are set right. All the occurences of /opt/hpws should have been replaced with /path_to_hpws

D. In start/stop control file:
/path_to_hpws/apache/bin/apachectl
Replace all occurrences of:
/opt/hpws
With:
/path_to_hpws
And define HTTPD with a different server root:
HTTPD="/path_to_hpws/apache/bin/httpd -d /path_to_hpws"
For example without this step Apache will try to access the old
/opt/hpws/apache/logs directory

E. In automatic startup file:
/etc/rc.config.d/hpws_apacheconf
Replace:
HPWS_APACHE_HOME=/opt/hpws/apache
With:
HPWS_APACHE_HOME=/path_to_hpws/apache

Notes:
If you also plan to run Tomcat from a different directory then see:
How can I run Tomcat from a different directory?
If you are trying to run multiple Apache servers, you will have to specify separate port numbers for each server. See:
What are the default ports used by HP-UX Web Server Suite?
How can I find out what ports are used?

First, install the entire depot, and then move it to the desired location.
For example /new_path_to_tomcat
A. In main configuration file:
/opt/hpws/apache/conf/httpd.conf
Replace all occurances of:
/opt/hpws/tomcat
With:
/new_path_to_tomcat

B. Edit main start/stop file.
/new_path_to_tomcat/bin/startup.sh
Change:
TOMCAT_DIR=/opt/hpws/tomcat
To:
TOMCAT_DIR=/new_path_to_tomcat

C. Edit main configuration file.
/new_path_to_tomcat/conf/server.xml
Change:
Host name="localhost" debug="0" appBase="webapps"
to
Host name="localhost" debug="0" appBase="/new_path_to_tomcat/webapps"

D. In automatic startup file:
/etc/rc.config.d/hpws_tomcatconf
Replace:
HPWS_TOMCAT_HOME=/opt/hpws/tomcat
With:
HPWS_TOMCAT_HOME=/new_path_to_tomcat
If you are trying to run multiple Tomcat servers, you will have to specify separate port numbers for each server. See:
What are the default ports used by HP-UX Web Server Suite ?
How can I find out what ports are used?

For a more reasonable minimum add the following lines:
Timeout 300
KeepAlive On
MaxKeepAliveRequests 100
<IfModule worker.c>

StartServers 2
MaxClients 150
MinSpareThreads 25
MaxSpareThreads 75
ThreadsPerChild 25
MaxRequestsPerChild 0

A basic useable Apache would add access control, logging, and a more intelligent response header. This would involve loading the following modules and using their directives.
mod_access for access control.
mod_log_config for generic request logging.
mod_mime for response header generation for fixed content type/encoding.

For some basic scripting support that would enable dynamic content, you could add the following modules:
mod_cgi for Server-Side CGI implementation.
mod_include for Server-Side Includes. 

B. From the directory "/opt/hpws/apache/src/foo_module" compile the DSO file to generate a shared library.
/opt/hpws/apache/bin/apxs -c mod_foo.c foo_property.c

C. Install the DSO file into the Apache installation and activate it in the Apache configuration
This will automatically add the following to /opt/hpws/apache/conf/httpd.conf Automatic method:
/opt/hpws/apache/bin/apxs -i -a -n 'foo' mod_foo.so

Manual method:
cp /opt/hpws/apache/src/foo_module/mod_foo.so /opt/hpws/apache/modules/mod_foo.so
Make sure that the permissions and ownership are the same as the other modules.
Edit "/opt/hpws/apache/conf/httpd.conf" and in the "LoadModule" section add:
LoadModule foo_module modules/mod_foo.so

1. Single HP-UX Apache-based Web Server with Virtual Hosts (Recommended)

Using this method, one main server is launched which starts a main httpd process and a dynamic number of spare httpd processes. The Server daemon and spares are started using the apachectl script which specifies one configuration file httpd.conf and a Process ID file httpd.pid. The server can be configured to host multiple 'virtual hosts'. These virtual hosts can be 'Name Based' and share a single IP address or 'IP Based' where each virtual server requires its own IP address. A virtual server can also use a non-standard port number. Port 80 is the default non-SSL (http) port and Port 443 is the default SSL (https) port. See the FAQ: How do I setup testing environment for virtual hosting?.

2. Independent HP-UX Apache-based Web Servers (Not Recommended)

A disadvantage of running multiple web servers is that the multiple processes use more system resources. An advantage of running multiple HP-UX Apache-based Web Servers is that these servers can be started or stopped independently of each other. The "apachectl" script starts and stops all processes related to the main server. The solution to this problem is to create multiple 'instances' of the HP-UX Apache-based Web Server. 

Note: When copying files and creating directories, make sure the files or directories have the appropriate permissions and ownership. For example, if the server is running as user 'www' it needs permission to read the files (html) and in some cases write to the files (logs,pid).

For example, let's say one wanted to have separate instances of HP-UX Apache-based Web server for the 3 following web sites hosted on the same machine:
www.cats.org
www.dogs.org 
www.birds.org
After installing the default HP-UX Apache-based web server in /opt/hpws:

A. Make copies of the /opt/hpws/apache/bin/apachectl script and give each one a unique name. ie:
/opt/hpws/apache/bin/apachectl_cats
/opt/hpws/apache/bin/apachectl_dogs
/opt/hpws/apache/bin/apachectl_birds

B. Edit each of the new scripts to specify new httpd.pid and httpd.conf locations.
Note: Quotation marks "" are needed around the HTTPD runstring ie:
edit the following line in apachectl_cats:
PIDFILE=/opt/hpws/apache/cats_logs/httpd.pid
HTTPD="/opt/hpws/apache/bin/httpd -f /opt/hpws/apache/conf/httpd_cats.conf"

C. Make copies of the /opt/hpws/apache/conf/httpd.conf for each web server:
/opt/hpws/apache/conf/httpd_cats.conf
/opt/hpws/apache/conf/httpd_dogs.conf
/opt/hpws/apache/conf/httpd_birds.conf

D. Edit each of the new 'httpd_xxx.conf' files to specify different web sites settings:
ie, edit the file to specify the desired settings (values specified for example):
PidFile /opt/hpws/apache/cats_logs/httpd.pid
BindAddress 1.2.3.4 (only if each server uses a different IP address)
Listen 80 (each web site requires a different port # or a different IP address)
ServerName www.cats.org
DocumentRoot /html/wwwcats/docs
ErrorLog /opt/hpws/apache/cats_logs/error_log
CustomLog /opt/hpws/apache/cats_logs/access_log
etc... (don't forget the SSL directives as well.)

E. Start and stop each web server by typing:
/opt/hpws/apache/bin/apachectl_cats stop
/opt/hpws/apache/bin/apachectl_dogs stop
/opt/hpws/apache/bin/apachectl_birds stop
Or:
/opt/hpws/apache/bin/apachectl_cats start
/opt/hpws/apache/bin/apachectl_dogs start
/opt/hpws/apache/bin/apachectl_birds start

Add the following to httpd.conf:

<IfModule mod_proxy.c>
    ProxyRequests On
    < Proxy *>
        Order deny,allow
        Allow from all
    </Proxy>
</IfModule>

Now all URLs will be passed through yourserver.com on their way to the internet.
Further directives can be used restrict access

You can use the ProxyPass directive to redirect URLs.
For example:
ProxyPass / http://another.com/mirror
The above will take all requests to:
http://yourserver.com/
and send them to:
http://another.com/mirror

Proxies can be used in many different ways, for instance load balancing. They can be inside or outside the firewall. They can act as a firewall. 
Note: Caching is now done by mod_cache.

For more information see:
httpd.apache.org/docs/mod/mod_proxy.html

For example in "httpd.conf" a reverse proxy could have the following directives:

ProxyPass         /  http://foo.com/mirror
ProxyPassReverse  /  http://foo.com/mirror

Reasons to do this are:
A. Security because you want to hide the actual URL.
B. Transparency because you want to change the actual URL without the user knowing or caring. For example you don't want his bookmarks to change.
C. Accessibility since the user might not have access to the actual URL.

Request flow with and without reverse proxy enabled

Proxy Example	Reverse Proxy Example
1) Client Browser http://yourserver.com/mirror/foo/bar	1) Client Browser http://yourserver.com/mirror/foo/bar
2) Proxy Server ProxyPass /mirror/foo/ http://foo.com	2) Proxy Server ProxyPass /mirror/foo/ http://foo.com ProxyPassReverse /mirror/foo/ http://foo.com
3) Translation of URL http://yourserver.com/mirror/foo/bar is changed to: http://foo.com/bar	3) Translation of URL http://yourserver.com/mirror/foo/bar is changed to: http://foo.com/bar
4) Content Server http://foo.com/bar Assume that the content server redirects URL to: http://foo.com/new	4) Content Server http://foo.com/bar Assume that the content server redirects URL to: http://foo.com/new
5) Proxy Server gets back http://foo.com/new	5) Proxy Server gets back http://foo.com/new
	6) Reverse translation of URL http://foo.com/new is changed to: http://yourserver.com/mirror/foo/new
6) Client Browser gets back http://foo.com/new	7) Client Browser gets back http://yourserver.com/mirror/foo/new

For SSL logging edit file:
/opt/hpws/apache/conf/ssl.conf
And set:
ErrorLog logs/error_log

For auth_ldap logging edit file:
/opt/hpws/apache/conf/httpd.conf
And set:
LogLevel debug
Note: There are no special auth_LDAP logging directives.

For Tomcat logging edit file:
/opt/hpws/tomcat/conf/server.xml
And set:
<LogSetter name="tc_log" timestamps="true"

verbosityLevel="DEBUG" />

timestamps="true"

verbosityLevel = "DEBUG"

path="logs/servlet-${yyyyMMdd}.log"/>

timestamps="true"

path="logs/jasper-${yyyyMMdd}.log"

verbosityLevel = "DEBUG" />

For mod_jk logging edit file:
/opt/hpws/tomcat/jk/apache2/mod_jk.conf
And set:
JkLogFile /opt/hpws/tomcat/logs/jk.log

For a list of standard port numbers see:
www.iana.org/assignments/port-numbers

Look in /opt/hpws/apache/conf/httpd.conf under CustomLog.
For more info see:
httpd.apache.org/docs-2.0/mod/mod_log_config.html

In order to test "Virtual Hosts, we need to set-up a system so it can be accessed by multiple host/domain names. This can be done in two ways. One is to have site-IT make the necessary DNS changes. This means the whole site gets affected. Another is to isolate a test system, and make some configuration changes, such that our tests are isolated. 

A. Setting up the system hosting Apache webserver.
There are two ways.

(i) Without changing DNS entries:
Edit the file /etc/hosts
Change:

192.168.1.1 yourserver yourserver.com
127.0.0.1 localhost loopback

192.168.1.1 yourserver yourserver.com
192.168.1.1 foo www.foo.com
192.168.1.1 bar www.bar.com
127.0.0.1 localhost loopback

The above will allow the system to look at your /etc/hosts file first for any machine-name and if it wasn't found there, lookup using the DNS. 

(ii) Changing DNS entries
Edit your DNS lookup table to add:

192.168.1.1 foo www.foo.com
192.168.1.1 bar www.bar.com

In the file /opt/hpws/apache/conf/httpd.conf go to �Section 3: Virtual Hosts�.
Add the following:

NameVirtualHost 192.168.1.1

<VirtualHost foo>
    DocumentRoot /opt/hpws/apache/htdocs-foo
    ServerName www.foo.com
</VirtualHost>

<VirtualHost bar>
    DocumentRoot /opt/hpws/apache/htdocs-bar
    ServerName www.bar.com
</VirtualHost>

VirtualHost configuration:
    192.168.1.1:80 is a NameVirtualHost
    default server www.foo.com (/opt/hpws/apache/conf/httpd.conf:1299)
    port 80 namevhost www.foo.com (/opt/hpws/apache/conf/httpd.conf:1299)
    port 80 namevhost www.bar.com (/opt/hpws/apache/conf/httpd.conf:1304)

Create the file:
/opt/hpws/apache/htdocs-foo/index.html

Add the following:
<HTML>
<HEAD>

<TITLE>index.html for www.foo.com </TITLE>

<P>index.html for www.foo.com</P>

Create the file:
/opt/hpws/apache/htdocs-bar/index.html

Add the following:
<HTML>
<HEAD>

<TITLE>index.html for www.foo.com </TITLE>

<P>index.html for www.foo.com</P>

Then test by invoking the browser on the same server.
If you've selected option (i) in the previous FAQ: How do I setup testing environment for virtual hosting?, you can connect only from the system on which the Apache webserver is installed. If you've selected option (ii) in the previous step (modifying DNS), then you can connect from any system on the network. 

Enter the URL:
www.foo.com
You should see the text:
index.html for www.foo.com�

Enter the URL:
www.bar.com
You should see the text:
index.html for www.bar.com�

The access log is:
/opt/hpws/apache/logs/access_log
The access log may have more info on the errors that appear in the error log. In particular it will have status codes. The access_log is disabled by default. To enable the access_log, uncomment the following line in /opt/hpws/apache/conf/httpd.conf:
CustomLog logs/access_log common

For https errors see:
/opt/hpws/apache/logs/error_log

For suEXEC errors see:
/opt/hpws/apache/logs/suexec_log

For mod_rewrite errors see:
/opt/hpws/apache/logs/rewrite_log
By default this is not enabled so you need to edit:
/opt/hpws/apache/conf/httpd.conf
To enable mod_rewrite logs type:
RewriteLog logs/rewrite_log

For mod_cgi errors see:
/opt/hpws/apache/logs/script_log
By default this is not enabled so you need to edit:
/opt/hpws/apache/conf/httpd.conf
To enable cgi logs type:
ScriptLog logs/script_log

For Tomcat Java errors see:
In /opt/hpws/tomcat/logs/
tomcat.log is the main error log.
tomcat_startup.log saves not only startup info but also the standard output, STDOUT, and standard error, STDERR, from Tomcat.
jasper.log has jsp info.
servlet.log has servlet info.
jk.log has mod_jk info. 

For Cocoon errors see:
Cocoon produces execution log entries for debugging/auditing.
The amount of data to be logged can be controlled by log-level parameter in web.xml file. The default is DEBUG (maximum data). By default, the log file is:/opt/hpws/tomcat/webapps/cocoon/WEB-INF/logs/cocoon.log.
Cocoon keeps the generated .java files in a directory tree starting at (by default):/opt/hpws/tomcat/webapps/work/localhost_8080%2Fcocoon/org/apache/cocoon/www
Files created by LogTransformer are kept (by default) in /opt/hpws/tomcat directory.

B. Increase the log level
Increasing the log level will slow down the server. You should reset the log levels after the problem is solved.

For Apache problems
In /opt/hpws/apache/conf/ http.conf
Set:
LogLevel debug
CustomLog /opt/hpws/apache/logs/access_log combined

For https problems
In /opt/hpws/apache/conf/ssl.conf
Set:
LogLevel debug

For mod_ rewrite problems
In /opt/hpws/apache/conf/httpd.conf
Set:
RewriteLogLevel 9

For Tomcat Java problems
In /opt/hpws/tomcat/conf/server.xml
There are various "Logger" tags. In each one you can set the verbosity attribute.
For example set:
verbosity = 4

For more information see:
http://yourserver.com/hp_docs/tomcat/tomcat_manual/config/logger.html

For PHP problems
See "Error handling and logging" in:
/opt/hpws/apache/conf/php.ini

For mod_jk problems
In /opt/hpws/tomcat/jk/apache2/mod_jk.conf
Set:
JkLogLevel debug

For auth_ldap problems
In /opt/hpws/apache/conf/http.conf
Set:
LogLevel debug
Note: There are no special auth_LDAP logging directives.

For more info on log files see:
httpd.apache.org/docs-2.0/logs.html

C. Check permissions.
First give read/write/execute permissions to appropriate files. See if this works. If it does then gradually reduce permissions to minimum that works. If it doesn't then at least you have eliminated permissions as a cause of the problem. 

D. Look at configuration files.
The configuration files are heavily commented and act as help files.

/opt/hpws/apache/conf/httpd.conf
/opt/hpws/apache/conf/ssl.conf
/opt/hpws/apache/conf/cache.conf
/opt/hpws/apache/conf/ldap.conf
/opt/hpws/tomcat/conf/server.xml
/opt/hpws/tomcat/jk/apache2/mod_jk.conf
/opt/hpws/tomcat/jk/apache2/workers.properties

E. Use tools
ApacheBench can be used as a command line browser to test the web server.
For usage type:
/opt/hpws/apache/bin/ab -h
If you need more info set the verbosity to a high level.
For example:
-v 9

Status codes are grouped as follows:

100-199   Informational.
200-299 Client Request successful.
300-399 Client request redirected, further action necessary.
400-499 Client request incomplete.
    400 Bad Request 
    401 Unauthorized 
    402 Payment Required 
    403 Forbidden 
    404 Not Found 
    405 Method Not Allowed 
    406 Not Acceptable 
    407 Proxy Authentication Required 
    408 Request Timeout 
    409 Conflict 
    410 Gone 
    411 Length Required 
    412 Precondition Failed 
    413 Request Entity Too Large 
    414 Request-URI Too Long 
    415 Unsupported Media Type 
    416 Requested Range Not Satisfiable 
    417 Expectation Failed 
500-599 Server errors.
    501 Not Implemented 
    502 Bad Gateway 
    503 Service Unavailable 
    504 Gateway Timeout 
    505 HTTP Version Not Supported

LogFormat "%h %l %u %t \"%r\" %>s %b" common
CustomLog logs/access_log common

See comments and examples in:
/opt/hpws/apache/conf/httpd.conf

The program "logresolve" can resolve IP addresses into names and extract statistics from the log files.
For usage type:
/opt/hpws/apache/bin/logresolve -h
For info see:
httpd.apache.org/docs-2.0/programs/logresolve.html

File does not exist
Verify that the file exists and that httpd.conf is configured so that it can find it. 

Premature end of script headers
This implies a CGI problem. Many things can cause this error message. Check file permissions. Check path to executable for example Perl in script header should be #!/opt/perl/bin/perl. Check script syntax. Try running the script from the command line. 

"Apache.pm" failed to load
This is usually due to Perl binaries not being in the PATH.
/opt/hpws/apache/bin/apachectl should set the environment variable PERL5LIB correctly. If you start Apache with /opt/hpws/bin/httpd instead and PERL5LIB is not set properly then you will get this error.

SIGBUS or Segmentation fault
This is a severe problem. Check for a bad module or configuration in recent additions to the web server suite. Sometimes these problems only occur under heavy load.

(233)No buffer space available: accept: (client socket)
In general this error can be ignored. This error will be generated in the following scenario:
A. A client makes a new TCP connection to the server.
B. The new connection is queued on the servers LISTEN socket.
C. Client sends a TCP reset on the connection.
D. Server calls accept.
E. Accept fails and server will log the error and shut down httpd process handling it.
Note that if the client comes back with a new request it will be properly handled.

Then you need to do the following: 
Edit the file "/opt/hpws/apache/bin/apachectl" and add:
export LD_PRELOAD="/usr/lib/libpthread.sl:/
usr/contrib/oracle/lib/libjava.sl"

Did you run the script /opt/hpws/apache/util/chroot_os_cp.sh?
Also see Troubleshooting in:
/opt/hpws/hp_docs/apache/utilities.user.guide.

Check the error_log file. 
If /opt/hpws/apache/logs/error_log says "Apache.pm" failed to load then mod_perl has not loaded and all perl scripts will fail. This is usually due to perl binaries not being in the PATH or the PERL5LIB environment variable not being set to include following as a single line:
/opt/hpws/apache/lib/perl/lib/site_perl/5.6.1/PA-RISC1.1-thread-multi:/opt/hpws/apache/lib/perl/lib

SOLUTION: Verify that perl is installed in /opt/perl/bin and that /opt/perl/bin/perl and /opt/perl/lib/5.6.1 exist. Next specify where the mod_perl libraries are installed with the following command as a single line:
export PERL5LIB=/opt/hpws/apache/lib/perl/lib/site_perl/5.6.1/PA-RISC1.1-thread-multi:/opt/hpws/apache/lib/perl/lib

The PERL5LIB environment variable is preset by the shell running the Apache executable. If you experience problems, manually set this environment variable as shown above.

To test whether you have the correct 5.6.1 on your system type:
/opt/perl/bin/perl -v

PA-RISC versions of HP-UX Web Server Suite should say it is "v5.6.1"" and that it is "provided by ActiveState Tool Corp". IPF (Itanium) versions of HP-UX Web Server Suite should say it is "v5.6.1 built for IA64" and that it is "provided by ActiveState Tool Corp". If not, you need to install the correct HP-UX release of perl.
First download Perl from the URL software.hp.com/ then:
In the left navigation bar, click on "search". 
Use keywords: Perl v.5.6.1 

The solution is to either always start Tomcat as "www" or always start Tomcat with users who belong to the same group 

One solution to get rid of the problem is by having the statement "Listen 443" ahead of "Listen 80" in httpd.conf (and getting rid of "Listen 443" from ssl.conf.

A. .htaccess files
Authentication by user name/password. Hidden .htaccess files restrict access to files at this point and below in the file system. 

B. mod_auth
Authentication by user name/password.

C. mod_auth_anon
Authentication by anonymous name/email address.

D. mod_auth_dbm
Authentication by user name/password from a UNIX NDBM database.

E. mod_ssl
Authentication by exchanging client and server SSL certificates. 

F. mod_auth_ldap
Authentication from an LDAP server. 

  require user me

In /opt/hpws/apache/conf/ssl.conf:
Replace:
SSLCertificateKeyFile /opt/hpws/apache/conf/ssl.key/server.key
With:
SSLCertificateKeyFile /opt/hpws/apache/conf/ssl.key/server1.key

If necessary, update /opt/hpws/apache/conf/ssl.conf: 
Replace:
SSLCertificateKeyFile /opt/hpws/apache/conf/ssl.key/server1.key
With:
SSLCertificateKeyFile /opt/hpws/apache/conf/ssl.key/server2.key

B. Or use /opt/hpws/apache/bin/mkcert.sh which has built-in usage/help documentation.

Edit or create the following file and append the downloaded CA certificate.
Refer to the /opt/hpws/hp_docs/apache/ssl.admin.guide for detailed instructions.

Now only certificates signed by a CA whose certificates is in Apache's ca.bundle.crt file will be accepted. All others will be rejected.

See:
/opt/hpws/apache/bin/chroot_os_cp.sh

A. It allows cgi scripts in the "ScriptAlias" directory (default /cgi-bin) to be executed as the owner:group defined by the "SuexecUserGroup" directive in httpd.conf. (HP-UX Apache-based Web Server only)

B. It allows the scripts located in "~user/public_html" directory to be executed as CGI scripts with the users limited permissions.
The administrator needs to:
i. Have ExecCGI option set for the directory <Directory /home/*/public_html>
ii. Set up, "AddHandler cgi-script .cgi", for the directory.
This enables users to run the ".cgi" file in their "public_html" directory as a cgi script. Without suEXEC these scripts will run as "www:other" (or whatever is specified by the User/Group directive for the server). For security reasons it is better to run these cgi scripts under the limited permissions of user.

See:
http://httpd.apache.org/docs-2.0/suexec.html

In webmin, http://yourserver.com:10000
On the servers tab, click on "HP-UX Apache-based Web Server"
Click on "Edit Defined Parameters"
In the text field type: "-DSSL" 
Click on "save"
Stop and start Apache from the top right links. 

A. Disable indexing of directories.
With the "Options" directive don't use "Indexes" or "All" which enable index generation. Indexes are dynamically generated for every access. It is much better to create an "index.html" file instead.

B. Logging
Disable logging as much as possible. If necessary write each log to their own file system using different high speed disks. This will decrease delays caused by disk scheduling.

C. Set the following directives:
KeepAlive on
HostNameLookups off

D. With the "Options" directive use "FollowSymLinks" not "SymLinksIfOwnerMatch".

E. For local directory URL's put a forward slash, "/", at the end. That way the server can avoid needless file searches.

F. Deny access to well mannered spiders or web crawlers with a "robots.txt" file under the document root. The file has "User-Agent" and "Disallow" directives that limit access to URLs.

G. Use a high speed backend connection between the web server and database.

H. Avoid JSP's. Instead use Perl, C, C++, or Java modules.

I. For images:
Specify height and width.
Keep size small.
Minimize number of images.
Avoid animations.
Don't use macromedia flash on home pages.

J. Don't combine large and small images into same file.
Put alternate large images into a seperate file since many users will not choose to view the large image. 

A. Use only one echo or print statement in the script. Use array or concatenation to compose the html then send with only one echo or print.

B. Use the set of output buffer (ob_???) functions newly available in PHP4. For example ob_start.

C. Use an accelerator. Search the web for "PHP Accelerator" and you will find several accelerators, some of which are free. 

kernel parameters 

STRMSGSZ	65535
dnlc_hash_locks	512
create_fastlinks	1
dbc_max_pct	15
dbc_min_pct	15
eqmemsize	2048
max_thread_proc	2048
maxdsiz	0X40000000
maxdsiz_64bit	0X40000000
maxfiles	2048
maxfiles_lim	2048
maxssiz	0X17f00000
maxssiz_64bit	0X40000000
maxswapchunks	16384
maxtsiz	0X40000000
maxtsiz_64bit	0X40000000
maxuprc	512
maxusers	2048
maxvgs	64
msgmax	32768
msgmnb	65535
msgmni	3200
msgseg	32767
msgssz	32
msgtql	32000
nflocks	2000
npty	60
nstrpty	60
nstrtel	60
o_sync_is_o_dsync	1
semmni	4096
semmns	4096
semmnu	2048
semume	64
semvmx	32768
shmmax	0X40000000
shmmni	1024
shmseg	512
swchunk	4096
vps_ceiling	64

network parameters 

tcp_time_wait_interval	60000
tcp_conn_req_max	1024 --> 4096
tcp_ip_abort_interval	60000
tcp_keepalive_interval	900000
tcp_rexmit_interval_initial	1500
tcp_rexmit_interval_max	60000
tcp_rexmit_interval_min	500
tcp_xmit_hiwater_def	32768
tcp_recv_hiwater_def	32768

The "ndd" command is used for network tuning.
To check the current setting of the system listen queue:
ndd -get /dev/tcp tcp_conn_request_max
For example to adjust the system listen queue size to 256:
ndd -set /dev/tcp tcp_conn_request_max 256

A. Copy Tomcat
cd /opt/hpws
cp -pr tomcat tomcat2

B. Edit:
/opt/hpws/tomcat2/conf/server.xml
Change:
<Host name="localhost" debug="0" appBase="webapps"
To:
<Host name="localhost" debug="0" appBase="/opt/hpws/tomcat2/webapps">

Change HTTP/1.1 Connector port:
port="8081"
To:
port="8091"

Change AJP 1.3 Connector port:
port="8009"
To:
port="8019"

Change:
<Server port="8005"/>
To:
<Server port="8015"/>

Change:
Context path="/examples" docBase="/examples"
To:
Context path="/examples2" docBase="examples"

C. Change ports in worker configuration file.
Edit /opt/hpws/tomcat/jk/apache2/workers.properties
Change:
worker.list=ajp13
To:
worker.list=tomcat, tomcat2
Comment out:
worker.ajp13.port=8009
worker.ajp13.host=localhost
worker.ajp13.type=ajp13

Add:
worker.tomcat.port=8009
worker.tomcat.host=localhost
worker.tomcat.type=ajp13
worker.tomcat2.port=8019
worker.tomcat2.host=localhost
worker.tomcat2.type=ajp13

D. Add context for our second Tomcat.
Since Apache already reads /opt/hpws/tomcat/jk/apache2/mod_jk.conf we will add it there.
Edit /opt/hpws/tomcat/jk/apache2/mod_jk.conf
Comment out:
JkMount /examples ajp13
JkMount /examples/* ajp13
Add the following lines:
JkMount /examples tomcat
JkMount /examples/* tomcat
JkMount /examples2 tomcat2
JkMount /examples2/* tomcat2

F. Test
Edit a sample index file
/opt/hpws/tomcat2/webapps/examples/jsp/index.html
Change title from:
JSP Samples
To:
Tomcat2 JSP Samples
As root stop Apache, Tomcat, and Tomcat2.

/opt/hpws/apache/bin/apachectl stop
/opt/hpws/tomcat/bin/shutdown.sh
/opt/hpws/tomcat2/bin/shutdown.sh

/opt/hpws/apache/bin/apachectl start
/opt/hpws/tomcat/bin/startup.sh
/opt/hpws/tomcat2/bin/startup.sh

To test the second Tomcat, in a browser enter:
http://yourserver.com/examples2/jsp/
You should see:
Tomcat2 JSP Samples

	go to top

B. Set file permissions and ownership to:
-rwxr-xr-x bin bin mod_foo.so

C. Edit the file:
/opt/hpws/apache/conf/httpd.conf
Add the LoadModule directive. For example:
LoadModule foo_module modules/mod_foo.so

	go to top

For the Webmin Home Page:
www.webmin.com/webmin/

For the Webmin User's Guide:
www.swelltech.com/support/webminguide/server-apache.html

If you have the wrong version of Perl you will get errors similar to the following:

syntax error in file /opt/hpws/webmin/miniserv.pl at line 6, next 2 tokens "use Socket"
syntax error in file /opt/hpws/webmin/miniserv.pl at line 41, next 2 tokens "\Net:"

	go to top

See the file in the Apache bundle:
/opt/hpws/hp_docs/admin-guide

The IPv6 product supports IPv4 as well as IPv6.

HP-UX 11.23 onwards comes with IPv6.

PA-RISC 11i
For java support you must have Java 1.4.

lan0: flags=843<UP,BROADCAST,RUNNING,MULTICAST>
inet 111.222.333.444 netmask ffffff00 broadcast 111.222.333.255
lan0: flags=4800841<UP,RUNNING,MULTICAST,ONLINK>
inet6 fe80::210:83ff:feff:da14 prefix 10

C. Ensure that "/etc/nsswitch.conf" has a line corresponding to "ipnodes". An example entry is shown below:
ipnodes: dns [NOTFOUND=continue] files
More information on IPv6 configuration can be found in the documentation that comes with IPv6 product.

B. Partial Support
Although the following components works on IPv6 platform, they may not behave correctly for networking calls related to IPv6 addresses, due to lack of underlying support.
- CGI (Perl-based)
- mod perl
- Webmin

CGI scripts written in Perl will return failure for any calls to, say, gethostbyname() for the IPv6 addresses, as Perl does not support IPv6. Hence, CGI, mod_perl and Webmin are supported only in IPv4 mode.

Since HP-UX Apache-based Web Server implements the SSL using the OpenSSL library, mod_ssl does not support IPv6 addresses.

Currently there are no IPv6 compatible clients for WebDAV. Hence, WebDAV with IPv6 addresses is not supported for this release of HP-UX Apache-based Web Server.

If your LDAP server is not IPv6 capable, then you will need to configure your auth_ldap to connect to the LDAP server using the IPv4 address.

Stunnel currently does not have IPv6 capabilities, i.e. it cannot listen on IPv6 addresses. Therefore, when one starts Stunnel they need to specify an IPv4 address/port for Stunnel. Hence your auth_ldap configuration should point to the IPv4 address/port that Stunnel is listening on.

OpenSSL does not have support for IPv6. However, on an IPv6 machine, it could still be used in IPv4 mode.

/opt/hpws/apache/bin/ab implements SSL using OpenSSL. Since OpenSSL does not have support for IPv6, ab does not either.

Currently, there are no SSL clients available from HP on HP-UX for IPv6. However, one could use the standard SSL clients in IPv4 mode.

Client side:
You need a client that is enabled to interact with the WebDAV server. Windows 2000 is enabled by default. WindowsNT may not have complete support for �Web Folders� and hence you may not be able to fully test WebDAV with an NT client. 

A. Load Modules
Edit:
/opt/hpws/apache/conf/httpd.conf
Uncomment or add the following:

#LoadModule dav_module mod_dav.so
#LoadModule dav_fs_module mod_dav_fs.so

Note: WebDAV will create files under the /some/path/� directory with the prefix "DAVLock". Any prefix and path can be used. However, ensure that this directory exists and is on a non-NFS mounted file system.

After line:
<Directory "/opt/hpws/apache/htdocs">
Add the following line:
DAV On

Note: The same can be done within a <Location> directive.

C. Change ownership
chown �R www:other /opt/hpws/apache/htdocs

D. Restart Apache
/opt/hpws/apache/bin/apachectl stop
/opt/hpws/apache/bin/apachectl start

E. Verify if DAV works:
Windows2000 ONLY:
1) Double click the �My Network Places� icon on the Windows 2000 desktop.
2) Double click �Add Network Place
3) Enter the following URL:
yourserver.com/
4) Provide a simple display name for this WebDAV folder.
5) Result/Output:
If able to connect successfully to the WebDAV server and a web-folder is created on the Windows machine, then our WebDAV server is working.

WindowsNT ONLY:
1) Double click on �Network Neighbourhood
2) Click on the �Network Neighbourhood� drop-down list, and select �Web Folders
3) Double click on �Add Web Folder�.
4) Enter the following URL:
yourserver.com/
5) Provide a simple display name for this WebDAV folder.
6) Result/Output:
If able to connect successfully to the WebDAV server and a web-folder is created on the Windows machine, then our WebDAV server is working.
Note: WindowsNT may not have complete support for �Web Folders� and hence you may not be able to fully test WebDAV. 

	go to top

cpan.perl.org Comprehensive Perl Archive Network (CPAN) has lots of Perl software.
dbi.perl.org for the home of the database interface to Perl. 

For IPF (Itanium):
CGI will work with any Perl.
mod_perl requires HP's 64 bit Perl 5.6.1.

Download Perl from www.software.hp.com.
Search for: Perl v.5.6.1

B. mod_perl method
In the file:
/opt/hpws/apache/conf/httpd.conf
uncomment the mod_perl LoadModule directive
LoadModule perl_module modules/mod_perl.so
In the same file, also uncomment the section
<IfModule mod_perl.c> ... </IfModule>
This will allow all files ending with *.pl to be run through the Perl module. 

#export LD_PRELOAD="/usr/lib/libpthread.sl:/usr/lib/libcl.sl:/path_to_oracle/lib/libjava.sl"

export ORACLE_HOME = /path/to/oracle-8.1.6/client/side/libraries
export SHLIB_PATH=$SHLIB_PATH:$ORACLE_HOME/lib
export LD_PRELOAD=$LD_PRELOAD:$ORACLE_HOME/JRE/lib/PA_RISC/native_threads/
libjava.sl
export ORACLE_SID=YourConnectionName

Assuming a database with a customer table containing name and address fields, a simple MySQL example is:

<?
    @ $db = mysql_pconnect("localhost", user, password);
    if (!db)
    {
        echo "Error: Couldn't connect";
    }
    mysql_select_db("customers");
    $query = "select * from customers";
    $result = mysql_query($query);
    $num_results = mysql_num_rows($result);
    for ($i = 0; $i < $num_results; $i++)
    {
        $row = mysql_fetch_array($result);
        echo "&ltp>i+1).". Name: ";
        echo $row["name"];
        echo "&ltbr> Address: ";
        echo $row["address"];
        echo "&ltp>";
    }
?>

	go to top

"Apache Jakarta-Tomcat", by James Goodwill, APress.
"Core Servlets and JavaServer Pages (JSP)", by Marty Hall, Prentice Hall PTR.
"Professional Java Server Programming J2EE Edition", by Allamaraju,Avedal, Browett, et.al., Wrox Press.
"Java Developer's Guide to Servlets and JSP", by Bill Brogden, Sybex Inc.

If you wish to use JSPs (Java Server Pages) then you also need the JDK (Java Development Kit) so that you can compile JSPs.

For PA-RISC:
HP JDK 1.2.2.04 or higher must be used.
The latest version of Java 1.3.x can be downloaded from:
www.hp.com/products1/unix/java/java2/sdkrte1_3/index.html.
The latest version of Java 1.2 can be downloaded from:
www.hp.com/products1/unix/java/java2/sdkrte/index.html.

For IPF (Itanium):
HP JDK 1.3.x.0 for IPF or higher must be used.
The latest version of Java 1.3.x can be downloaded from www.hp.com/go/java/.

For IPv6 support Java 1.4 is required. 

To start Tomcat:
/opt/hpws/tomcat/bin/startup.sh
To stop Tomcat:
/opt/hpws/tomcat/bin/shutdown.sh

	go to top