This topic describes how to install a running version (server instance) of the IBM® HTTP Server for WebSphere® Application Server on z/OS® using the installer program.
The examples that follow in this topic assume a server user ID of WWWSERV and a server group of WWWGROUP.
mkdir /etc/websrv1 chown WWWSERV:WWWGROUP /etc/websrv1 chmod 770 /etc/websrv1
CONNECT ASCR1 GROUP (WWWGROUP) OWNER (WWWGROUP)
Perform the following steps to confirm that you have successfully installed a running version of the product on your machine:
cd /etc/websrv1
# bin/apachectl -v Server version: IBM_HTTP_Server/7.0.0.0 (Unix) Server built: Jan 9 2008 11:20:34 # bin/apachectl configtest Syntax OKThe actual version string and build date will vary.
bin/apachectl start
bin/apachectl stop
LoadModule was_ap22_module <plugin_config_hfs>/bin/mod_was_ap22_http.so WebSpherePluginConfig /path/to/existing/plugin-cfg.xml
$ iconv -f IBM1047 -t ISO8859-1 < /path/to/existing/plugin-cfg.xml \ > /path/to/ascii/plugin-cfg.xml
LoadModule ibm_ssl_module modules/mod_ibm_ssl.so Listen 443 <VirtualHost *:443> SSLEnable </VirtualHost> SSLDisable Keyfile /saf saf-keyring-nameThe Keyfile directive can instead specify an HFS filename using the syntax: Keyfile /path/to/keyfile.kdb. The .sth file must be in the same directory as the .kdb file. For more information, see Securing with SSL communications and SSL directives.
<IfModule mod_status.c> ExtendedStatus On </IfModule> ... #<Location /server-status> # SetHandler server-status # Order deny,allow # Deny from all # Allow from .example.com #</Location>If you want to restrict access to specific networks, uncomment the sample mod_access configuration, but modify the Allow from directive to specify the proper domain or network.
CONNECT ASCR1 GROUP (WWWGROUP) OWNER (WWWGROUP)