Setting tuning parameters for the Sametime Proxy Server
Refine the tuning parameters for the Sametime® Proxy Server for better performance.
Procedure
- On the Sametime Proxy Server, log in to the IBM® WebSphere® Integrated Solutions Console as the WebSphere administrator.
-
Set JVM verbose garbage collection and heap sizes on the Sametime Proxy Server by completing the following steps:
-
Adjust web container transport settings for the Sametime Proxy Server by completing the following steps:
- In the container settings section, click .
- Click .
- In the Maximum open connections field, enter a value that is two times greater than the maximum number of expected concurrent users.
- In the Inactivity timeout field, enter 120 seconds.
- Click .
- In the Maximum open connections field, enter a value that is two times greater than the maximum number of expected concurrent users.
- In the Inactivity timeout field, enter 120 seconds.
- Click OK.
-
Set the object cache instance size for the Sametime
Proxy Server by completing the following steps:
- Click .
- In the Scope list, select the STProxyServer or STProxyCluster to be modified.
- Click Access control objects and in the Cache size field, enter a value that is two times greater than the maximum number of expected concurrent users.
- Click Real Time Session Objects and in the Cache size field enter a value that is two times greater than the maximum number of expected concurrent users.
- Click STProxySTUserMap and in the Cache size field enter a value that is two times greater than the maximum number of expected concurrent users.
- Click OK.
-
Increase web container threads by completing the following steps:
- Click .
- In the list of application servers, click the STProxyServer link.
- In the Container Settings section of the STProxyServer Configuration page, click .
- In the Maximum in-memory session count field, enter a value that is one greater than the maximum number of expected concurrent users.
-
Increase log and trace file settings by completing the following steps:
- From the list of application servers, choose the Sametime Proxy Server you are configuring.
- In the Troubleshooting section, click .
- In the System.out section, set File size - Maximum sizeto 10 MB and set Maximum Number of Historical Log Files to 20.
- In the System.err section, set File size - Maximum size to 10 MB and set Maximum Number of Historical Log Files to 20.
- Click OK.
-
Increase the available TCP ports by completing the following steps according to platform:
- Linux - Complete one of the following two steps:
- Use the ulimit command on the Proxy Server. For example, enter the following
command:
ulimit -n 65535
- In the
nofile
section of the/etc/security/limits.con
file, set ulimit to 65535.
For detailed information about using the ulimit command see the following Tech Note: Guidelines for setting ulimits (WebSphere Application Server).
- Use the ulimit command on the Proxy Server. For example, enter the following
command:
- Windows (32-bit)
Enter the following regedit command:
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters] "TcpNumConnections"=dword:00fffffe
- Windows (64-bit)
Use the netsh int ipv4 show dynamicport tcp command, set to a maximum value of 60000. Enter the following command:
netsh int ipv4 set dynamicport tcp start=1025 num=60000
- Linux - Complete one of the following two steps:
-
Modify the Web container - thread pools setting on every Sametime Proxy Server in your configuration by completing the
following steps on each Sametime Proxy Server:
- Click .
- In the Additional Properties section, click Thread pools.
- Click WebContainer.
- In the Minimum Size field, enter 100 threads.
- In the Maximum Size field, enter 100 threads.
- Click OK.
- Save the change to the master configuration by clicking the Save link in the "Messages" box at the beginning of the page.
What to do next
AIX, Linux: AIO (Asynchronous Input/Output) native transport in WebSphere Application Server might result in limiting the number of concurrent users and unintended logouts. Disabling AIO will solve those issues. For more information, see the technote Disabling AIO (Asynchronous Input/Output) native transport in WebSphere Application Server.