| United States-English |
|
|
|
![]() |
Communicator 3000 MPE/iX Release 6.5 (Non-Platform Software Release C.65.00): HP 3000 MPE/iX Computer Systems > Chapter 5 Internet and InteroperabilityApache for MPE/iX 6.5 |
|
by Barbara Dubbert Apache for MPE/iX is server software which turns your HP 3000 into a full-featured web server. With the Apache web server, HP 3000 users can now do business over the Internet. As a web server, your HP 3000 can provide users with direct access to documents and applications residing on your system. These applications can include both internet and intranet dynamic database connectivity using a browser as a common, easily-maintained interface. The client browser can be any one of a variety of browsers including those from Microsoft and Netscape. The Apache Web Server is currently the most popular web server on the market with over 50% of the web server market share. Apache on the HP 3000 joins a growing number of computer platforms which support Apache including HP-UX and other UNIX derivatives, Linux, Win32 and various other server and desktop platforms. Apache for MPE/iX supports a rich set of features including:
For details on installing and using Apache for MPE/iX, refer to the Technical Overview section. As a web server, your HP 3000 can provide users with direct access to documents and applications residing on your system. Users make requests to the web server via a client browser using the Hypertext Transfer Protocol (HTTP). The sole purpose of a web server is to translate a request (URL) into either a filename, and then send that file back over the network, or into a program name, and then run that program and send its output back.Once you start the executable, HTTPD, Apache runs silently in the background, waiting for a client's request to arrive on a port to which it is listening. Apache listens on the port specified in its configuration file. When a request arrives, Apache hands the request to one of its child processes to service and returns to listen again on the port. The major components for Apache are the web server program (HTTPD), the job stream file which runs the HTTPD program (JHTTPD), a set of configuration files for enabling Apache features, the htdocs directory containing HTML pages, the logs directory, and the cgi-bin directory. Apache also comes with a full, on-line manual set.
To start the Apache web server:
Before your HP 3000 can act as a web server, it must be available for network access via TCP/IP. In preparation, you should:
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. 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. 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.
We strongly recommend setting KeepAlive to off in http.conf. With KeepAlive on, sockets may eventually be used up. When this happens, Apache will appear to be hung and will need to be restarted. The JHTTPD Job Stream File is used to run the HTTPD web server program in standalone mode with your local timezone:
The timezone variable, TZ, should be set to your local timezone (for example, EST5EDT for Eastern Daylight Time, PST8PDT for Pacific Daylight Time, and MST7MDT for Mountain Daylight Time). For more information about setting the timezone value, enter "man timezone" in the POSIX shell to read the POSIX help file. To preserve the access permissions (ACD) on the JHTTPD file, you can edit the file using the secure feature of EDITOR:
The HTTPD web server program is started using the JHTTPD job file. Apache can be started from either the CI or the POSIX shell:
There are a number of ways to verify if the Apache web server is running or, if it is not, to isolate how far the startup process progressed. After streaming the JHTTPD file, use :SHOWJOB to view the running job:
Another method is to check server status using either ps from the POSIX shell or using :SHOWPROC at the CI. The parent process is the HTTPD process with the -f option. :SHOWPROC; job=jhttpd,www.apache shell> ps -ef | grep HTTPD
If the HTTPD program is running, make sure you can also access files in the directory tree. Some pages to try are:
If you are unsuccessful in starting the HTTPD program, you can get more information about the problem by:1. Looking at the output of the JHTTPD spoolfile2. Checking the messages in the /APACHE/PUB/logs/error_log file 3. Trying to telnet to Apache's port (port 80 if you have not modified the port directive set in the httpd.conf.sample file)If you cannot telnet to Apache's port, then your problem is not with the web server. You are not yet reaching your HP 3000 box. A successful telnet connection should look something like,
Apache is stopped by aborting the Apache job from either the CI or the POSIX shell. Use SHOWJOB to view the Apache job:
Apache can also be stopped using :ABORTJOB from the POSIX shell
Apache error logging is useful when trying to start Apache as well as for monitoring a running web server. Apache logs errors into a log file called the error_log by default. This log file resides in the /APACHE/PUB/logs directory. The number of messages logged in the error log is set by the LogLevel directive in the httpd.conf file. Possible values for LogLevel (by increasing significance) are debug, info, notice, warn, error, crit, alert, emerg. When a particular level is specified, messages from all other levels of higher significance are reported as well. For example, when LogLevel is "info", then messages with log levels of notice, warn, and up to emerg are also posted. By default, the level is set to warn. Using a level of at least crit is recommended. The current version of Apache for MPE/iX is based on Apache 1.3.4 from the Apache Software Foundation. In addition to the http core that is the heart of the Apache code, 28 more Apache modules have been compiled into the web server program for a large feature set. A full description of each of these modules is included in the on-line manual document pages.
Much of the public information available on Apache can be used for administrating Apache on MPE/iX. This especially applies to the description and usage of the over 128 different Apache configuration directives. Sources for additional information include,
For downloadable software to enhance your web site (perl, sendmail, python, etc.), visit MPE's external Jazz web server at http://jazz.external.hp.com |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||