Siebel Installation Guide for UNIX > Installing and Configuring the Siebel Web Server Extension > Postinstallation Tasks for the SWSE and the Web Server >

Configuring the Web Server

This topic is part of Postinstallation Tasks for the SWSE and 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 Siebel System Requirements and Supported Platforms on Oracle Technology Network.

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.

Use the following guidelines for setting parameters in the httpd.conf file when using Apache-based Web servers with Siebel applications.

• Required
  • Make sure your section <worker.c> looks like the following:

  <IfModule worker.c>
  ThreadLimit N
  StartServers 1
  ServerLimit 1
  MaxClients N
  MinSpareThreads 1
  MaxSpareThreads N
  ThreadsPerChild N
  MaxRequestsPerChild 0
  </IfModule>

  where:

  N = 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.
• Recommended
  • 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=0 for maximum performance.
• Optional

  You can comment out the line that loads the CGI module, if you are not using the CGI functionality of your Apache-based Web server. Commenting out the line makes tracking Web server processes simpler because there is always one child process.

  • IBM HTTP Server

  LoadModule cgid_module modules/mod_cgid.so

  • HP Apache Web Server or Oracle HTTP Server

  LoadModule cgi_module modules/mod_cgi.so