XI 3.1 .Net InfoView Concurrent User Timeout

[Former Member]

I am using BO XI 3.1, .Net infoview, and Windows AD authentication with SSO. In past BO Enterprise versions there was a standard method to reduce the time out period so that concurrent user sessions would end quickly after the user closed the browser. I am not finding a solution to this with XI 3.1. Has anyone been able to solve this?

The only thing I can find is this post, which after trying to did not solve the problem.

I have also opened up a case with support so when I find out the solution it will be posted here for everyone.

[Former Member · Accepted solution]

Jacob,

Have you found a way to reduce the timeout period in XI 3.1? We are having an issue where the concurrent licensing is getting to the max limit when users close the browser instead of logging off.

We would like to reduce the the timeout from 20 minutes to 10.

Thanks,

Mike

[Former Member · Accepted solution]

Mike,

I do not have a resolution to this problem yet; I am still working with SAP support to find a solution but at this point I do not know if they will be able to come up with one. I have been told that since Business Objects/SAP stopped selling concurrent licenses that the problems with the InfoView not timing out is a new feature and that I should move to processor based licensing.

[Former Member · Accepted solution]

Stoped selling concurrent licenses? That is what my implementation of Crystal Report Server 2008 came with, 5 concurrent licenses. I cannot get the InfoView timeout period to change no matter what I do. Every post says that lowering the timeout value from the default of 20 for the InfoView app will do the trick, but no dice.

The default seems to be 30 minutes to me anyway and I cannot figure out where this setting is coming from. I successfully changed the timeout period for opening a report via a URL using Enterprise authentication but I had to make changes to the web.xml file for the CrystalReports application.