I have BAAN 4_c4 on Unix platform.

I am looking out for a product which would close BAAN for all idle sessions.

I know a product named "idlewhile" existed at one of my earlier client sites, but it was on an NT platform. In this, I was able to specify the time parameter. I was also able to disable all users from logging into BAAN. The functionality was quite extensive and the product cost was not that expensive too.

Could you please share your wisdom and your thoughts in identifying a viable product for this problem.

I appreciate all your input in this regard.

Thanks in advance,

Please refer to the other thread in this discussion board -

http://www.baanboard.com/baanboard/showthread.php?s=&threadid=592&highlight=idle

If you like to disable the users to log into the system when you doing the maintenance, you just need to modify the

$BSE/lib/ipcinfo file and rename the bshell to something like new.bshell and add a new entry for only the IS guys like you, as
bshell.is so that you can log into the system and others cannot.

This is what we are using at the Customer site I am currently working for. It is called CloseIdle. The web site is.



Website: http://www.dsigb.com




This works really great, just make sure you update the ini to fit your installation.

Mahasund,

I too am looking for a tool that closes idle Baan sessions.

Somebody pointed me to the following Baan solutions, I haven't had a chance to look at these yet but they may be of interest to you.

19868
110907
110908

Regards

PJ

Just another endorsement for Close idle

It gives flexibility to differentiate between groups of users and different timeouts , if you do not mind the admin

Also saves having to kill users for maintenance jobs when they forget to log out

L.S.,

It's also possible to block BaaN for all users exept bsp bij filling the file ${BSE}/blok with the word "baan".


Henk.

I don't believe this is standard Baan functionality in any version.

Sounds like a little scripting was done on your box ;)

Neat idea though, to have a file with users that are allowed and users or usergroups that are disallowed.

I'll get on that one.

Francesco,

I don't know if it IS standard BaaN-functionality, but anyway, it's not that hard to realize. First you've got to create the directory ${BSE}/blok. In this directory, you create a numer of files: for instance "COMPblok", "USERblok" and "PCblok".
Then you have to edit the "bshell6.1"-file:
*************************

# BLOCKS #############################################################
#
# File containing blocked Package Combinations
PCfile=$BSE/blok/PCblok

# File with blocked companies
COMPfile=$BSE/blok/COMPblok

# File with blocked user-id's
USERfile=$BSE/blok/USERblok

#
# Blocked Package Combinations
#
# Insert the PC's you want to block, seperated by spaces.
# Do this in the file named ${BSE}/blok/PCblok.
# To block ALL PC's, insert the word "BAAN" in this file.
PC="`cat $PCfile 2>/dev/null`"
# Close everything?
if test "$PC" = "BAAN"
then
exit
fi
for i in $PC
do
if `grep $i $BSE/lib/user/u$USER > /dev/null`
then
exit
fi
done
#
# Blockage of companies
#
# Insert the companies you want to block, seperated by spaces.
# Do this in the file named ${BSE}/blok/BEblok.
# To block all companies: put the word "BAAN" in the file.
COMP="`cat $COMPfile 2>/dev/null`"
# Close everything?
if test "$COMP" = "BAAN"
then
COMP="[0-9][0-9][0-9]"
fi
for i in $COMP
do
if `grep -E compnr:$i $BSE/lib/user/u$USER > /dev/null`
then
exit
fi
done
#
# Blockage of user-id's
#
# Put the user-id's you want to block in the file ${BSE}/blok/USERblok
#
# To block all users, put the word "BAAN" in this file.
USER="`cat $USERfile 2>/dev/null`"
# Close all?
if test "$USER" = "BAAN"
then
USER=$USER
fi
for i in $USER
do
if `grep $i $BSE/lib/user/u$USER > /dev/null`
then
exit
fi
done

***************************
Come to think of it: I think we built this ourselves. But that doesn't prevent anyone for using it, now does it...?



Henk.

A quick way to block all users (whomever you want) would be to change the $BSE/lib/ipc_info file. comment out the bshell line and add your own

## bshell3 s 0 0 s ${BSE}/bin/bshell6.1
bshell3 s 0 0 s ${BSE}/bin/bshell6.1

Then on the configure screen of BW, enter bshell3 to connect.
Just tells who knews to know.

AS far as the idle process thing, we had our Unix Admins write some scripts to remove all processes over 24 old (unless own by
a particular group of users).

Did anybody consider using the SESSION_TIMEOUT variable? (Standard Baan functionality since not so long ago.)

Hi,

It is not difficult to kill correctly idle BAAN sessions especially if you use Oracle. You shall use sys view $v_session, write a small script which looks the values of fields username, os_user and min(last_call_et). The timeout depends on your wish.
When min(last_call_et) is 0 it means the os_user does absolutely NOTHING. You can correctly close his pid (calculating his pid you can via awk) with the help of bshcmd.

Closing Baan you can thru chmod 000 $BSE/bin/bshell6.1 but in this case you must have another bshell just for you in $BSE/lib/ipc_info.

REgards,
Old Vens
:)

SESSION_TIMEOUT can be used, see several solution on this issue. Also be aware you need a recent portingset and tools software to have it run correctly...

Issues with external processes (like import/export on databases) started from sessions have been addressed recently.

Hi,
sometimes some versions of BWclients show that the CPU activity grows although the user doesn't do any active steps. Maybe Windows itself has its own bugs in this case. So session_timeout may not be the solution in some situations.

Hey mahasund!

The product we used at BFG was called OST Frontline - that was pretty good actually. Currently I am using a product called CloseIdle. This product however should be installed on each client, I am using a batch script for that. Look me up at Yahoo if you got the chance.

I suppose it is pretty good (we had tested it) but as far i as rememeber it doesn't work upon subsessions
(xxxxxxxxxs000)

I don't see any problem in using Session timeout variable. Because all the processing is done in Backend, I don't think there will be any problem if we kill the sessions on the Client side.

I am using this variable (with 10 minutes) from last one year & i never faced a problem. But one thing is you need to have the last porting set.

Process like Rebuild inventory, MRP Run (or) sequential dump for the ful company are successfully completed.

Any comments can be shared..,

regards
Sudha

Hi,

We are using SESSION_TIMEOUT to kill BaaN Idle sessions and working fine.

Regards,
BK

where can I put the value of session_timeout ?
is it at server or at client place?
is it in minutes ??

We have set session_timeout=10 and it works perfectly but there is one problem.

What Our users do, they display one report (any report) and in display browser they go to option and click on read tail.

Now what happened, the process is running in the background and it does not kill login in 10 minutes.

Can anybody help me out

Thanx in advance

We have set session_timeout=10 and it works perfectly but there is one problem.

What Our users do, they display one report (any report) and in display browser they go to option and click on read tail.

Now what happened, the process is running in the background and it does not kill login in 10 minutes.

Can anybody help me out

Thanx in advance

you have to create new file with name all in folde {BSE}\lib\DEFAULTS. But you must have service pack more than 12 or check which solution u require for that.

You siply pur SESSSION_TIMEOUT:10 in you created file .

Sanjay

Thanx for your suggestion. We have already created file with the name ALL in $BSE/lib and it works perfectly.