Configuring sessions for use by accounts

Procedure

  1. For each account, the on-premises Integration Server maintains a session pool to send responses to the cloud. Integration Server provides server configuration parameters to set the pool size and the interval at which Integration Server sweeps for unused sessions. Integration Server starts with a minimum number of sessions for each account. watt.wmcloud.sessionPool.minCount controls the minimum pool size. When the minimum number of sessions are in use, Integration Server creates new sessions to handle more requests. Integration Server continues to create new sessions until it handles all the requests for the account or it reaches the maximum size of the session pool. The watt.wmcloud.sessionPool.maxCount value determines the maximum size of the session pool for the account. After the session pool reaches the maximum size, Integration Server reuses sessions in a round-robin fashion. As the load reduces, sessions become unused. Integration Server uses a background thread to sweep for and remove unused extra sessions. For example, if watt.wmcloud.sessionPool.minCount is set to 3 and an account session pool contains 10 sessions, 7 of those sessions are extra or more. If 8 of the 10 sessions are unused, Integration Server removes only 7 of the unused sessions to keep the minimum number of sessions in the pool.
  2. The interval at which the sweeper runs is controlled by the watt.wmcloud.sessionPool.sweeperInterval parameter.
    • watt.wmcloud.sessionPool.max Count - The maximum number of sessions in the session pool that is used to send responses to the cloud.
    • watt.wmcloud.sessionPool.min Count - The minimum number of sessions in the session pool that is used to send responses to the cloud.
    • watt.wmcloud.sessionPool.sweeper Interval - The interval at which Integration Server removes unused sessions in session pools for the accounts. Integration Server removes only the number of unused sessions more than the minimum session pool size.
    For more information about the parameters, see the webMethods Integration Server Administrator’s Guide.