InfoView Timeout Crystal Report Server 2008 Business Objects 3.1

Question

After two days of digging, poking, prodding and fumbling around in the dark I finally found a method (one that actually works!) to change the timeout period for InfoView.  Venkat Patnaik (second message) posted an excellent procedure in a place that is not readily apparent:
/message/8250448#8250448 [original link is broken]
Following his method, my InfoView seems to timeout after about 3 minutes.  I am going to play with the settings to see if I can get it dialed in a bit more, but I wanted to post this so there is a thread with a relevant subject so people can find Venkat's excellent post.  Thanks Venkat!

Answer 1

Wow I am getting really tired of SAP's constant broken links and moving things around.  That link worked great a couple of weeks ago when I posted this message.  I did some digging around for that particular thread but I was not able to find it this morning.    Maybe it was deleted.... 
Luckily I documented my procedure for making these changes and I did not stray from Ventak's original procedure except for making paths and such specific to my environment. 
Basically the timeout values need to be changed in several places:
1. Stop the TomCat server via the Central Configuration Manager before doing anything else. 
2. Modify the web.xml file in each of the following directories:
C:\Program Files\Business Objects\Tomcat55\webapps\InfoViewApp\WEB-INF\web.xml
C:\Program Files\Business Objects\Tomcat55\webapps\InfoViewAppActions\WEB-INF\web.xml
C:\Program Files\Business Objects\Tomcat55\webapps\CmcApp\WEB-INF\web.xml
C:\Program Files\Business Objects\Tomcat55\webapps\CmcAppActions\WEB-INF\web.xml
Parameters to change:
***This parameter may not exist in all web.xml files.***
<!-- Set to false to disable logon with token. -->
    <context-param>
        <param-name>logontoken.enabled</param-name>
        <param-value>true</param-value> (Change to false)
    </context-param>
<!-- Define the default session timeout for your application,
         in minutes.  From a servlet or JSP page, you can modify
         the timeout for a particular session dynamically by using
         HttpSession.getMaxInactiveInterval(). -->
    <session-config>
        <!-- 20 minutes for session objects -->
        <session-timeout>20</session-timeout>   (Change to 5)
    </session-config>
3. Modify the registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\Business Objects\Suite 12.0\CMS\Instances\<SERVER NAME> u2013 IdleSessionTimeout=0x927C0 (600000)
The key is a REG_DWORD value and the value is in hexadecimal.  Set the timeout value to 90,000 ms u2013 1.5 minutes with the value 0x15F90.  You can use other hex values as desired, 90,000 ms worked for me. 
4. Restart the TomCat server. 
5. Add the following command line parameter to the CrystalManagementServer parameters in the server properties window of the Central Management Console <-failovertimeout 1.5>
6. Restart the CrystalManagementServer via the CMC
Good luck, let me know if you have any questions.