This document outlines the steps needed to install Apache onto an IBM z/TPF Enterprise Edition V1 R1 system. (There are separate installation instructions for TPF4.1.)
You should first review readme-tpf.html for basic information on the port of Apache to TPF including a list of supported modules.
The allocated CHTA program name is used throughout
these instructions to refer to Apache. You can use a different
program name if you wish.
Likewise the directory structure opensource/apache/src is used for the Apache source code directory. You can use different directories than opensource/apache if you wish.
If you change the program or directory names be sure to change the entries shown in these instructions, all MakeTPF-related files, and the sample files accordingly.
Releases of the Apache server are compressed into a "tarball" file which must be downloaded to your PC. Additionally the source code from the tarball will need to be copied onto your Linux build system for compiling. Here are all the details on how to get Apache and how to get it where it needs to be:
Download the compressed Apache 1.3 files (the "tarball") from http://httpd.apache.org/download.cgi to your PC. The file name on the web site will be apache_1.3.vv.tar.Z, where "vv" is the version number. Replaced "vv" throughout these instructions with the actual version number.
TIP: Be sure to keep the .tar.Z extension when saving the file.
Decompress the tarball on your PC using WinZip or some other PC decompression tool.
TIP: If you are using WinZip verify that the "TAR File Smart CR/LF Conversion" option (under Options, Configuration) is not checked.
This is what you can expect if you use WinZip:
FTP the tarball to your Linux build machine using binary mode:
TIP: Linux file names are case sensitive.
On your Linux build machine, decompress and extract the archived files necessary for compiling Apache:
tar -xzkf apache_1.3.vv.tar.Z "*/src"
Note that the following "src" subdirectories are not used for Apache on z/TPF and may be removed if desired:
lib/expat-lite, lib/sdbm, regex, and all os subdirectories except for os/tpf.
Create header files that are automatically generated for other platforms but are not for z/TPF:
cp apache_1.3.vv/src/os/tpf/samples/uri_delims.txt apache_1.3.vv/src/main/uri_delims.h
Move the source code into your desired directory
structure for MakeTPF with the following entries.
Replace "foobar" below with your actual directory name:
mkdir -p $AROOT
mv apache_1.3.vv/* $AROOT
CHTA is already in the tpf_app_base.cntl control file. Adjust any settings if necessary.
Create an environment file for Apache named
$AROOT/src/os/tpf/samples/sample_env.txt as a
Place maketpf.env_apache in the same directory as your other environment files.
Create a .mak file for Apache named
$AROOT/src/os/tpf/samples/sample_mak.txt as a
Verify that the maketpf_env assignments in chta.mak are correct for your build environment.
Create a configuration file named
Ensure that the first assignment of TPF_ROOT in maketpf.cfg is the absolute path to your "foobar" directory.
Later if you want to include Apache in your full build
add APACHE=YES to the CONFIG macro in
your Stage 1 deck.
Then reassemble the SIP deck (sip.asm) to update the SIP generated build files with the APACHE function switch enabled.
Switch to the Apache source code subdirectory:
Overlay src/Configuration with src/Configuration.tmpl:
cp Configuration.tmpl Configuration
The src/Configuration file controls which optional
modules are compiled into Apache.
Leave the file as-is if you want to use the default set of modules.
Otherwise edit the src/Configuration file to customize which modules are used:
If you would like to use the TCP/IP network services database add "CFLAGS_CHTA += -DTPF_HAVE_NSD" to either src/chta.mak or src/maketpf.cfg. See "Network Services Database Support" in the IBM TPF Product Information Center for details.
Run the "Configure" script:
export TPF=YES; export
Using config file: Configuration Creating Makefile + configured for TPF platform + setting C compiler to c89 + setting C pre-processor to /usr/bin/cpp + using "tr [a-z] [A-Z]" to uppercase + checking for system header files + adding selected modules + checking sizeof various data types Creating Makefile in support Creating Makefile in os/tpf Creating Makefile in ap Creating Makefile in main Creating Makefile in modules/standard $
This generates modules.c and the apache.modules text
file for use later by MakeTPF.
(Other files created by Configure are not used on z/TPF such as include/ap_config_auto.h and the various Makefiles, so don't be concerned that the C compiler and pre-processor shown in the Configure output are incorrect.)
Use the -file option if you want to maintain multiple configurations:
./Configure -file Configuration.2nd
Using config file: Configuration.2nd Creating Makefile + configured for TPF platform + setting C compiler to c89 et cetera
Edit src/os/tpf/os.h if you do not want the scoreboard kept in shared memory.
The default behavior for Apache on all platforms except TPF is to use the file system for maintaining the scoreboard (which holds current Apache children status). The default behavior for Apache on TPF is to use shared memory. This reduces file activity and improves performance.
If for some reason you do not want to use shared memory for the scoreboard, you must remove "#define USE_SHMGET_SCOREBOARD" from the os.h. The change will only take effect after Apache is (re)compiled.
Compile and link Apache:
maketpf chta -f
Apache uses cinet6 from CLTY, which is part of the
Internet Daemon (ZINET). Ensure that you link Apache
with the proper version of CLTY for your system. If you
apply changes to CLTY you should re-link Apache to
inetd_getServerStatus functions from
Load and activate Apache on your test system.
Ensure that the program name you are using for Apache has RESTRICT and KEY0 authorization:
If necessary you can use the zapat entry to alter the authorization:
zapat chta restrict key0
General documentation for Apache is located at http://httpd.apache.org/docs/ and in the HTML pages included with the distribution (tarball) under the htdocs/manual directory.
Create the Apache run-time configuration file. The
server requires a configuration file to initialize
itself during activation.
Copy the distribution version, conf/httpd.conf-dist from the decompressed tarball on your PC, to conf/httpd.conf and then edit the conf/httpd.conf copy with your site specific information.
You must change every occurrence of "@@ServerRoot@@" to your document server root (for example "/usr/local/apache")
You should also add the following line to the httpd.conf file to prevent Apache from doing a host name lookup on your test system:
Be sure your Native Stack communications device is
active on TPF.
Refer to the IBM TPF Product Information Center for details.
Using either TFTP or FTP, transfer the configuration file, icons, and web pages to your TPF system. A typical directory structure for Apache is as follows:
At a minimum you will need these files on TPF:
All gif, jpg, and zip files should be transferred as binary; the configuration file and html pages should be transferred as text.
Refer to the IBM TPF Product Information Center for details on TFTP and FTP.
The logs directory must exist and be accessible in order to avoid an fopen error while running Apache:
zfile chmod 777 /usr/local/apache/logs
Add Apache to the Internet Daemon's tables using ZINET entries:
zinet add s-apache pgm-chta model-daemon user-root
Refer to the IBM TPF Product Information Center for details on the Internet Daemon and ZINET commands.
Start the server:
zinet start s-apache
Verify Apache was successfully started:
zfile cat /usr/local/apache/logs/error_log
The output should be similar to this:
[timestamp] [notice] Apache/1.3.vv (TPF) configured -- resuming normal operations [timestamp] [notice] Accept mutex: tpfcore (Default: tpfcore)
If there are severe errors correct the conf file and restart the server:
zinet stop s-apache
correct the httpd.conf file and transfer it to TPF
zfile rm /usr/local/apache/logs/error_log
zinet start s-apache
Request a page from your browser:
http://xx.xx.xx.xx (where xx.xx.xx.xx is your test system IP address)