Event Management Configuration › How to Configure Event Management GUI Tasks › Configure the Web Server

Configure the Web Server

The Event Management GUI requires a z/OS HTTP server. Any z/OS web server can be used if it provides compatible HTTP, Java, and CGI scripting capabilities. The web server must run on the same host where the Event Management Java server resides.

If you already run a web server on z/OS, you can add the CCS definitions to your existing server. In most cases, however, run a secondary web server that is dedicated to servicing requests for CCS.

When configuring the web server, update or create an HTTPD configuration file. During the Event Management installation, a sample is created in $CAIGLBL0000/browser/httpd.conf, where $CAIGLBL0000 is the path you use to install into. Verify the settings in this file.

The following settings are required:

Exec               /scripts/*
Exec               /tngfw/scripts/*
Exec               /tng/scripts/*
Exec               /ubi/scripts/*
Exec               /ubifw/scripts/*
Pass               /tngfw/*
Pass               /tng/*
Pass               /browser/*
Pass               /UBIImages/*
Pass               /ubiimages/*
Pass               /ubi/*
Pass               /ubifw/*
Pass               /*
Pass               *

See file $CAIGLBL0000/browser/httpd.conf.sample for a complete list of required Exec and Pass parameters.

If you are running a web server that is dedicated to CCS, specify these configuration options:

The Event Management HTML files are shipped in EBCDIC format. Typically, your z/OS web server is configured to process HTML files in EBCDIC format. You have an HTTPD configuration statement similar to:

AddType   .html   text/html   ebcdic   1.0

The Event Management GUI performs user authentication and security validations as sensitive resources are accessed; however, you can also review web server security options. Certain CGI scripts that CCS requires require superuser privileges, and the web server must be configured to run the scripts in the $CAIGLBL0000/browser/scripts using UID 0. Other than this requirement, you are free to deploy any of the security features outlined in your web server documentation, including SSL, SAF, and Certificate-based authentication.

The scripts in $CAIGLBL0000/browser/scripts require certain environmental variables to be set. For best performance, you can define these variables in an LE envvar file, which is used to start the web server. After the Event Management installation, a sample environment variable file can be found in $CAIGLBL0000/browser/httpd.envvars. Review this file and specify it on the PARM= field of the JCL used to start the web server.

The web server can be run as a started task or as a batch job. The CNSMPROC member NSMWEBSV can be used as a model. Set the path statement on the DD card that is associated with the CEE_ENVFILE environment variable to your /cai/nsmem/browser/httpd.envvars file and use your /cai/nsmem/browser/httpd.conf configuration file.