Overview
With long-running reports, users often experience timeout issues in InfoView. The tips shown below should assist in alleviating your timeout problems.
Environment
- Windows Server 2008
- Tomcat
- Business Objects XI 3.1
Disclaimer: Please note that the these configuration changes should be performed in a Test environment - prior to making the changes in your Production environment. The settings changes listed below were obtained during a process I undertook to troubleshoot timeout issues in my environment. I make no guarantees that these changes will solve all your timeout issues. Please also note that all of my reports in this environment are Web Intelligence reports. There may be other configuration changes required to optimize Desktop Intelligence and Crystal Reports.
Change # 1
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.
Go to the
\Business Objects\Tomcat55\webapps\AnalyticalReporting\WEB-INF folder and open the web.xml file.
Change the setting for the <session-timeout> node from the default of 20 minutes - to a larger value - I use 60.
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). Click on the Servers link.
Double-click WebIntelligenceProcessingServer.
Change the Idle Document Timeout setting to 3600.
Change the Idle Connection Timeout setting to 60.
Add the switch "-requesttimeout 3600000" to the end of the Command Line Parameters.
Change # 3 - Re-start Services.
Open the Central Configuration Manager(CCM).
Stop and re-start the Apache Tomcat service and the Server Intelligence Agent (SIA)
Change # 4 - Registry changes.
Open the Registry Editor (Start/Run/regedit)
Locate the HKEY_LOCAL_MACHINE\SOFTWARE\Business Objects\Suite 12.0\CMS\Instances\cmsname.cms node - and set the. IdleSessionTimeout to 14400000
Note, if you have Business Objects installed on a 64-bit server (which is my environment), the path is:
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6532Node\Business Objects\Suite 12.0\CMS\Instances\cmsname.cms
Locate the HKEY_LOCAL_MACHINE\SOFTWARE\BusinessObjects\Suite 12.0\default\WebIntelligence\Server\Admin\SwapTimeOut node - and set the. IdleSessionTimeout to 3600000
Note, if you have Business Objects installed on a 64-bit server (which is my environment), the path is:
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6532Node\BusinessObjects\Suite 12.0\default\WebIntelligence\Server\Admin\SwapTimeOut
Change # 5 - Universe Parameter changes.
Using Designer, Import your Universe from the Repository. From the main menu select File/Parameters.
In the Definition tab, click the Edit button for the connection.
Change the Connection Pool Mode setting to Disconnect after each transaction.
In the Controls tab, change the Limit size of result set to setting to a value appropriate to your environment. I have mine set to 1,000,000.
Change the Limit Execution time to 60 minutes - or higher if necessary. The default is 20 minutes.
Click OK, save the Universe and export to the repository.
Conclusion
I hope that you found this article useful. If you have any other tips/suggestions please feel free to add your comments.