IBM® Welcome Page V1.1 requires the following production level HTTP server: IBM HTTP Server for i5/OS™ (powered by Apache 2.0, 5722-DG1).
IBM Welcome Page V1.1 provides the ability to set up and manage the configuration needed for an Apache 2.0 HTTP server in support of itself, as well as the IBM Telephone Directory V5.2 application. The application sets up a separate configuration file that contains the required directives for an Apache 2.0 HTTP server. Once complete, the Apache 2.0 HTTP server must be reconfigured to include the additional directives.
The location of the Apache 2.0 configuration file varies depending on the name of your WebSphere® Application Server and what edition is used. The following is an example of the location of the configuration files set up by the IBM Welcome Page V1.1 application when it is deployed:
/QIBM/UserData/WebASE/ASE5/yourserver/ibs/yourserver/apache20.inc
where yourserver is the name of your WebSphere Application Server - Express for iSeries™ V5 server. Once the IBM Welcome Page V1.1 application creates the Apache 2.0 configuration file listed above, the HTTP server must be reconfigured to include the new directives. The following is an example of the directives that are required:
- LoadModule ibm_ldap_module /QSYS.LIB/QHTTPSVR.LIB/QZSRVLDAP.SRVPGM
- Include /QIBM/UserData/WebASE/ASE5/ yourserver/ibs/ yourserver/apache20.inc
where yourserver is the name of your WebSphere Application Server - Express for iSeries V5 server.
The server must be configured to allow the application to benefit from additional functionality provided by the HTTP server.
Once the configuration is set up and the HTTP server is restarted, the plugin module for LDAP is used to authenticate users that route requests to the IBM Telephone Directory V5.2 application. These include requests to create, update, and delete entries in the directory, requests to the IBM Telephone Directory V5.2 application administrative interfaces, and requests to manage identity mappings for Enterprise Identity Mapping (EIM), if configured.
After users are authenticated, their credentials (IDs and passwords) are allowed to pass with the requests routed to the application through the HTTP server plugin for WebSphere and can be used by the application as necessary. Requests that do not require authentication are routed to the application (through the plugin) without credentials.
Other features of the HTTP server can be used to support and protect access to the application. For example, the HTTP server can be configured to require the use of Secure Sockets Layer (SSL) ports to ensure information is sent confidentially. It can be configured to log user activity or to prevent certain users (or systems) from accessing the application.
See the HTTP Server for i5/OS Web page for more details on setting up HTTP servers:
IBM HTTP Server for i5/OS 
(http://www.ibm.com/servers/eserver/iseries/software/http).
See Administer IBM Welcome Page V1.1 for additional information on the entries used to create the apache20.inc file, including name, port, location of users and groups, naming, object classes, and administrator names and groups.