Optimize performance for the IBM®
Spectrum Symphony session director by tuning
settings within the application profile, session director environment variables, and applicable
configuration files.
Configuring how the session director (SD) handles task history files IBM Spectrum Symphony session director (SD) when it queries history files for these tasks. In addition, with the increased workload for the session director, this can slow down how the session director responds to newly submitted work. Configuring the session director (SD) to automatically reject repeatedly invalid authentication requests IBM Spectrum Symphony session director (SD) will record its information (username, IP address, and application name). In some cases, the client will send the authentication request to the session director repeatedly, and if the request cannot pass verification, the session director, therefore, becomes very busy and cannot handle other requests in a timely manner, leading to a denial of service attack on the session director. To prevent this bottleneck to session director performance, configure the sd.xml file to allow the session director to reject these repeated requests, using user-defined rules for handling authentication requests with same information (username, IP address, and application name). This way, once the request is rejected, the session director will no longer try to verify the username and password in it, but return an authentication failure message instead. Optimizing how a session manager (SSM) manages disconnections from the session director (SD) IBM Spectrum Symphony session manager (SSM) is disconnected from the session director (SD), such as due to network errors, the SD detects this disconnection, and attempts to restore the SSM connections. Once the reconnection retries reach their limit, the new SSMs will be started. This reconnection logic is enabled by default. You can optionally configure settings to optimize the base behavior; use any or all of the following steps to enhance SD's detection of SSM disconnections, extend the TCP_KEEP_ALIVE_TIME configuration used to detect disconnections due to network errors, and prolong the time that the SSM waits to reconnect to EGO.