With long-running reports, users often experience timeout issues in InfoView. The tips shown below should assist in alleviating your timeout problems.

book

Article ID: 49665

calendar_today

Updated On:

Products

SUPPORT AUTOMATION- SERVER CA Service Desk Manager - Unified Self Service KNOWLEDGE TOOLS CA Service Management - Asset Portfolio Management CA Service Management - Service Desk Manager

Issue/Introduction

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>

Figure 1

Change the setting for the <session-timeout> node from the default of 20 minutes to a larger value (i.e. 60).

<Please see attached file for image>

Figure 2

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>

Figure 3

Double-click WebIntelligenceProcessingServer.

<Please see attached file for image>

Figure 4

Change the Idle Document Timeout setting to 3600.

<Please see attached file for image>

Figure 5

Change the Idle Connection Timeout setting to 60.

<Please see attached file for image>

Figure 6

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

<Please see attached file for image>

Figure 7

Change # 3 - Re-start Services.

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

<Please see attached file for image>

Figure 8

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

<Please see attached file for image>

Figure 9

Change # 4 - Registry changes.

On the CABI server, launch 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 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>

Figure 10

<Please see attached file for image>

Figure 11

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>

Figure 12

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>

Figure 13

In the Definition tab, click the Edit button for the connection.

<Please see attached file for image>

Figure 14

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

<Please see attached file for image>

Figure 15

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>

Figure 16

Environment

Release:
Component: SDBOXI

Attachments

1558709968867000049665_sktwi1f5rjvs16roq.gif get_app
1558709967019000049665_sktwi1f5rjvs16rop.gif get_app
1558709965038000049665_sktwi1f5rjvs16roo.gif get_app
1558709963097000049665_sktwi1f5rjvs16ron.gif get_app
1558709961351000049665_sktwi1f5rjvs16rom.gif get_app
1558709959505000049665_sktwi1f5rjvs16rol.gif get_app
1558709957309000049665_sktwi1f5rjvs16rok.gif get_app
1558709955568000049665_sktwi1f5rjvs16roj.gif get_app
1558709953437000049665_sktwi1f5rjvs16roi.gif get_app
1558709951557000049665_sktwi1f5rjvs16roh.gif get_app
1558709949659000049665_sktwi1f5rjvs16rog.gif get_app
1558709947618000049665_sktwi1f5rjvs16rof.gif get_app
1558709945670000049665_sktwi1f5rjvs16roe.gif get_app
1558709943602000049665_sktwi1f5rjvs16rod.gif get_app
1558709941788000049665_sktwi1f5rjvs16roc.gif get_app
1558709939781000049665_sktwi1f5rjvs16rob.gif get_app