CMC/BI Launchpad Session Timeout in SAP BI Platform 4.x

The default timeout for a logon tokens at BI platform is 20 minutes (1200 seconds), and this calculated from the last interaction with JAVA server.
In the platform Enterprise sessions are generated for each connection, and one enterprise session is valid up to 60 minutes.
Online sessions for Crystal Enterprise and Webintelligence applications after 10 minutes inactivity (half time) are swapped to hard disk for performance reasons.
Generally data connection sessions will be disconnected after 30-60 minutes inactivity.
(These settings are based on SAP BI platform 4.1 SP 7)

Background & Process
When a user or an administrator logs on into BI Launchpad or CMC with any authentication types (may be Enterprise, LDAP, Windows AD, SAP, Oracle EBS, Siebel, JD Edwards EnterpriseOne, PeopleSoft Enterprise) at least 2 timeout counting starts

  • Session timeout
  • Logon token timeout (see next chapter)

The timeout of a these kind of sessions are managed by the java server (by default it is the tomcat server). All applications, such as webi or explorer, or Crystal Reports Viewer using the same timeout configuration, which is driven by the session. By out of the box installation BI Launchpad and CMC displays timeout warnings when session will run for timeout.

The timeout counting is starting from last action which interacts with the Java web application server, so actions like in webi click on tabs of the report, copy any object from the report, start drill etc. restarts the timeout counting. So best practice to set the timeout for a time which is needed to review a report, but minimum 20 minutes.

Configuration
The session timeout is set in the tomcat web server configuration.
Default value is 20 minutes.

To modify this follow these steps

1. Go to <BI 4.0 Install folder>\SAP BusinessObjects\tomcat\webapps\BOE\WEB-INF folder

2. Open web.xml in Notepad and search for the following tag:

3. To modify to 60 minutes, change the value of <session-timeout> xml tag.
This example increases the timeout up to 60 minutes.

4. Go to <BI 4.0 Install folder>\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\warfiles\webapps\BOE\WEB-INF folder

5. Open web.xml in Notepad and search for the following tag:

6. To modify to 60 minutes, change the value of <session-timeout> xml tag.
This example increases the timeout up to 60 minutes.

7. Save the file and restart tomcat via Central Configuration Manager

 

Change Properties through CMC
Once the warfiles are updated, log into the Central Management Console (CMC) and do the below changes.

1. Go to Servers

2. Click the Servers List

3. Right-click the Web Intelligence Processing Server

4. Select Properties

5. Change “Idle Connection Timeout” to 60 minutes

cmc-bi-idle-connection-time-out

6. Click Save & Close button

7. Right-click the Web Intelligence Processing Server again

8. Select Restart Server

 

 

Check Also

Determining the Number of Work Processes

Procedure The context change for processes on Windows is more time-consuming compared to UNIX. Therefore, …