Description:

Disclaimer: Please note that the these configuration changes should be performed in a Test environment prior to making the changes in a Production environment. These values are known to help alleviate generic timeout issues in Infoview. There are several other external factors (ex: firewalls) that might close connections and cause timeouts as well.

Solution:

IMPORTANT: This article contains information about modifying the registry.
Before you modify the registry, make sure to create back up of the registry and ensure that you understand how to restore the registry if a problem may occur.
For more information about how to back up, restore, and edit the registry, please review the relevant Microsoft Knowledge Base articles on support.microsoft.com.

There are a number of configuration files in the \Business Objects\Tomcat55\webapps folder. There are sub-folders that contain configuration files with timeout settings.

On the CABI Server, navigate to the 'Business Objects\Tomcat55\webapps\AnalyticalReporting\WEB-INF' folder and open the web.xml file in text editor.

<Please see attached file for image>

<Please see attached file for image>

Perform the same changes to the web.xml files in the following folders:

• ? Business Objects\Tomcat55\webapps\InfoViewApp\WEB-INF
• ? Business Objects\Tomcat55\webapps\InfoViewAppActions\WEB-INF
• ? Business Objects\Tomcat55\webappsPlatformServices\WEB-INF

Change # 2 - CMS Timeout Settings

Log into the Central Management Console (CMC) with an administrator account. Click on the Servers link.

<Please see attached file for image>

Double-click WebIntelligenceProcessingServer.

<Please see attached file for image>

Change the Idle Document Timeout setting to 3600.

<Please see attached file for image>

Change the Idle Connection Timeout setting to 60.

<Please see attached file for image>

Add the switch "-requesttimeout 3600000" to the end of the Command Line Parameters.

<Please see attached file for image>

Change # 3 - Re-start Services.

From the CABI server, launch the Central Configuration Manager(CCM).

<Please see attached file for image>

Stop and re-start the Apache Tomcat service and the Server Intelligence Agent (SIA)

<Please see attached file for image>

Locate the HKEY_LOCAL_MACHINE\SOFTWARE\Business Objects\Suite 12.0\CMS\Instances\cmsname.cms node and set the IdleSessionTimeout value to 14400000

Note, if you have Business Objects installed on a 64-bit server, the registry path is:

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6532Node\Business Objects\Suite 12.0\CMS\Instances\cmsname.cms

<Please see attached file for image>

<Please see attached file for image>

Locate the HKEY_LOCAL_MACHINE\SOFTWARE\BusinessObjects\Suite 12.0\default\WebIntelligence\Server\Admin\SwapTimeOut node and set the IdleSessionTimeout value to 3600000

Note, if you have Business Objects installed on a 64-bit server, the registry path is:

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6532Node\BusinessObjects\Suite 12.0\default\WebIntelligence\Server\Admin\SwapTimeOut

<Please see attached file for image>

Change # 5 - Universe Parameter changes.

From the CABI server, launch the Designer application and Import the ServiceDesk Universe from the Repository. From the main menu select File/Parameters.

<Please see attached file for image>

<Please see attached file for image>

Change the Connection Pool Mode setting to Disconnect after each transaction.

<Please see attached file for image>

In the Controls tab, change the Limit size of result set to setting to a value appropriate to your environment.

Change the Limit Execution time to 60 minutes - or higher if necessary. The default is 20 minutes.

Click OK and then save the Universe and export to the repository.

<Please see attached file for image>

Release:
Component: SDBOXI