Apache Web Server for SCO UnixWare 7 Release and Installation Notes

System requirements
Installing and removing Apache
    pkgadd procedures
    Application Installer procedures
    Removing Apache
Installation directory
Existing server configuration files and content
Starting and stopping the Apache web server
Port 80 default server, and interactions with Netscape FastTrack
Documentation notes
Apache and Microsoft FrontPage
SCO Webtop integration
Managing DBM and DB authorization files

Apache for UnixWare 7 is a robust, full-featured HTTP web server derived from the Apache Project open source server.

The following notes apply only to the supported Apache web server installation, Apache release 1.3.9, on UnixWare 7 systems. For notes on other Apache releases, specifically the Skunkware release of Apache, consult the relevant Skunkware documentation.

System requirements

Apache software
Apache documentation

NOTE: If you have installed the Skunkware version of Apache, you must remove it before installing this release. The package names conflict (both packages are named 'apache'), and this will cause problems if an attempt is made to keep both packages on the same system. Before removing the Skunkware version of Apache, back up your htdocs and cgi-bin directories, as well as any configuration files that you wish to preserve.

Installing and removing Apache

To install Apache from the UnixWare 7 Release 7.1.1 Updates CD-ROM or downloaded files, use the Application Installer or pkgadd(1M)

pkgadd procedures

To install the package from downloaded files:

Log in as root.
Download the package to an installation directory; for example, /tmp.
Run the pkgadd(1M) command by entering:

pkgadd -d /tmp/Apache.pkg

To install the package from media distribution:

Log in as root.
Insert the CD-ROM in the drive if you have not already done so.
You can use the pkgadd(1M) command to install with the distribution CD mounted or unmounted (you may have mounted the CD to read these Release Notes from the distribution media):

mounted

pkgadd -d

/mount_point

Apache

unmounted

pkgadd -d cdrom1

Apache

The Apache package is a set installation that encompasses both the Apache runtime and the Apache documentation, and allows you to select individual components to install.

Application Installer procedures

If you are using the Application Installer:

Start the Application Installer by clicking on the Application Installer icon in the SCOadmin folder on the UnixWare 7 desktop.
Select the correct device from which to install (for example, CD-ROM_1).
Click on Update View to see the products that are available to install.
Select the product set and click on Install.

Depending on the product you are installing, you may need to respond to some additional prompts. Answer these prompts as appropriate for your installation.

Repeat this step for each package you want to install.

When you have installed all desired packages, select Actions->Exit.

Removing Apache

To remove a layered product or patch, use the Application Installer or pkgrm(1M)

See ``Installing, managing, and removing software'' for details.

Installation directory

The Apache server root directory is /usr/internet/apache. In this directory you will find the following subdirectories:

/bin

Apache executable programs

/cgi-bin

Location for CGI-bin gateway programs; this directory and programs in it are created on installation if no such directory already exists, otherwise, the existing files are left in place

/cgi-bin-default

The source for a cgi-bin directory if none exists on installation

/conf

Apache configuration files

/htdocs

Location for HTML content files; this directory and files in it are created on installation if no such directory already exists, otherwise, the existing files are left in place

/htdocs-default

The source for an htdocs directory if none exists on installation

/icons

Images used by Apache when creating HTML pages, typically directory indexes

/include

C-language header files for Apache data structures

/libexec

Dynamically loadable .so files

/libextra

Additional libraries used when building Apache

/logs

Default location of the server access and error log files

/man

Nroff format manual pages for the server and various support utilities

/proxy

Caching directory for the Apache proxy module

Existing server configuration files and content

On installation, Apache will preserve any existing configuration files it finds, renaming them to files with a .bak extension.

If existing /htdocs and /cgi-bin directories are found on the system, the Apache installation will not install its own web server content. Otherwise, it builds up a default set of content from the /htdocs-default and /cgi-bin-default directories.

Starting and stopping the Apache web server

The normal way to start an Apache web server is using the apachectl script; this script is provided in the /bin subdirectory of the Apache installation.

As an alternative, the /usr/sbin/apache script is provided. This script also allows the server to be enabled to start on system boot. See the apache(1M) manual page for details of how to use this script.

Port 80 default server, and interactions with Netscape FastTrack

By default, Apache creates a port 80 web server instance, and creates some default server content if none exists already. This server runs as user nobody, and serves documents from /usr/internet/apache/htdocs.

If the Netscape FastTrack port 80 server is already running on the system, the Apache port 80 server will fail to start, and log the following type of message to its error log file:

[crit] (125)Address already in use: make_sock: could not bind to port 80

In this case, either stop, or even disable, the FastTrack server before starting Apache, or move one or the other of the servers to a different port.

In general, both Apache and Netscape FastTrack can run together on a single system, providing that they are not trying to listen on the same network port or ports.

Documentation notes

The manual pages for the main Apache server and its supporting programs are built into SCOhelp. Install the apacheD (Apache documentation) package to enable this feature.

NOTE: The main Apache User's Guide, and other server documentation that is not simple manual pages, is not integrated into SCOhelp. This documentation is however served by the default port 80 web server instance on installation. If you have disabled the default port 80 server, or replaced the content with your own files, you can still access the documentation by pointing a browser at the local files in

file:/usr/internet/apache/htdocs-default/manual

Alternatively, you can access the Apache documentation directly from the Apache organization, at http://apache.org.

Apache and Microsoft FrontPage

This release of Apache contains the FrontPage 'glue' module mod_frontpage.c. However, this is not the complete FrontPage product; the module contains only the server redirections necessary to allow it to work with a FrontPage installation.

On installation, if Apache determines that FrontPage is not present (that is, no directory /usr/local/frontpage exists), this FrontPage module is automatically disabled by default in the Apache httpd.conf configuration file.

The mod_frontpage module supplied with this release should function with both FrontPage 98 and FrontPage 2000. If you wish to install Microsoft Frontpage for SCO UnixWare, you can obtain it from Ready-to-Run Software.

SCO Webtop integration

On installation, the Apache web server configures its default port 80 server instance to serve the SCO Webtop. If the Webtop is already installed, then the server at port 80 will serve it immediately. If the Webtop is not installed, then the server at port 80 will serve it as soon as it is installed.

Webtop administrative access is controlled by a server authentication file, stored in

/var/webtop/users-apache

If this file does not exist on installation, it is created to allow access for a username 'root' and a password equal to the current superuser password.

If the file already exists on installation, no new entries are added, and the file is left unchanged.

If the Apache package is removed from the system, this file will not be removed automatically; if it is necessary to remove it, this must be done manually.

Managing DBM and DB authorization files

The standard Apache tool for managing DBM and DB authentication files is dbmmanage(1M). In this release, dbmmanage(1M) is only capable of managing DBM format authorization files.

To manage DB format authorization files, a small additional tool, dbfile, is provided. This tool may be found in the /usr/internet/apache/bin directory.

The dbfile program creates or updates a DB format file from a list of usernames and encrypted passwords that it reads from standard input (one pair per line, separated by whitespace). You can, for example, convert an existing .htpasswd authorization file into a DB format file called authfile.db, using the following command:

awk -F: '{ print $1 " " $2 }' < .htpasswd | \
/usr/internet/apache/bin/dbfile authfile.db

Input for dbfile can also be prepared manually, or using other system tools. If an input line contains a username only, that entry is deleted from the database. If the input line contains both a username and an encrypted password, that entry is either appended to the database, or used to replace the password if an entry for that username already exists.

The -d option to dbfile allows you to view the contents of the database, by writing it to standard output. For example:

/usr/internet/apache/bin/dbfile -d authfile.db

There is no separate documentation for the dbfile utility.

More information on the DB database file format may be obtained from http://www.sleepycat.com.

Software:	SCO UnixWare 7, 7.0.1, or 7.1, or greater
RAM:	>64MB
Disk Space:	4MB free disk space