Customizing the HTTP server

If you plan to use the HTTP server to invoke the gateway, these changes must be made to the HTTP environment and configuration files:

The HTTP environment file, httpd.env, must be updated to include directives that identify the workarea and configuration directories for the gateway. The CGI_ISPWORK directive is used to define the path for the WORKAREA directory used by the gateway. The CGI_ISPCONF directive is used to define the path for the CONFIG directory where the ISPF configuration file ISPF.conf is stored. Shown here are examples of the CGI_ISPWORK and CGI_ISPCONF directives specifying the default paths for the WORKAREA and CONFIG directories:
```
CGI_ISPWORK=/var/ispf
CGI_ISPCONF=/etc/ispf
```
Update the path statement in httpd.env to include /usr/lpp/ispf/bin. If dot(.), the current directory, is already specified then no update is required.

These pass and exec directives must be added into the HTTP configuration file httpd.conf:

Pass             /ISPZIVP.html /usr/lpp/ispf/bin/ISPZIVP.html
Exec            /ISPZINT       /usr/lpp/ispf/bin/ISPZINT
Exec            /ISPZXML       /usr/lpp/ispf/bin/ISPZXML
Exec            /ISPZIVP.cgi   /usr/lpp/ispf/bin/ISPZIVP.cgi

Note: The path specified for these directives must be the path of the directory where the gateway was installed.

If the gateway modules (see Table 1) are not in the LINKLIST, then update the HTTP server STEPLIB DD to include the load library data sets containing these modules.

Note: To use the gateway, the client is required to supply a valid z/OS® user ID and password.

For additional information about configuring IBM® HTTP Web servers, review these IBM manuals:

HTTP Server Planning, Installing and Using, (SC31-8690)
OS/390® e-business Infrastructure: IBM HTTP Server V5.1 for OS/390, (SG24-5603-00)