Installing and configuring IBM HTTP Server on the z/OS V2R2 and later systems
You can use the install_ihs
installer program to configure an instance
of IBM® HTTP Server on the z/OS® operating system. Before you begin using IBM HTTP Server, you must
create an instance of the server with the /usr/lpp/ihsa_zos/bin/install_ihs
script
as detailed in the following procedure.
Before you begin
Attention: IBM HTTP Server Version 9 now installs with the base operating system on
z/OS V2R2 and later. No separate installation is required. You do need to create an instance of the
IBM® HTTP Server by using the
/usr/lpp/ihsa_zos/bin/install_ihs
script to the
preinstalled location at /usr/lpp/ihsa_zos
or you can perform a separate
installation using the IBM Installation Manager. For details on a separate installation, refer to
Installing IBM HTTP Server for WebSphere Application Server for z/OS V2R1 and earlier. In either case, before using IBM® HTTP Server
create an instance of the IBM® HTTP Server using the install_ihs
script.
Before you use the installer program, complete the following items:
- Create a System Authorization Facility (SAF) user ID and group for IBM HTTP Server. For more information, see Performing required z/OS system configuration.
The following examples assume a server user ID of WWWSERV and a server group of WWWGROUP.
- Choose a directory to hold the configuration files for the server instance. This directory is
sometimes referred to as the installation directory for the server instance. Because the directory
contains both the configuration and the run-time logs for the server instance, you might want to
create a separate filesystem for it.The examples that follow assume an installation directory of /etc/websrv1. Set the directory permissions to 770, and the directory ownership to the server user ID and group:
mkdir /etc/websrv1 /usr/sbin/mount -f OMVS.SYS1.WEBSRV1.ZFS /etc/websrv1 chown WWWSERV:WWWGROUP /etc/websrv1 chmod 770 /etc/websrv1
About this task
Procedure
Results
Perform the following steps to confirm that you successfully installed a running version of the product on your z/OS operating system:
- Log in to the OMVS shell by using the server user ID.
- Change the directory to the installation directory of the server
instance:
cd /etc/websrv1
- Run the apachectl -v and apachectl configtest commands to
verify the installation of the program.The following sample output is an example of a successful program installation:
The actual version string and build date varies.# bin/apachectl -v Server version: IBM_HTTP_Server/9.0.0.0 (Unix) Server built: Jan 27 2016 12:38:02 # bin/apachectl configtest Syntax OK
- Start IBM HTTP
Server.
bin/apachectl start
- Point a web browser to the IP name or address of your z/OS system by using either the non-SSL port number you specified when you ran the installer
program, or the default port of 80.
If the installation is successful, the IBM HTTP Server default home page displays.
- Stop IBM HTTP Server by running the following
command:
bin/apachectl stop
What to do next
- If you are using IBM HTTP Server with WebSphere Application Server and did not configure the plug-in when you ran the install_ihs installer program, install and configure the WebSphere Application Server plug-in for IBM HTTP Server according to the instructions in the WebSphere Application Server for z/OS IBM Knowledge Center. If IBM HTTP Server is at Fix Pack 9.0.0.9 or later, you can use the WebSphere Application Server plug-in in the /usr/lpp/ihsa_zos/plugin directory instead of installing them separately with IBM Installation Manager.
- Create a JCL cataloged procedure to start the server instance. You must do this step if you are
using the administrative console to start and stop IBM HTTP
Server. For more information, see Using JCL procedures to start IBM HTTP Server on z/OS.Important: The PARM value in a JCL cataloged procedure that is limited to 100 characters. Since the PARM value contains the installation directory (&DIR), the total length might exceed the 100 character limit. Take the path name length into consideration when you choose the installation directory. If the installation directory path name is too long, it is possible to use a shorter named path in the JCL that is symbolically linked to the original installation directory path name.
- Edit the IBM HTTP Server configuration file,
httpd.conf, to meet your organization's needs. For more information about this
file and about supported Apache modules, see Configuring IBM HTTP Server.The following changes are typical ones that you can make to the configuration file:
- Edit the DocumentRoot directive to point to the web pages for your site.
- Enable SSL support by adding the following directives to the end of the
httpd.conf
file:
The Keyfile directive can instead specify an HFS file name by using the syntax ofLoadModule ibm_ssl_module modules/mod_ibm_ssl.so Listen 443 <VirtualHost *:443> SSLEnable </VirtualHost> SSLDisable Keyfile /saf saf-keyring-name
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 Secure Sockets Layer (SSL) directives. - Verify that mod_status module is enabled as shown in the following
example:
If you want to restrict access to a specific IP address, uncomment the sample mod_access Require directive, but modify the IP argument to specify the proper IP address.LoadModule status_module modules/mod_status.so <IfModule mod_status.c> ExtendedStatus On </IfModule> ... <IfModule mod_status.c> <Location /server-status> SetHandler server-status Require all denied # To allow access from a specific IP: # Require ip 192.168.1 </Location> </IfModule>
- You can install the web server to an HFS shared R/W by multiple hosts in a sysplex.Special configuration requirements exist for components of the web server that use AF_UNIX sockets. AF_UNIX sockets are not supported by an HFS that is shared R/W. So, configuration directives are used to place the AF_UNIX sockets on a filesystem that is owned by the host on which the web server runs.
- If mod_ibm_ssl is loaded, use the SSLCachePortFilename directive to specify a file on a filesystem owned by the local host.
- If mod_fastcgi is loaded, use the FastCGIIpcDir directive to specify a directory on a filesystem owned by the local host.
- If you are using IBM HTTP Server with WebSphere Application Server and you specify
-admin when you created the server instance, you can add support for the
administrative console after the initial installation.
- Run the
bin/enable_admin
script to set the permissions needed to modify the httpd.conf file from the administrative console. - Add the control region user ID to the IBM HTTP Server
group by using SAF. See the following
example:
CONNECT ASCR1 GROUP (WWWGROUP) OWNER (WWWGROUP)
- Create a cataloged JCL procedure to start and stop the server. For more information, see Using JCL procedures to start IBM HTTP Server on z/OS.
- Run the