Policy Server Guides › Policy Server Administration Guide › Scaling Your SiteMinder Environment › How to Determine When to Add Policy Servers › Determine the Number of Sockets Opened to a Policy Server › Multi-Process/Single-Threaded Web Server

Multi-Process/Single-Threaded Web Server

A multi-process/single-threaded web server creates multiple, concurrent single-threaded processes to handle client requests. Each thread requires the Web Agent to open a socket to the port on which the Policy Server service is listening.

Note: You configure the maximum number of processes the web server creates in the web server's configuration file. Consider the expected load on the web server when configuring this setting. Refer to your vendor-specific documentation for more information.

The MinSocketsPerPort setting in the HCO is the only applicable socket parameter to a Web Agent installed on a multi-process/single-threaded web server because the web server handles each request with a separate process. A Web Agent never has to handle more than one thread per process. As such, the Web Agent only needs to open one socket on start-up and does not need to open further sockets.

Note: CA recommends changing the MaxSocketsPerPort, MinSocketsPerPort, and NewSocketSetUp default settings to 1 to prevent Web Agents from opening unnecessary sockets. More information on modifying the default HCO settings exist in the Policy Server Configuration Guide.