Configuring subsession timeout

The concept of an application subsession is toolkit-specific and does not exist in WebSphere Application Server. As a result, the only way to configure application subsession expiration is through the toolkit, which means the cookies attribute does not affect the cleanup of application subsessions. To configure the timeout of an application subsession, set it as part of the CSServer definition as shown in the following example:
<CSServer id="realCSServer" inactivityClientTimeout="1800000"
    timeBetweenSessionCheck="3600000" appSessionTimeout="60000" /> 

The appSessionTimeout attribute sets the actual expiration timeout of the application subsession and timeBetweenSessionCheck sets how often the thread that searches for expired application subsessions performs this task. Both are set in milliseconds. In this example, the session expires after one minute of inactivity (60000) and the thread that will detect expired application subsessions is activated each hour (3600000).