What timeout settings can I set?

The following list shows timeout settings that you can set in IBM® Planning Analytics. Timeout settings allow the server to clean up inactive sessions, which frees up resources and memory from services that are used by active users. Timeouts that are set too high might have a negative impact on your environment.

TM1 SERVER IDLE
Default: 900 seconds (15 minutes)
Location: tm1s.cfg
Setting: IdleConnectionTimeOutSeconds=900
IdleConnectionTimeOutSeconds
TM1 SERVER REST/HTTP
Default: 20 minutes
Location: tm1s.cfg
Setting: HTTPSessionTimeoutMinutes=20
HTTPSessionTimeoutMinutes
CAM SECURITY
Default: 3600 seconds (60 minutes)
Location: Cognos Configuration > Security > Authentication
Setting: Inactivity timeout in seconds
Configuring session timeout values for Cognos TM1 Applications and Cognos Analytics Security
TM1 WEB (2.0.5 or earlier):
Default: 20 minutes
Location: \tm1_64\webapps\tm1web\WEB-INF\web.xml
Setting <session-timeout>20</session-timeout>
Setting the TM1 Web session timeout
TM1 WEB (2.0.6 or later):
Default: 20 minutes
Location: \tm1_64\webapps\tm1web\WEB-INF\configuration\tm1web_config.xml
Setting <add key="HttpSessionTimeout" value="60" />
Setting the TM1 Web session timeout
PMPSVC
Default: 60 minutes
Location: Cognos Configuration > TM1 Applications
Setting: Session timeout (min)
This setting updates the \tm1_64\webapps\pmpsvc\WEB-INF\configuration\fpmsvc_config.xml session-timeout.
Configuring session timeout values for Cognos TM1 Applications and Cognos Analytics Security
PLANNING ANALYTICS WORKSPACE PROXY TIMEOUT
Default: 120 seconds (2 minutes)
Location: <paw install>/config/paw.env
Setting: ProxyTimeoutSeconds
Configure parameters
PLANNING ANALYTICS WORKSPACE IDLE TIMEOUT
Default: 60m (60 minutes)
Location: <paw install>/config/paw.env
Setting: SessionTimeout
Configure parameters

In some circumstances, users might experience a session timeout when they try to access TM1 Applications (pmpsvc) while Planning Analytics Spreadsheet Services (TM1 Web) is already open in the same browser. To resolve this issue, see Why do users experience a timeout when using both TM1 Applications and Planning Analytics Spreadsheet Services simultaneously?