1. Link the compiled object files into a DLL. Sample link JCL has been included as src/os/tpf/samples/linkhttp.jcl. You will need to modify this JCL:
    
   • Change the IDs, data set names, and libraries for your particular site. 
   • Add/remove mod_xxx.o files so they correspond to the mod_xxx.o lines in your src/Configuration file. 

   
   TIP: Do NOT include gen_test_char.o or gen_uri_delims.o in the link JCL since these files are only used during the make step. 
   
   If you receive an "Unresolved references" error for "XML_ErrorString" you probably need to remove the expat-lite directory and start back at the "Run the Configure script" step
   
   If you receive an "unable to open" error for lib/expat-lite/hashtable.o" you probably need to remove all of the expat-lite .o's from your link JCL
    
   TIP: Apache uses cinet6, which is part of the Internet Daemon (ZINET). Ensure that you link Apache with the proper version of cinet6 for your system. If you apply changes to cinet6 you should re-link Apache to prevent the inetd_getServer and/or inetd_getServerStatus functions from failing.
   
   

2. Create a loadset. Sample loadset JCL has been included as src/os/tpf/samples/loadset.jcl. You will need to modify this JCL for your particular site.
   
   A JCL condition code of 4 is expected since the C load module will contain no link map data.
   If you require a link map refer to the instructions below on creating one with VisualAge TPF.
    
3. Load (ZOLDR LOAD) and activate (ZOLDR ACT) the loadset on your test system.
    
4. Ensure that the program name you are using for Apache has RESTRICT and KEY0 authorization. zdpat chta  (c-c) will display allocation information. You can use zapat chta restrict key0  (c-c) to alter the authorization. Note that if the program name is unallocated, you must have the loadset for it activated or you will receive INVALID PROGRAM NAME from the zdpat/zapat entries.
    
5. Create the Apache run-time configuration file. The server requires a configuration file to initialize itself during activation. (Previously three configuration files were used.) Copy the distribution version, /conf/httpd.conf-dist, to /conf/httpd.conf and then edit the /conf/httpd.conf copy with your site specific information. 

   At a minimum you must change every occurrence of "@@ServerRoot@@" to your document server root (for example "/usr/local/apache")

6. 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.   

7. On TPF activate your TCP/IP Offload (ZCLAW) or Native Stack communications device.

   Refer to the TPF TCP/IP publication for more information: http://www.ibm.com/tpf/pubs/tpfpubs.htm.

8. 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:

        /usr/local/apache/conf
        /usr/local/apache/logs
        /usr/local/apache/icons
        /usr/local/apache/htdocs
   

   All gif, jpg, and zip files should be transferred as binary; the configuration file and html pages should be transferred as text. 
   
   The logs directory must exist in order to avoid an fopen error while running Apache:
   
   If you're running a PUT10 or higher version of TPF make the directory using the zfile mkdir /usr/local/apache/logs command.
   
   If you're running TPF version PUT09 TFTP an empty file into the logs subdirectory to create it. 
   
   Make sure Apache can write into the logs subdirectory by doing a zfile chmod on it with the appropriate permission settings.

   Refer to the TFTP and FTP sections of the TPF TCP/IP publication for more information: http://www.ibm.com/tpf/pubs/tpfpubs.htm.

9. On TPF add Apache to the Internet Daemon's tables using ZINET entries, the common case:
   
   
   • For PUT11 and later use the DAEMON model for Apache: ZINET ADD S-APACHE PGM-chta MODEL-DAEMON USER-root
   • On pre-PUT11 systems use the NOLISTEN model instead: ZINET ADD S-APACHE PGM-chta MODEL-NOLISTEN

   
   TIP: Logic changes implemented with PUT11 cause ZINET to not restart NOLISTEN servers after ZOLDR ACT and ZOLDR DEACT entries. This means that Apache running as NOLISTEN on a PUT11 or later system will exit whenever any ZOLDR ACT or ZOLDR DEACT entry is made. Therefore at PUT11 you should switch to the DAEMON model and ensure that you have APARs PJ25761 and PJ27363 applied.
   
   Refer to the Internet Daemon section of the TPF TCP/IP publication for more information: http://www.ibm.com/tpf/pubs/tpfpubs.htm.
   
   

10. Start the server using the ZINET START S-APACHE command.
    
    
11. Request a page from your browser: http://xx.xx.xx.xx    (where xx.xx.xx.xx is your IP address)

© 2005 Active-Venture.com Web Page Hosting Service

Disclaimer: This documentation is provided only for the benefits of our hosting customers.
For authoritative source of the documentation, please refer to http://httpd.apache.org/docs/