On Policy Server running on Linux, configure the /{home_policy_server}/registry/sm.registry file after having stopped the Policy Server. Ensure making a backup of this file before doing modifications.
The values starting with 0x mean hexadecimal.
- Worker Threads:
{home_policy_server}/registry/sm.registry:
HKEY_LOCAL_MACHINE\SOFTWARE\Netegrity\SiteMinder\CurrentVersion\PolicyServer=xxxxx
Thread Pool Size= 0x8; REG_DWORD
- MaxConnections:
{home_policy_server}/registry/sm.registry:
HKEY_LOCAL_MACHINE\SOFTWARE\Netegrity\SiteMinder\CurrentVersion\PolicyServer=xxxxx
Tcp Max Server Connections= 0x100; REG_DWORD
- PriorityThreadCount
For this one, add the key as per documentation (1):
The default number of worker threads in the thread pool available for
High Priority messages is five and the maximum number is 20. You can
change the default value by adding and setting the PriorityThreadCount
registry key.
To add the PriorityThreadCount registry key in UNIX
Navigate to: policy_server_home/registry.
policy_server_home
Specifies the Policy Server installation path.
Modify sm.registry and locate:
HKEY_LOCAL_MACHINE\SOFTWARE\Netegrity\SiteMinder\CurrentVersion\PolicyServer
Add the PriorityThreadCount key using the DWORD value. Verify that
the name of the key includes the equal sign (=), for example
PriorityThreadCount=
Set PriorityThreadCount to a value in the range 5-20. A value less
than five or greater than 20 disables the registry key. When the
key is disabled, the number of worker threads in the pool for High
Priority messages is the default value of five. Example: 0x6;
To illustrate:
HKEY_LOCAL_MACHINE\SOFTWARE\Netegrity\SiteMinder\CurrentVersion\PolicyServer=xxxxx
PriorityThreadCount= 0x6; REG_DWORD