Home Operating Systems: z/OS

 

Install IHS

This topic describes how to install a running version (server instance) of the IHS for WebSphere Application Server on z/OS using the installer program.

Prior to using the installer program:

• Ensure that your environment meets the prerequisites for the application server. For more information, see the Preparing the base operating system topic.

• Obtain and apply the current version of WebSphere Application Server that provides support of IBM HTTP Server for z/OS systems using SMP/E. The IBM HTTP Server code is installed into the HHAP700 Function Modification Identifier (FMID). The default name is: /usr/lpp/IHSA/V7R0/IBM.

• Mount the file system containing this on the z/OS system where the IHS instance will run.

• Perform the z/OS system configurations that are required for IHS.

• If we are installing the product for the first time, then create a System Authorization Facility (SAF) user ID and group for IBM HTTP Server. For information, see the topic about z/OS system configurations.

  The examples that follow in this topic assume a server user ID of WWWSERV and a server group of WWWGROUP.

• Create an installation for the configuration files for the server instance. For more information, see the topic about migrating and installing IHS on z/OS systems.The examples that follow in this topic assume an installation of /etc/websrv1. Set the permissions to 770 and the ownership to the server user ID and group:

  mkdir  /etc/websrv1 
  chown  WWWSERV:WWWGROUP /etc/websrv1
  chmod 770 /etc/websrv1
  

• The user running the installer must have write access to the selected installation

  The user ID must have a valid OMVS segment, and the user ID must be the same as the user ID that the Web server runs as. (See the z/OS system configuration section referenced in the previous steps.)

• Set the umask value to

  022

  . To verify that the umask value is set to

  022

  , run the umask command.

• If we are installing the product for the first time, then enable the admin console to modify the httpd.conf file by adding the WAS control region user ID to the IHS group using SAF. For example, to add a user ASCR1 to the group WWWGROUP, type the following command:

  CONNECT ASCR1 GROUP (WWWGROUP) OWNER (WWWGROUP)

Using the installer program, perform the following tasks to install a running instance of IBM HTTP Server for z/OS on your machine.

1. Log in to the UNIX System Services shell with the user ID that will run the installer. (See the Before you begin section for this topic.) Change the to the IBM HTTP Server product code directory:

   /usr/lpp/IHSA/V7R0/server

2. Run the installer program to install the product files into the installation directory, perform initial customization, and create symbolic links from the installation to the product directory.

   The installer program is: bin/install_ihs. Three parameters can be used to invoke the installer program.

   • Optional: The -admin keyword, which allows you to use the admin console to modify the httpd.conf file.

   • The installation for the server instance. This must not be the same as the product

   • Optional: The non-SSL port for the Web server. The default port is 80. You can also change the port on the Listen directive.

   The following examples invoke the installer program from the admin console. You can invoke the command with or without support for modifying thehttpd.conf file. For both examples, /etc/websrv1 is the installation directory, and 80 is the non-SSL port for the Web server.

   • This example invokes the command with support for modifying the httpd.conf file.

     bin/install_ihs -admin /etc/websrv1 80

   • This example invokes the command without support for modifying the httpd.conf file.

     bin/install_ihs /etc/websrv1 80

   If wer product path contains symbolic links, you should point the symbolic links to the following default product directory: /usr/lpp/IHSA/V7R0/server. If we do not use the default product directory, invoke the installation script using its absolute path, such as

   /WebSphere/7.0/SMPE/bin/install_ihs

   . If we do not use of the two options, IBM HTTP Server creates physical links, not logical links, when it creates the symbolic links for the installation

3. Optional: This step is optional unless the admin console is configured to start and stop IBM HTTP Server. You can start the IHS instance from the MVS™ console by creating a JCL cataloged procedure for the instance. For more information, see the topic about using JCL procedures to start IBM HTTP Server on z/OS. Verify the JCL procedure is assigned to the user and group you defined for IBM HTTP Server, as described in the topic about performing required z/OS system configurations.

4. Optional: You can create multiple instances of IHS by running the IBM HTTP Server installer program more than once. However, specify a different installation each time you run the installer program.

Perform the following steps to confirm that you have successfully installed a running version of the product on your machine:

1. Log in to the OMVS shell using the server user ID. Verify that the server user ID has a non-zero UID value. Change the to the server instance's installation directory:

   cd /etc/websrv1

2. Run the following commands to verify the installation of the program: apachectl -v and apachectl configtest

   The following sample output is an example of a successful program installation:

   # 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 OK

   The actual version string and build date will vary.

3. Start IHS.

   bin/apachectl start

4. Load the default Web page from the browser to confirm that IBM HTTP Server is operational: Point a Web browser to the IP name or address of your z/OS system, using either the non-SSL port number you specified when running the installer program, or the default port of 80.

5. Stop IHS by running the following command:

   bin/apachectl stop

 

What to do next

• Install and configure the WebSphere Application Server plug-in for IHS

• For information about editing the IBM HTTP Server configuration file, httpd.conf, and information about supported Apache modules, see the topic about configuring IBM HTTP Server.Typical changes that you can make to the configuration file are:

  • Edit the DocumentRoot directive to point to the Web pages for your site.

  • Enable the WAS plug-in for IBM HTTP Server by adding the following directives to the end of httpd.conf:

    LoadModule was_ap22_module  <plugin_config_hfs>/bin/mod_was_ap22_http.so
    WebSpherePluginConfig /path/to/existing/plugin-cfg.xml

    If the plug-in configuration file has been used with a WebSphere Application Server Version 5.0 or 5.1 plug-in, then the file is in EBCDIC. Before using the file with this WAS Version 6.0 or higher plug-in, you need to convert it to ASCII. The following example is for converting the plug-in configuration file from EBCDIC to ASCII:

    $ iconv -f IBM1047 -t ISO8859-1 < /path/to/existing/plugin-cfg.xml \
    > /path/to/ascii/plugin-cfg.xml

  • Enable SSL support by adding the following directives to the end of httpd.conf:

    LoadModule ibm_ssl_module modules/mod_ibm_ssl.so
    Listen 443
    <VirtualHost *:443>
    SSLEnable
    </VirtualHost>
    SSLDisable
    Keyfile /saf saf-keyring-name

    The Keyfile directive can instead specify an HFS filename using the syntax: Keyfile /path/to/keyfile.kdb. The .sth file must be in the same as the .kdb file. For more information, see Securing with SSL communications and SSL directives.

  • Enable mod_status by removing the comment delimiters in the default configuration file which are highlighted below:

    <IfModule mod_status.c>
    ExtendedStatus On
    </IfModule>
    ...
    #<Location /server-status>
    #    SetHandler server-status
    #    Order deny,allow
    #    Deny from all
    #    Allow from .example.com
    #</Location> 

    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.

  • You can install the Web server to an HFS shared R/W by multiple hosts in a sysplex.There are special configuration requirements for components of the Web server which utilize AF_UNIX sockets. AF_UNIX sockets are not supported by an HFS which are shared R/W, so configuration directives are used to place the AF_UNIX sockets on a filesystem 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 on a filesystem owned by the local host.

• Add support for the admin console after the initial installation.

  • Run the bin/enable_admin script to set the permissions needed to modify the httpd.conf file from the admin console.

  • To modify the httpd.conf file from the admin console, add the control region user ID to the IBM HTTP Server group using SAF. For example, to add a user ASCR1 to the group WWWGROUP, type the following command:

    CONNECT ASCR1 GROUP (WWWGROUP) OWNER (WWWGROUP)

  • To use the admin console to start and stop IBM HTTP Server, create a cataloged JCL procedure. For information, see the topic about using JCL procedures to start IBM HTTP Server on z/OS. Verify the JCL procedure is assigned to the user and group you defined for IBM HTTP Server, as described in the topic about performing required z/OS system configurations.

---

 

Subtopics

Running multiple instances of IHS from a single install

 

Related concepts

Using JCL procedures to start IHS on z/OS

 

Related tasks

Performing required z/OS system configurations

Uninstalling IHS

z/OS: Preparing the base z/OS operating system for product installation

Install and configuring the WebSphere Application Server plug-in for IHS on z/OS

 

Related reference

FastCGI directives

SSL directives

Migrating and installing IHS on z/OS systems

Configuring IHS