Customizing the IBM HTTP Server - Powered by Apache

In z/OS® V2R1 and earlier versions, the Infoprint Central component of Infoprint Server was designed to work only with the IBM® HTTP Server powered by Domino®. In z/OS V2R2, IBM removed support for the Domino HTTP Server and only the IBM HTTP Server - Powered by Apache, a base element of z/OS V2R2 and later, is supported. You must now use the Apache 31-bit IBM HTTP Server with Infoprint Central.

To display Infoprint Central web pages, you must customize and start the IBM HTTP Server - Powered by Apache.

Guidelines:
  1. Start a separate IBM HTTP Server - Powered by Apache to be used exclusively by Infoprint Central. A separate HTTP server can improve Infoprint Central performance. Also, you can customize the HTTP server for Infoprint Central without affecting other applications that use the HTTP server.
  2. Start an IBM HTTP Server - Powered by Apache on each z/OS system where Infoprint Server is running. The HTTP server can display Infoprint Central web pages only for Infoprint Server running on the same z/OS system as the HTTP server.
  3. Customize the IBM HTTP Server - Powered by Apache to use the Secure Sockets Layer (SSL) protocol to encrypt information that passes between the user's browser and the HTTP server. This customization is required if the use-unencrypted-connection attribute is set to no, the default value. If you do not want to use SSL, set use-unencrypted-connection to yes.
    Warning: IBM does not recommend setting use-unencrypted-connection to yes. Using an unencrypted connection can expose your network communication to nefarious actors. User IDs, passwords, and data are vulnerable to attacks against the browser or during data transmission using network traffic system techniques.
Related information: For complete information about how to install the IBM HTTP Server - Powered by Apache, see . For more information about the HTTP Server - Powered by Apache, see WebSphere Application Server Knowledge Center.
Table 1 summarizes the customization tasks for using the HTTP Server - Powered by Apache with Infoprint Central. Required tasks are necessary for all installations. Optional tasks are required only if the listed condition applies to your installation.
Table 1. Customization tasks for using the HTTP Server - Powered by Apache with Infoprint Central
Task Condition
Configuring the IBM HTTP Server - Powered by Apache Required
Editing the configuration file for the IBM HTTP Server - Powered by Apache (conf/httpd.conf) Required
Customizing the environment variables file for the IBM HTTP Server - Powered by Apache (bin/envvars) Required
Creating a started task to run the IBM HTTP Server - Powered by Apache Required