Closing the DOORS Application

Mathias Mamsch - Sat Mar 13 10:28:56 EST 2010
If I understood you right, you want to auto-close a module that has been opened in "shared-edit" or "exclusive edit" if the user is inactive for a defined period of time. First of all there is no built-in option in DOORS for that. So you would need to make a script for that.

The first problem with making a script is, that you cannot reliably detect "inactivity". What you could do is detect changes to attributes but there is lots of stuff you can do in a module that you cannot detect, like changing views, running report scripts, etc... So there is the possibility to kick active users out.

The second problem is, that you need to decide what to do, if the user has unsaved work. If you close the module or change to read mode all unsaved changes are lost.

What irritates me, is that you talk about a "batch" script doing it. These options would only be possible by a script on the client PC. If you would want to do that from a remote computer that would be even harder.

My guess is there is no easy way to achieve this.

Regards, Mathias

Lion29 - Tue Mar 16 14:05:32 EDT 2010
Yes Mathias,
i really wanted the persons to be kicked out after 5.30 PM in the evening. B'cos there will be backup of the DOORS Module from 10 PM. Whenever some people keeps the Modules as open, then the backup process will fail.

So i don't really want any persons to make use of DOORS Module after 5.30 PM.

Thanks
Matthew

Lion29 - Tue Mar 16 14:05:32 EDT 2010
Yes Mathias,
i really wanted the persons to be kicked out after 5.30 PM in the evening. B'cos there will be backup of the DOORS Module from 10 PM. Whenever some people keeps the Modules as open, then the backup process will fail.

So i don't really want any persons to make use of DOORS Module after 5.30 PM.

Thanks
Matthew

PDU - Wed Mar 17 09:27:27 EDT 2010
Hi,

if your server is on Window, youcan use :

net stop "DOORS DB Server X.x" (for X.x version)
do your backup
net start "DOORS DB Server X.x"

all in a batch script and Task Scheduler.

Pierre

Lion29 - Wed Mar 17 14:49:22 EDT 2010
Is there any other means by which the client system should get out of the DOORS instead of DOORS Server.

jsarkic - Thu Mar 18 01:25:19 EDT 2010
We've tried reminding users to log out at the end of the day, but users will forget. You cannot leave it up to them, so you have to forcibly disconnect the clients from the server(s).

We also have a means to release the FlexLM licenses, which will also sever the connection.

Doesn't matter which method you choose, the end result is the same - break the client/server connection.

I am looking forward to the next major release of DOORS which is supposed to have the ability for a live backup.

ePiallat - Thu Mar 18 06:02:08 EDT 2010
I remember answering a very similar question here.

As it is basically the same problem, my recommendation is the same: don't.

Do not shut down any DOORS client remotely. But instead, send a warning message to late users 30-60' before shutting down the DOORS server.

A list of connected users is returned by the lmstat command (in license manager directory).
Shutdown warning can then be batch-sent with the net send command.

- Éric

mcnairk - Thu Mar 18 08:42:53 EDT 2010
ePiallat and others before suggest this is not a good idea, but I beg to differ.

We access DOORS through Citrix and have configured Windows Terminal Services to force out users after half an hour of idle time (to maximise usage of those ridiculously expensive international DOORS licenses). We have been doing this for years and haven't seen any corruption. The only side effects I am aware of are:

• Users may loose unsaved changes (too bad, you snooze, you loose!)
• Files are left behind in the temp folder and need to be cleaned up periodically (I do it monthly) or you will eventually run out of disk space.

PDU - Thu Mar 18 09:17:14 EDT 2010
ridiculously expensive international DOORS licenses

Information given by french IBM sells manager :
all DOORS licenses are now global (id. international), at the price of locals.

Pierre

ePiallat - Thu Mar 18 06:02:08 EDT 2010
I remember answering a very similar question here.

As it is basically the same problem, my recommendation is the same: don't.

Do not shut down any DOORS client remotely. But instead, send a warning message to late users 30-60' before shutting down the DOORS server.

A list of connected users is returned by the lmstat command (in license manager directory).
Shutdown warning can then be batch-sent with the net send command.

- Éric