Web Server Tuning

8. Web Server Tuning

You can use these settings to optimize web servers, such as Apache Server or IBM HTTP Server (IHS), for TRIRIGA®.

While the following settings provide optimal performance in IBM test environments, your environment typically requires different settings. You can use these settings as a guideline or as a starting point, and then customize the settings to your specific environment requirements. For more information on how to tune web servers, see your web server documentation.

The following options and values can be configured by editing the httpd.conf configuration file:

  1. Enable the MPM module.
  2. Apply these starting values for your testing.
    The following parameters are provided for a server configuration of 32 CPU and 240 GB RAM and you must calculate your own values based on your server configuration.
    Note: Values that are based on incorrect calculations can lead to memory leakages.
    <IfModule mpm_event_module>
    StartServers                4   
    MinSpareThreads             25
    MaxSpareThreads             75
    ThreadLimit                 64
    ThreadsPerChild             64
    MaxRequestWorkers           128
    MaxConnectionsPerChild      100             
</IfModule>
  3. Set the following KeepAlive timeouts:
    • KeepAlive On
    • KeepAliveTimeout 5
    • MaxKeepAliveRequests 100
    • Timeout 600
    • Proxy timeout 1800
Note: Proxy server configuration is beyond the scope of TRIRIGA documentation.

Enabling CORS on a web server

If you are using multiple domains in your environment, ensure that you configure your web server for Cross-Origin Resource Sharing (CORS).

For example, on web servers such as Apache Server or IBM HTTP Server (IHS), set the following headers in your /etc/httpd/conf.d/virtual.conf file:

Access-Control-Allow-Origin: <TRIRIGA server domain name>
Access-Control-Allow-Credentials: true