Setting LBI timeout params

I believe that it is under the server1 App server options of the WAS for LBI. Check under 'Session Management' There's a timeout value there.

We have changed our settings on both the application servers and on the Enterprise Application to be one hour. But when we run reports (in a new window or in the same window) and then try to open them after only 40 minutes we are presented with "Internet Explorer can not display the page" error. Is there a different setting for this?

look for the xml tag

<session-timeout>numberOfminutes </session-timeout>

in

%framework service install folder%\xxxx.ear\efswar-xxxxx.war\WEB-INF\web.xml

Our session-timeout parameter has been/was commented out. Is there a default? What is the value?

the newer versions of LBI no longer have the session-timeout problem. Thus, they have commented out the settings in the xml.

JEFFCOZAG!!! Have James call me. Let me know if you are on 9042. It is a known issue.

So just as Jimmy said the XML where the session-timeout property is set is commented out

<!--
<session-config>
<session-timeout>60</session-timeout>
</session-config>
-->

So.......why is it that our users need to log back into LBI seemingly every 10-15 minutes or so?.........

How can we change this so that they dont need to login constantly?....Ideally Id like to set it to an hour or more...

What is your Lawson core session timeout set at? Are you using DSSO?
If so, you need to set your LBI timeouts to be longer than your core session timeout value.

Correct me if I am wrong Jeff, but I believe Weissman is using MSAD authentication.

We use LDAP authentication. Which is another frustrating aspect...(wondering why we cannot just pass through the windows user name and password automatically).

There may be a way but I came in after implementation, and after all the training was gone.

@Greg - I dont know where to even see the Lawson core session timeout.

If there are 2 places where timeout values are set, with one overriding the other, and I knew how both of those settings could be found and changed, I probably wouldn't have a problem resolving this

On your WebSphere IBM console for the instance that runs your core system, find the app server, (by default server1) then click it, then I believe it's under 'Session Management' There's a timeout value there. This would only come into play if you are using Lawson Distributed Single Sign-on component with LBI though. (DSSO)

Otherwise, check the same location on your LBI WAS server.

Fantastic. Thank you Greg.

I found it finally (a link to our WebSphere console) buried in our folders and no documentation around here indicating it

I was able to change the timeout interval, but a message at the top appeared saying the server may need to be restarted for changes to take effect. Do you think that is true in this case? I'll find out soon enough I suppose.

I also am not certain that we are using DSSO either. Is there a way I can determine that?

Go to http://lbiserverurl:port/...installvalidator.jsp --> System Settings. If you see "Lawson Single Sign-on" as your Authentication Provider then you are using DSSO.

jeff: In my humble experience, a restart to the server is necessary in almost all cases of changes. And to be entirely sure, I'd stop and start the node, and manager as well as the app server(s).