Using Apache With Novell NetWare

This document explains how to install, configure and run Apache 2.0 under Novell NetWare 6.0 and above. If you find any bugs, or wish to contribute in other ways, please use our bug reporting page.

The bug reporting page and dev-httpd mailing list are not provided to answer questions about configuration or running Apache. Before you submit a bug report or request, first consult this document, the Frequently Asked Questions page and the other relevant documentation topics. If you still have a question or problem, post it to the novell.devsup.webserver newsgroup, where many Apache users are more than willing to answer new and obscure questions about using Apache on NetWare.

Most of this document assumes that you are installing Apache from a binary distribution. If you want to compile Apache yourself (possibly to help with development, or to track down bugs), see the section on Compiling Apache for NetWare below.

NetWare service packs are available here.

Apache 2.0 for NetWare can also be run in a NetWare 5.1 environment as long as the latest service pack or the latest version of the NetWare Libraries for C (LibC) has been installed . WARNING: Apache 2.0 for NetWare has not been targeted for or tested in this environment.

Follow these steps to install Apache on NetWare from the binary download (assuming you will install to sys:/apache2

along with any file path values to reflect your correct server settingsSYS:/APACHE2

to the search path, for example: SEARCH ADD SYS:\APACHE2

on a NetWare volumeAPACHE2.NLM

directory\HTTPD-2.0\DOCS\ICONS

on the serverSYS:/APACHE2/CGI-BIN

file searching for all @@Value@@

markers and replacing them with the appropriate settingSYS:/APACHE2

Apache may be installed to other volumes besides the default SYS

During the build process, adding the keyword "install" to the makefile command line will automatically produce a complete distribution package under the subdirectory DIST

. Install Apache by simply copying the distribution that was produced by the makfiles to the root of a NetWare volume (see: Compiling Apache for NetWare below).

This will load Apache into an address space called apache2. Running multiple instances of Apache concurrently on NetWare is possible by loading each instance into its own protected address space.

After starting Apache, it will be listening to port 80 (unless you changed the

directive in the configuration files). To connect to the server and access the default page, launch a browser and enter the server's name or address. This should respond with a welcome page, and a link to the Apache manual. If nothing happens or you get an error, look in the Listenerror_log

Once your basic installation is working, you should configure it properly by editing the files in the conf

To unload Apache running in the OS address space just type the following at the console:

When working with Apache it is important to know how it will find the configuration files. You can specify a configuration file on the command line in two ways:

specifies a path to a particular configuration file apache2 -f "vol:/my server/conf/my.conf"

In these cases, the proper

. Invoking Apache with the -V

switch will display this value labeled as SERVERCONFIGFILE

. Apache will then determine its

by trying the following, in this order:ServerRoot

Apache 2.0 for NetWare includes a set of command line directives that can be used to modify or display information about the running instance of the web server. These directives are only available while Apache is running. Each of these directives must be preceded by the keyword APACHE2

By default these directives are issued against the instance of Apache running in the OS address space. To issue a directive against a specific instance running in a protected address space, include the -p parameter along with the name of the address space. For more information type "apache2 Help" on the command line.

The main differences in Apache for NetWare are:

Because Apache for NetWare is multithreaded, it does not use a separate process for each request, as Apache does on some Unix implementations. Instead there are only threads running: a parent thread, and multiple child or worker threads which handle the requests.

Therefore the "process"-management directives are different:

- Like the Unix directive, this controls how many connections a worker thread will serve before exiting. The recommended default, MaxConnectionsPerChildMaxConnectionsPerChild 0

, causes the thread to continue servicing request indefinitely. It is recommended on NetWare, unless there is some specific reason, that this directive always remain set to 0

- This directive tells the server how many threads it should start initially. The recommended default is StartThreadsStartThreads 50

- This directive instructs the server to spawn additional worker threads if the number of idle threads ever falls below this value. The recommended default is MinSpareThreadsMinSpareThreads 10

- This directive instructs the server to begin terminating worker threads if the number of idle threads ever exceeds this value. The recommended default is MaxSpareThreadsMaxSpareThreads 100

- This directive limits the total number of work threads to a maximum value. The recommended default is MaxThreadsThreadsPerChild 250

- This directive tells the server what size of stack to use for the individual worker thread. The recommended default is ThreadStackSizeThreadStackSize 65536

The directives that accept filenames as arguments must use NetWare filenames instead of Unix names. However, because Apache uses Unix-style names internally, forward slashes must be used rather than backslashes. It is recommended that all rooted file paths begin with a volume name. If omitted, Apache will assume the SYS:

Apache for NetWare has the ability to load modules at runtime, without recompiling the server. If Apache is compiled normally, it will install a number of optional modules in the \Apache2\modules

directive must be used. For example, to active the status module, use the following:LoadModule

Information on creating loadable modules is also available.

- This directive maps a CGI file extension to a script interpreter.SecureListen

- Enables SSL encryption for a specified port.NWSSLTrustedCerts

- Adds trusted certificates that are used to create secure connections to proxied servers.NWSSLUpgradeable

- Allow a connection created on the specified address/port to be upgraded to an SSL connection.Compiling Apache requires MetroWerks CodeWarrior 6.x or higher. Once Apache has been built, it can be installed to the root of any NetWare volume. The default is the sys:/Apache2

markers and replacing them with the appropriate setting. Copy over the conf/magic

and conf/mime.types

files as well. Alternatively, a complete distribution can be built by including the keyword install

The following development tools are required to build Apache 2.0 for NetWare:

to the location of the NetWare Libraries for C SDK, for example: Set NOVELLLIBC=c:\novell\ndk\libc

, you don't need to set this.LDAPSDK

to the location where you installed the LDAP Libraries for C, for example: Set LDAPSDK=c:\Novell\NDK\cldapsdk\NetWare\libc

to the location where you installed the source code for the ZLib Library, for example: Set ZLIBSDK=D:\NOVELL\zlib

to the location where you installed the source code for the PCRE Library, for example: Set PCRESDK=D:\NOVELL\pcre

source code directory. Typically \httpd\srclib\apr

but the APR project can be outside of the httpd directory structure. Set APR_WORK=D:\apr-1.x.x

to the full path of the apr-util

) have been included in the system's PATH

and build the prebuild utilities by running "gmake -f nwgnumakefile prebuild

". This target will create the directory \httpd-2.0\nwprebuild

and copy each of the utilities to this location that are necessary to complete the following build steps. \httpd-2.0\nwprebuild\GENCHARS.nlm

volume of a NetWare server and run them using the following commands: SYS:\genchars > sys:\test_char.h

SYS:\dftables sys:\chartables.c

Builds release versions of all of the binaries and copies them to a \release

Builds debug versions of all of the binaries and copies them to a \debug

Creates a complete Apache distribution with binaries, docs and additional support files in a \dist\Apache2

directory in the destination directory and copies headers and import files.

Cleans all object files and binaries from the \release.o

build areas depending on whether DEBUG

Same as clean and also deletes the distribution directory if it exists.

to provide SSL services. This module simply enables the native SSL services implemented in NetWare OS to handle all encryption for a given port. Alternatively, modssl can also be used in the same manner as on other platforms.modnw_ssl

Before mod_ssl can be built for the NetWare platform, the OpenSSL libraries must be provided. This can be done through the following steps:

and modify any tools and utilities paths so that they correspond to your build environment. Netware\set_env netware-libc

Netware\build netware-libc nw-nasm enable-mdc2 enable-md5

to the full path to the root of the openssl source code directory, and set WITHMODSSL to 1. Set OSSLSDK=d:\openssl-0.9.8x

Modules | Directives | FAQ | Glossary | Sitemap

Apache HTTP Server Version 2.4