Siebel Installation Guide for UNIX > Additional Postinstallation and Configuration Tasks > Additional Tasks for the Siebel Web Server Extension and the Web Server >
Configuring the Web Server
This topic describes steps for configuring the Web server for use with the SWSE. Some other documented postinstallation tasks also involve Web server configuration.
Additional Web server configuration tasks are described in Installing the Web Server.
For version information for supported Web servers and the operating systems they run on (where you also install SWSE), see the Certifications application on My Oracle Support.
For Apache-based Web servers, to configure the Web server for use with the SWSE, you must edit the Web server configuration file httpd.conf. For more information about the location of this file, see Installing the Web Server.
This topic is part of Additional Tasks for the Siebel Web Server Extension and the Web Server.
Use the following guidelines for setting parameters in the httpd.conf file when using Apache-based Web servers with Siebel Business Applications.
Requirements for an Apache-Based Web Server
Use the following settings for configuring your Web server. Some adjustments to these values may be needed, as outlined in article 871352.1 (Article ID) on My Oracle Support.
- Make sure that your section
<worker.c> looks like the following:
In this example, N is two times the average number of concurrent users.
- The User and Group values must correspond to an existing user who has appropriate permissions. Most importantly, the user must have appropriate permissions for various SWSE directories.
Recommendations for an Apache-Based Web Server
The following are recommended settings for configuring your Web server:
- Set UseCanonicalName to OFF. You are required to set UseCanonicalName to OFF if you load-balance Web servers.
- Set KeepAliveTimeout to 15 seconds.
- Set MaxKeepAliveRequests to 0 for maximum performance.
Optional Settings for an Apache-Based Web Server
Optionally, you can add comment characters and disable the line that loads the CGI module, if you are not using the CGI functionality of your Apache-based Web server. Doing this makes tracking Web server processes simpler because there is always one child process.