Select Properties. Change “Idle Connection Timeout” to 45 minutes. Click Save & Close button.
Navigate to Home. Click Applications under Manage.
Right-click on Web Intelligence. Select Properties. Change the Auto-save time delay‟ to 2700 seconds. By default, this is 600 seconds.
IMPORTANT: The following step involves editing the registry. Using the Registry Editor incorrectly can cause serious problems. Use the Registry Editor at your own risk. Please refer to Knowledge Base article 1323322 for more information.
Open the Registry Editor. (Click Start > Programs > Run > type regedit.) Modify the following values:
HKEY_LOCAL_MACHINE\SOFTWARE\Business Objects\Suite 12.0\CMS\Instances\cmsname.cms, Change IdleSessionTimeout=2700000
HKEY_LOCAL_MACHINE\SOFTWARE\BusinessObjects\Suite 12.0\default\WebIntelligence\Server\Admin\SwapTimeOut to 2700000.(Only if WebIntelligence reports timeout)
Is there anywhere we can do this where we won’t have to re-implement the change every time we redeploy the WAR file or patch the system (similar to the /custom folder for BILaunchpad.properties)?
No, I don’t see it. I have installed service packs and I have seen multiple times that I lost my files even though they are were in custom folder.
It is always better to save all the configuration files as a backup at a different location or network drive, as it will be easier to restore them back to their respective folders.
Are you putting the ‘custom’ files in the following location?
d:\Program Files (x86)\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\warfiles\webapps\BOE\WEB-INF\config\custom
This one seems to stay stable when patching and redeploying WAR files.
If you put your .properties files in
D:\Program Files (x86)\SAP BusinessObjects\tomcat\webapps\BOE\WEB-INF\config\custom they will get overwritten on every refresh of Tomcat.