{DISCLAIMER} - Please use this information carefully, please test and retest on a non-live environment before implementing in production. Use this as a reference.
This information is based on my experience and it may differ from your own. I have the following setup:
Loadbalancer (Citrix Netscaler 9.1)
Apache 2.2.14 sitting on DMZ (using Mod_JK)
Tomcat 6.0.24
Business Objects XI R3.1 SP2 FP2.4
All Windows Server 2008 OS
All timeouts set to 60 minutes.
[QUESTION] Is this really an error?
An error has occurred: Unable to reconnect to the CMS. The session has been logged off or has expired. (FWM 01002)
[ANSWER] No, unfortunately BOXIR3.1 sends an "error message" when the user is inactive for a period of time
There are many places where a timeout can occur in Infoview. All impact the user experience differently. My personal experience has been that even though the session has timeout the user will get many different errors depending on where they are in the application.
e.g.
Unfortunately BOBJ architecture does not allow administrators to set 1 global timeout (what a novel idea). Wouldn't it be awesome if there was a way to let the user know that a timeout was coming? -- like a coutdown.
I've seen many disparate entries all over the internet explaining this issue.
This blog is an attempt to document all the places where you need to setup timeout parameters.
*** NOTE: Make sure you back up all your original files before modifying them.
Loadbalancer: There are many flavors of loadbalancers but in general they all have the following features:
Persistence timeout (minutes): 60
Backup Persistence timeout (minutes): 60
Client Idle Timeout (seconds): 3600
*** It is extremely important that you contact your network administrators so they can help you set the correct combinations of session timeouts.
Apache Servers:
C:\Program Files\Apache Software Foundation\Apache2.2\conf\httpd.conf
KeepAlive On
KeepAliveTimeout 1200
TimeOut 1500
C:\Program Files\Apache Software Foundation\Apache2.2\conf\workers.properties
worker.{server_name}.reply_timeout=0
worker.biboxiweb06.connection_pool_timeout=60
TOMCAT Servers:
C:\Program Files\Apache Software Foundation\Tomcat 6.0\conf\server.xml
connectionTimeout="20000"
C:\Program Files\Apache Software Foundation\Tomcat 6.0\webapps\AnalyticalReporting\WEB-INF \Web.xml
distributable
true
60
C:\Program Files\Apache Software Foundation\Tomcat 6.0\webapps\CrystalReports\WEB-INF \Web.xml
distributable
true
30
C:\Program Files\Apache Software Foundation\Tomcat 6.0\webapps\InfoViewApp\WEB-INF\Web.xml
siteminder.enabled
false
logontoken.enabled
false
persistentcookies.enabled
false
distributable
true
60
C:\Program Files\Apache Software Foundation\Tomcat 6.0\webapps\InfoViewAppActions\WEB-INF\Web.xml
distributable
false
60
C:\Program Files\Apache Software Foundation\Tomcat 6.0\webapps\OpenDocument\WEB-INF\Web.xml
distributable
true
opendoc.persistentcookies.enabled
true
opendoc.sessioncookie.enabled
true
opendoc.siteminder.enabled
true
C:\Program Files\Apache Software Foundation\Tomcat 6.0\webapps\PerformanceManagement\WEB-INF Web.xml
distributable
true
30
C:\Program Files\Apache Software Foundation\Tomcat 6.0\webapps\PlatformServices\WEB-INF\Web.xml
distributable
false
60
C:\Program Files\Apache Software Foundation\Tomcat 6.0\webapps\Xcelsius\WEB-INF\Web.xml\
distributable
true
60
In CMC:
CMC\Servers\WebIntelligenceProcessingServer\Properties
Idle Document Timeout (seconds) = 3600
Idle Connection Timeout (minutes) = 60
In Command Line Parameters add at the beginning: -requesttimeout 3600000
CMC\Servers\BIBOXIFS04.OutputFileRepository\Properties and CMC\Servers\BIBOXIFS04.InputFileRepository\Properties
Maximum Idle Time (minutes) = 60
Registry settings (CMS Servers):
Click Start > Programs > Run > type 'regedit' > Registry set HKEY_LOCAL_MACHINE\SOFTWARE\Business Objects\Suite 12.0\CMS\Instances\cmsname.cms
IdleSessionTimeout: 3600000
Registry settings (WebiProcessing Servers):
Click Start > Programs > Run > type 'regedit' > Registry set HKEY_LOCAL_MACHINE\SOFTWARE\BusinessObjects\Suite12.0\default\WebIntelligence\Server\Admin\SwapTimeOut
SwapTimeOut: 3600000
Universe Level Settings for ALL Connections
Login Timeout: 60 Minutes
Database: Depends on what database you use, most databases will have a connection idle timeout. Make sure that it is set to the same as the universe timeout.
Obviously, if you would like to set your enterprise timeout level to another number then make sure you research whether the parameter is in minutes, seconds, etc.
Hope this helps.
Gabe
2 Comments
