This content has been marked as final. Show 7 replies
There are timeouts in the OHS config and IIS configs. I don't think IIS would impact you for workspace, though....1 person found this helpful
I have a list I made of all of the settings I had to change to get this to work in 22.214.171.124 as we had a lot of fun with timeouts as there are various settings everywhere. When I get in the office tomorrow, I'll try to add some more specifics.
Could you confirm the EXACT message users get when they are timeout and do they only get timeout out if in HFM, reports, or both?
check this doc: https://support.oracle.com/epmos/faces/ui/km/DocumentDisplay.jspx?id=1110718.11 person found this helpful
I will update this with the actual error but it seems like the application is timing out before Workspace itself.
The error that occurs past 30 minutes is:
An error has occurred. Please contact your administrator.
Error Description:Please Relogin. Session has Timed out
Page On which Error Occurred:
I noticed that the actual 'your session is going to timeout' warning and then getting punted back to the login screen happens beyond the 30 minute mark (I have not timed it, but it appears closer to or at the 60minute timeout I had set).
Edited by: 987694 on Feb 22, 2013 10:45 AM
Edited by: 987694 on Feb 22, 2013 10:47 AM
Yes, the application definitely times out before workspace. When we were on 11.1.1 and the application has timed out we had to close and open it again without logging out from the workspace itself. Now the cool thing about 126.96.36.199 is that it re-opens the application automatically as long as you are not timed out from the workspace1 person found this helpful
Thanks! I haven't yet searched for extending the application timeout -- if you have the details handy can you provide them?
Better check all the documents in the link I posted above, but the most basic advice from the Doc 583878.1 is:
Increase timeout settings for web sessions on the HFM site
In normal scenarios, increasing the session timeout might result in performance issues; as more "dead" sessions are kept open much longer, more processing power is wasted on them. To have long session timeouts is also (generally) considered bad practice from a security point of view.
Note that these timeouts are only enforced on idle sessions, i.e. when the user will not "click anything" for that amount of time. For this reason, they rarely need to be set to anything higher than 120 minutes.
The following instructions change the idle timeout from default 20 minutes to 30 minutes in Microsoft Internet Information Services 6 (IIS):
1.Go to Start > All Programs > Administrative Tools > Internet Information Services (IIS) Manager.
2.Expand the server node <ServerName> (local computer).
3.Right click on the application pool node.
5.Select the Performance tab.
6.Change the Idle timeout value from 20 to 30 minutes.
9.Expand the node Web Sites.
10.Right click on the 'HFM' web site.
11.Go to Properties > Home Directory tab > Configuration button > Options tab.
12.Change the Enable session state > Session timeout value from 20 to 30 minutes.
15.Test that the timeout is now the new value.
Thanks!!!! That did it :)