Communicator e3000 MPE/iX Release 6.5 (Non-Platform Software Release C.65.00 (30216-90291)
140 Chapter5
Internet and Interoperability
Apache for MPE/iX 6.5
Prepare Your HP 3000 for Network Access
Before your HP 3000 can act as a web server, it must be available for network access via
TCP/IP. In preparation, you should:
• Configure TCP/IP on your system
• Have a domain name associated with your system’s IP address
Apache communicates on the network using the HTTP Hypertext Transfer Protocol which,
in turn, uses TCP/IP. Using NMMGR, configure your system’s IP address and subnet mask.
Then run :NETCONTROL START from the CI command line and verify that it ran
successfully.
You will also want to get a domain name. This is a unique identifier such as
“yourserver.com” which is used (instead of the IP address) to direct requests from a
browser to your server. Request a domain name from the administrator of the Domain
Name Server (DNS) on your network.
Configure Apache
Apache reads two global configuration files when it starts: httd.conf and mime.types.
These configuration files determine how Apache behaves. Earlier versions of Apache read
two additional global configuration files: access.conf and srm.conf. These additional
global configuration files can be still be used, but by default they are empty and their
original content is now included in the httpd.conf file.
Edit your Configuration Files
The mime.types file comes as mime.types.default and must be copied or renamed to
mime.types. Similarly the magic.default file must also be copied or renamed. The
httpd.conf file comes in two different versions. The httpd.conf.default file is for a
UNIX-based platform installation. The httpd.conf.sample file was derived from the
httpd.conf.default file with modifications for MPE. This is the file you should edit.
shell> cd /APACHE/PUB/conf
shell> cp mime.types.default mime.types
shell> cp magic.default magic
shell> cp httpd.conf.sample httpd.conf
shell> vi httpd.conf
1. Uncomment and replace “yourserver.com” with your own server’s name for the
ServerAdmin and ServerName directives. Review the Configuration Recommendation
below. You may also choose to make other changes. The Apache Server Project web site,
http://www.apache.org/docs, has information about all of the configuration
directives.
All lines beginning with # are comments and are ignored by the HTTPD program file.
Also note that the content of the configuration files is case sensitive.
Changes to the global configuration files do not take effect until the web server is
started (or stopped and restarted if it is already running).
2. Verify the configuration file. It is a good idea to verify your configuration files before
trying to start the web server. This verification is for syntax checking only.