0N/A<!
DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" 0N/A <
meta name="generator" content="Microsoft FrontPage 4.0" />
0N/A <
title>Using Apache with Novell NetWare</
title>
0N/A <!-- Background white, links blue (unvisited), navy (visited), red (active) --> 0N/A <
body bgcolor="#FFFFFF" text="#000000" link="#0000FF" 0N/A vlink="#000080" alink="#FF0000">
0N/A <
h1 align="center">Using Apache With Novell NetWare</
h1>
0N/A <
p>This document explains how to install, configure and run
0N/A Apache 2.0 under Novell NetWare
6.x and above. If you find any bugs,
0N/A or wish to contribute in other ways, please
0N/A <
p>The bug reporting page and dev-httpd mailing list are <
em>not</
em>
0N/A provided to answer questions about configuration or running Apache.
0N/A Before you submit a bug report or request, first consult this document, the
0N/A relevant documentation topics. If you still have a question or problem,
0N/A Apache users are more than willing to answer new
4378N/A and obscure questions about using Apache on NetWare.</
p>
4378N/A Most of this document assumes that you are installing Apache
4378N/A from a binary distribution. If you want to compile Apache
4378N/A yourself (possibly to help with development, or to track down
4378N/A bugs), see the section on <
a href="#comp">Compiling Apache for
0N/A <
li><
a href="#req">Requirements</
a></
li>
0N/A <
li><
a href="#down">Downloading Apache for NetWare</
a></
li>
0N/A <
li><
a href="#inst">Installing Apache for NetWare</
a></
li>
0N/A <
li><
a href="#run">Running Apache for NetWare</
a></
li>
0N/A <
li><
a href="#use">Configuring Apache for NetWare</
a></
li>
0N/A <
li><
a href="#comp">Compiling Apache for NetWare</
a></
li>
0N/A <
h2><
a id="req" name="req">Requirements</
a></
h2>
0N/A Apache 2.0 is designed to run on NetWare 6 and above.
0N/A <
p><
strong>You must install Service
0N/A Pack 1 or above.</
strong></
p>
0N/A <
p>NetWare service packs are available <
a 0N/A <
h2><
a id="down" name="down">Downloading Apache for NetWare</
a></
h2>
0N/A <
p>Information on the latest version of Apache can be found on
0N/A the Apache web server at <
a 0N/A will list the current release, any more recent alpha or
0N/A beta-test releases, together with details of mirror web and
0N/A anonymous ftp sites.</
p>
0N/A <
h2><
a id="inst" name="inst">Installing Apache for
0N/A There is no Apache install program for NetWare currently. You
0N/A will need to compile apache and copy the files over to the
0N/A server manually. An install program will be posted at a later
0N/A <
p>Follow these steps to install Apache on NetWare from the
0N/A binary download (assuming you will install to sys:/apache2):</
p>
0N/A <
li>Unzip the binary download file to the root of the SYS:
0N/A volume (may be installed to any volume)</
li>
0N/A ServerName to reflect your correct server settings</
li>
0N/A <
li>Add SYS:/APACHE2 to the search path. EXAMPLE: SEARCH ADD
0N/A <
p>Follow these steps to install Apache on NetWare manually
0N/A from your own build source (assuming you will install to
0N/A <
li>Create a directory called <
code>Apache2</
code> on a
0N/A <
li>Create a directory under SYS:/APACHE2 called CONF</
li>
0N/A <
li>Copy all files and subdirectories in \HTTPD-2.0\DOCS\ICONS to
0N/A <
li>Copy all files and subdirectories in \HTTPD-2.0\DOCS\MANUAL to
0N/A <
li>Copy all files and subdirectories in \HTTPD-2.0\DOCS\ERROR to
0N/A <
li>Copy all files and subdirectories in \HTTPD-2.0\DOCS\DOCROOT to
0N/A modules into the modules directory</
li>
0N/A <
li>Edit the
HTTPD.CONF file searching for all @@<
i>Value</
i>@@ markers
0N/A and replacing them with the appropriate setting</
li>
0N/A <
li>Add SYS:/APACHE2 to the search path. EXAMPLE: SEARCH ADD
0N/A <
p>Apache may be installed to other volumes besides the default <
samp>SYS</
samp> volume.</
p>
0N/A <
h2><
a id="run" name="run">Running Apache for NetWare</
a></
h2>
0N/A To start Apache just type <
strong>apache</
strong> at the
0N/A console. This will load apache in the OS address space. If you
0N/A prefer to load Apache in a protected address space you may
0N/A specify the address space with the load statement as follows:
0N/A load address space = apache2 apache2
0N/A <
p>This will load Apache into an address space called apache.
0N/A Running multiple instances of Apache concurrently on NetWare is
0N/A possible by loading each instance into its own protected
0N/A <
p>After starting Apache, it will be listening to port 80
0N/A (unless you changed the <
samp>Listen</
samp> directive in the configuration
0N/A files). To connect to the server and access the default page,
0N/A launch a browser and enter the server's name or address. This
0N/A should respond with a welcome page, and a link to the Apache
0N/A manual. If nothing happens or you get an error, look in the
0N/A <
samp>error_log</
samp> file in the <
samp>logs</
samp>
0N/A <
p>Once your basic installation is working, you should
0N/A configure it properly by editing the files in the
0N/A <
samp>conf</
samp> directory.</
p>
0N/A <
p>To unload Apache running in the OS address space just type
0N/A the following at the console:</
p>
0N/A unload apache2</
pre>
0N/A<
pre> apache2 shutdown
0N/A If apache is running in a protected address space specify the
0N/A address space in the unload statement:
0N/A unload address space = apache2 apache2
0N/A <
p>When working with Apache it is important to know how it will
0N/A find the configuration files. You can specify a configuration
0N/A file on the command line in two ways:</
p>
0N/A <
li>-f specifies a path to a particular configuration
0N/A In these cases, the proper ServerRoot should be set in the
0N/A <
p>If you don't specify a configuration file name with -f,
0N/A Apache will use the file name compiled into the server, usually
0N/A display this value labeled as SERVER_CONFIG_FILE. Apache will
0N/A then determine its ServerRoot by trying the following, in this
0N/A <
li>A ServerRoot directive via a -C switch.</
li>
0N/A <
li>The -d switch on the command line.</
li>
0N/A <
li>Current working directory</
li>
0N/A <
li>The server root compiled into the server.</
li>
0N/A <
p>The server root compiled into the server is usually "sys:/apache2". invoking apache with the -V switch will display
0N/A this value labeled as HTTPD_ROOT.</
p>
0N/A <
p>Apache 2.0 for NetWare includes a set of command line directives that can
0N/A be used to modify or display information about the running instance of the
0N/A web server. Each of these directives must be preceded by the keyword
0N/A <
li>RESTART - Instructs Apache to terminate all running worker threads as
0N/A they become idle, reread the configuration file and restart each worker
0N/A thread based on the new configuration.</
li>
0N/A <
li>VERSION - Displays version information about the currently running
0N/A instance of Apache.</
li>
0N/A <
li>MODULES - Displays a list of loaded modules both built-in and
0N/A <
li>DIRECTIVES - Displays a list of all available directives.</
li>
0N/A <
li>SETTINGS - Enables or disables the thread status display on the
0N/A console. When enabled, a status of the number of running threads
0N/A is displayed along with their status.</
li>
0N/A <
li>SHUTDOWN - Terminates the running instance of the Apache web server.</
li>
0N/A <
h2><
a id="use" name="use">Configuring Apache for
0N/A Apache is configured by files in the <
samp>conf</
samp>
0N/A directory. These are the same as files used to configure the
0N/A Unix version, but there are a few different directives for
0N/A Apache on NetWare. See the <
a href="./">Apache
0N/A documentation</
a> for all the available directives.
0N/A <
p>The main differences in Apache for NetWare are:</
p>
0N/A <
p>Because Apache for NetWare is multithreaded, it does not
0N/A use a separate process for each request, as Apache does in some Unix
0N/A implementations. Instead there are only threads running: a parent
0N/A thread, and a multiple child threads which handle the requests. So the "process"-management directives are
0N/A - Like the Unix directive, this controls how many requests
0N/A a worker thread will serve before exiting. The recommended default, <
code>MaxRequestsPerChild
0N/A 0</
code>, causes the thread to continue servicing request indefinitely.
0N/A It is recommended on NetWare, unless there is some specific reason, that
0N/A this directive always remain set to 0. </
p>
0N/A This directive tells the server how many
0N/A threads it should start initially. The recommended default is <
code>StartThreads
0N/A This directive instructs the server to spawn additional worker threads
0N/A if the number of idle threads ever falls below this value. The recommended default is
0N/A <
code>MinSpareThreads 10</
code>.</
p>
0N/A This directive instructs the server to begin terminating worker threads
0N/A if the number of idle threads ever exceeds this value. The recommended default is
0N/A <
code>MaxSpareThreads 100</
code>.</
p>
0N/A This directive limits the total number of work threads to a maximum
0N/A value. The recommended default is <
code>ThreadsPerChild 250</
code>.</
p>
0N/A - This directive tells the server what size of stack to use
0N/A for the individual worker thread. The recommended default is
0N/A <
code>ThreadStackSize 65536</
code>.</
p>
0N/A <
p>The directives that accept filenames as arguments now
0N/A must use NetWare filenames instead of Unix ones. However,
0N/A because Apache uses Unix-style names internally, you must
0N/A use forward slashes, not backslashes. It is recommended that all rooted
0N/A file paths begin with a volume name. If omitted, Apache will
0N/A assume the SYS: volume.</
p>
0N/A <
p>Apache for NetWare has the ability to load modules at
0N/A runtime, without recompiling the server. If Apache is
0N/A compiled normally, it will install a number of optional
0N/A modules in the <
code>\Apache2\modules</
code> directory. To
0N/A activate these, or other modules, the <
a 0N/A must be used. For example, to active the status module, use
0N/A the following (in addition to the status-activating
0N/A <
p>Information on <
a 0N/A modules</
a> is also available.</
p>
0N/A Additional NetWare specific directives:</
u></
b></
p>
0N/A - This directive maps a CGI file extension to a script interpreter.</
li>
0N/A <
h2><
a id="comp" name="comp">Compiling Apache for
0N/A <
p>Compiling Apache requires MetroWerks CodeWarrior
6.x or
0N/A higher to be properly installed. Once Apache has been built, it needs to be installed on a NetWare
0N/A volume's root directory. The default is the
0N/A <
code>sys:/Apache2</
code> directory.</
p>
0N/A <
p>Before running the server you must fill out the conf
0N/A and replacing them with the appropriate setting. Copy over
Requirements: </
u></
b></
p>
The following development tools are required to build Apache 2.0
Developer Components for NetWare</
a></
li>
<
li>To build using either the project file or the make files, requires an AWK utility (awk, gawk or
utility must be found in your windows path and must be named
awk.exe. </
li>
<
li>To build using the makefiles, you will need GNU make version 3.78.1 (GMake)
<
p><
b><
u>Building Apache using the Metrowerks Project Files: </
u></
b></
p>
<
p>All major pieces of Apache and APR are built using the
status, info, proxy, etc.</
p>
<
li>Set the environment variable "NovellLibC" to the
location of the NetWare Libraries for C SDK (ex. Set NovellLibC=c:\novell\ndk\libc).</
li>
<
li>Make sure that the path to the CodeWarrior command line tools (
MWCCNLM.exe,
MWLDNLM.exe) has been included in the system's PATH environment
<
li>Make sure that the path to the AWK utility has been included in the
system's PATH environment variable.</
li>
<
li>Download the source code and unzip to an appropriate directory on
your workstation. </
li>
<
li>Change directory to \httpd\srclib\apr\build and run the batch file
for building the APR libraries. It will also run 2 AWK scripts
that will generate the export files for APR.</
li>
<
li>Change directory to \httpd\srclib\apr and extract the project file
<
li>Open the
LIBAPRNW.mcp project file in the Metrowerks IDE.</
li>
<
li>Select the target "Build Util - Gen URL Delim" and build the target.
This target will produce the NLM "
GENURI.nlm" </
li>
<
li>Copy the file
GENURI.nlm to the SYS: volume of a NetWare server and
run using the following command:
<
li>Copy the file "
uri_delims.h" to the directory \httpd\srclib\apr-util\uri
on the build machine. </
li>
<
li>Select the target "APR Debug NLM" or "APR Release NLM" in the IDE and build. This will
<
li><
i>OPTIONAL</
i>: Select any of the LIB targets to produce a
statically linkable libraries. </
li>
<
li>Change directory to \httpd\build and run the batch file
prebuildnw.bat. This batch file will setup the build environment for building the
APACHE.nlm. It will also run several AWK scripts that will
generate the export files for APACHE. </
li>
<
li>Change directory to \http and extract the project file
ApacheNW.mcp <
li>Open the
ApacheNW.mcp project file in the Metrowerks IDE. </
li>
<
li>Select the target "Build Utility - DFTables" and build the target. </
li>
<
li>Select the target "Build Util - Gen Test Chars" and build the target. </
li>
volume of a NetWare server and run using the following commands:
\httpd\os\netware on the build machine. </
li>
<
li>Select the target "Apache Full Debug" or "Apache Full
Release" in the IDE and build. This will
produce the file
APACHE2.nlm along with all of the external module NLMs. </
li>
<
p><
b><
u>Building Apache using the NetWare makefiles: </
u></
b></
p>
<
li>Set the environment variable "NOVELLLIBC" to the
location of the NetWare Libraries for C SDK (ex. Set NOVELLLIBC=c:\novell\ndk\libc).</
li>
<
li>Set the environment variable "METROWERKS" to the
location where you installed the Metrowerks CodeWarrior compiler (ex. Set
METROWERKS=C:\Program Files\Metrowerks\CodeWarrior). If you
installed to the default location C:\Program
Files\Metrowerks\CodeWarrior, you don't need to set this.</
li>
<
li>Set the environment variable "AP_WORK" to the full path of
the \httpd directory.</
li>
<
li>Set the environment variable "APR_WORK" to the full path of
the \httpd\srclib\apr directory.</
li>
<
li>Make sure that the path to the AWK utility and the GNU make utility (
gmake.exe)
have been included in the
system's PATH environment variable.</
li>
<
li>Download the source code and unzip to an appropriate directory on
<
li>Change directory to \httpd\srclib\apr-util\uri and build
GENURI.nlm by
running "gmake -f nwgnumakefile"</
li>
<
li>Copy the file
GENURI.nlm to the SYS: volume of a NetWare server and
run using the following command:
<
li>Copy the file "
uri_delims.h" to the directory \httpd\srclib\apr-util\uri
on the build machine. </
li>
<
li>Change directory to \httpd\srclib\apr and build APR by running "gmake
-f nwgnumakefile"</
li>
<
li>Change directory to \httpd\srclib\pcre and build
DFTABLES.nlm by
running "gmake -f nwgnumakefile" </
li>
<
li>Change directory to \httpd\server and build
GENCHARS.nlm by running
"gmake -f nwgnumakefile"</
li>
volume of a NetWare server and run them using the following commands:
\httpd\os\netware on the build machine. </
li>
<
li>Change directory to \httpd and build Apache by running "gmake -f
nwgnumakefile." You can create a distribution directory by
adding an install parameter to the command (ex. gmake -f nwgnumakefile
<
p><
u>Additional make options</
u></
p>
<
li>gmake -f nwgnumakefile - Builds release versions of all of the
binaries and copies them to a \release destination directory.</
li>
<
li>gmake -f nwgnumakefile DEBUG=1 - Builds debug versions of all of the
binaries and copies them to a \debug destination directory.</
li>
<
li>gmake -f nwgnumakefile install - Creates a complete Apache
distribution with binaries, docs and additional support files in a
\dist\Apache2 directory.</
li>
<
li>gmake -f nwgnumakefile installdev - Same as install but also creates a
\lib and \include directory in the destination directory and copies
headers and import files.</
li>
<
li>gmake -f nwgnumakefile clean - Cleans all object files and binaries
from the \release or \debug build areas depending on whether DEBUG has
<
li>gmake -f nwgnumakefile clobber_all - Same as clean and also deletes
the distribution directory if it exists.</
li>