Administer IBM HTTP Server

Learn how to administer and configure IBM HTTP Server, including: Secure Socket Layer (SSL), Key management, Lightweight Directory Access Protocol (LDAP) and System Authorization Facility (SAF) for z/OS® systems

• Perform required z/OS system configurations
  Before starting IBM HTTP Server, there are required z/OS system configurations that you must set up.

• Start and stop IBM HTTP Server
  We can start or stop IBM HTTP Server using the WebSphere® Application Server administrative console or using other methods depending on your platform.

• Configure IBM HTTP Server
  To configure the IBM HTTP Server, edit the httpd.conf configuration file. To successfully configure the server, the name of the configuration file must be retained as httpd.conf.

• Enable IBM HTTP Server for FastCGI applications
  FastCGI applications use TCP or UNIX sockets to communicate with the Web server. This scalable architecture enables applications to run on the same platform as the Web server, or on many machines scattered across an enterprise network.

• Manage IBM HTTP Server remotely with the WebSphere Application Server administrative console
  We can remotely administer and configure IBM HTTP Server using the WebSphere Application Server administrative console.

• Extending IBM HTTP Server functionality with third-party plug-in modules
  This section contains topics on using third-party plug-in modules with IBM HTTP Server.

• Configure IBM HTTP Server for SMF recording
  System Management Facilities (SMF) record 103 subtype 13 and 14 records are written by the IBM HTTP Server. The record 103.13 contains operational statistics, while the record 103.14 contains request and response information.

• Classify HTTP requests for WLM (z/OS operating systems)
  Classify HTTP requests for workload management (WLM) by first enabling WLM support in IBM HTTP server. Then, map HTTP requests to one or more WLM transaction classes.