siemon_sun
15th May 2008, 06:25
We have many inactive user in Baan and they prevent other users to login Baan.

Can or not automatically log off from Baan for these inactive users?

Thanks a lot.

sukesh75
15th May 2008, 09:07
There is an old way of dealing with this and which has been discussed over and over on this board...... its by timing out the users.
1) Go to BSE/lib/defaults folder and create a file named "all" (without extensions)
2) Open the file and enter "session_timeout:n" (without quotes) where n is number of minutes to wait before the user is timed out thus freeing up his/her license.
In addition to the above if you want to give certain users more time before they are timed out then go to BSE/lib/user and in the user file (u<login>) enter the same parameter "session_timeout:n", where n this time is greater than what you have entered in the "all" file.

hth
sk

siemon_sun
15th May 2008, 09:47
Thanks.

I have a question:Must I need to shutdown and restart Baan service,yes or no?

jclju1
15th May 2008, 10:51
No. When user starts his client, it will read this setting.

siemon_sun
20th May 2008, 10:28
No. When user starts his client, it will read this setting.

Can the job be also log off?

Andy..
20th May 2008, 18:18
The functionality above (explained very well by sukesh75) is only available in more 'recent' versions of Baan4 service pack/portingset. I should hope most people will be more up-to-date but there's no guarantee!

CloseIdle was one of the few reliable ways before the above functionality was added and is still available for Baan. It goes beyond the above functionality by performing a save on the data if a session is left open as well as preventing a user logging in to Baan more than once (common when you are short of licences!). You can also set certain sessions to not be closed and have different or even no timeouts for certain users. Details at http://www.closeidle.co.uk

jclju1
21st May 2008, 11:38
Can the job be also log off?
Yes, it could happen. So, it is fine to set session_timeout to 0 for user who starts job.