we are XI3.1 SP2, FP2.6 – oracle db – windows server – WinAD/Vintella on Tomcat. Have set up some URL for opendoc to WEBI reports, but when user goes to report – there seems to be no way for them to LOG OUT, this leaving sessions open.
Is there a spot within the OpenDoc web.xml where I can set a ‘listener cleanup’ that would log out the session at least within a certain amount of time?
Or is there a parameter that can passed within the URL that would accomplish this?
There is no supported method of terminating an Open Document session as described in SAP KB# 1384496. One option is to generate a logon token and set the session lifetime to a short value before redirecting the user to the report. The other option which I don’t recommend is to reduce the session time for the OpenDocument web application via its web.xml file. This option can negatively affect InfoView users which is why I would shy away from implementing it.
Thanks, Bob. But I’m afraid that I don’t know how to ‘generate a logon token and set the timeout session’. Is this something that is put into the ‘url’ created pointing to the opendoc? if so, do you know documentation that explains how to do this?
also, wondering how setting timeout on OpenDocument web.xml would affect the Infoview users. Could you further explain this for me?
It looks to me that timeouts within Infoview and/or full clients remains an issue even with V3.1 from all that I am reading.
Just hoped that SAP had improved the product as opposed to just trying to fix the bugs in it… Mayhap V4 will be better… (One can only hope).
We are on the same FP version and we see the same issue. I saw this shortly after rolling out 3.1 in April 2009. The situation is made worse if you utilize concurrent licensing. Processor or named not so bad. However, concurrent you are really hurting when 3.1 refuses to release the licenses. I have seen my system hold onto this stuff for over 18 hours or so. I called SAP in late 2009 concerning this, but as of right now it is still an issue. They did provide some reg keys to alter to see if it made the situation better, but it really didn’t seem to work. Anyway, like you here’s hoping BOBI 4.0 does a better job of session management.
well – I did see some documents on the SAP about setting tokens with openDoc, but I’m not that savvy to understand how, where, exactly what to do with it… Nothing that I see on SAP site indicates any relief for this condition soon. I tried to find something on the new coming version, without any success yet.
I did find something about changing the web.xml for infoviewapp for ‘logontoken.enable’ to be ‘false’ where we had it as ‘true’. I’ll watch for a while and see if that at least helps clear out some of the sessions left behind.
OpenDoc has a lot of promise, but it apparently isn’t really part of BOXI – just some ‘bolt on’ they found!
I did some of the ‘reg’ key changes some time ago, but that hasn’t really helped.
But, I DID find a little code that allows me to actuall ‘kill sessions’ though! That at least let’s me clean out those that I KNOW are dead!
Sure do miss the good ole 6.5 Supervisor tool!!! Ah, well. Such is progress!
What is even more frustrating is that I created an asp script that utilizes the SDK and creates a session using session manager and makes a call to opendocument. It is a really nifty script that has made pumping out content to our users via URL links much easier. In the script I dictate the session manager to log in the user and after 20 minutes close the session. BOE totally ignores the setting!
I also have a nice java app that allows me to close these sessions, but for the price of admission…I really shouldn’t have to babysit these sessions. Good luck!
SAP has example code to generate a logon token in note 1511423. Once you have the token, you would redirect the user using a URL along the lines of http://:/InfoViewApp/logon/start.do?ivsLogonToken=" + logonTokenValue. It is possible to set the token lifetime before creating an instance. This is a server side implementation so it isn’t as simple as appending a parameter to the URL.
Eons ago, I traced the HTTP calls made when performing various actions in InfoView. Some action(s) which I can’t remember opened reports using the OpenDocument web application. Since the timeout is set at the web application level, a low value has the negative consequence of impacting your InfoView users.
There is a somewhat helpful document titled boxi3_info_timeouts.pdf available somewhere on the SAP site. I would post it if not for the whole copyright thing. It provides some insight into the timeout lifecycle although it doesn’t provide a good solution to the problem. Grrr!
(BOB member since 2007-10-23)
(BOB member since 2007-10-23)