Welcome to Telelogic Product Support
  Home Downloads Knowledgebase Case Tracking Licensing Help Telelogic Passport
Telelogic DOORS (steve huntington)
Decrease font size
Increase font size
Topic Title: Login/Logout DXL
Topic Summary:
Created On: 5-Apr-2004 17:32
Status: Post and Reply
Linear : Threading : Single : Branch
Search Topic Search Topic
Topic Tools Topic Tools
Quick Reply Quick Reply
Subscribe to this topic Subscribe to this topic
E-mail this topic to someone. E-mail this topic
Bookmark this topic Bookmark this topic
View similar topics View similar topics
View topic in raw text format. Print this topic.
 5-Apr-2004 17:32
User is offline View Users Profile Print this message


Louie Landale

Posts: 2070
Joined: 12-Sep-2002

I need to run some DXL in the background when users login and logout. There are no login/logout triggers. I know I can edit the "startup.dxl" and "finish.dxl" files on everyone's client machines and add a call to a network *.dxl file that will do the job, but I don't want to have to updated everyone's clients and besides I want to prevent them from suppressing the call.

Can I force Login/Logout DXL to run somehow? Perhaps the license server can be patched to do this job? Can the server be patched to take notice? I know DOORS keeps a log of login attempts; perhaps THAT code can be modified?

- Louie
Report this to a Moderator Report this to a Moderator
 13-Apr-2004 02:34
User is offline View Users Profile Print this message


Paul Miller

Posts: 376
Joined: 2-Oct-2002

Hi Louie,

If you installed a FLEXLm license server from the DOORS installation media, FLEXLm is pre-configured to dump license check-in and check-out data into a debug text file called Telelogicflex.log. If this is not the case, run the file "lmtools.exe" (should be co-located with the other FLEXlm server app files), select the "config sevices" tab, the debug log file being used by FLEXLm is identified within this tab.

If you're into PERL scripting, you could schedule a PERL script to interrogate this text file and extract the check-in and check-out data. You'll need to use some fairly fierce Regular Expresions to filter out the "noise" that is dumped into this log file and be aware that this file is purged whenever the FLEXLm server is restarted for any reason.

I do something similar for collecting usage statistics on Telelogic Tools.



-------------------------
Paul Miller
Specification Practices Specialist,
EuroCyber,
Melbourne, Australia.
Mobile: +61 (0)418 135 103
Web Site: http://www.eurocyber.biz
E-mail: miller@eurocyber.biz">pmiller@eurocyber.biz
Report this to a Moderator Report this to a Moderator
 16-Apr-2004 11:09
User is offline View Users Profile Print this message


Ross Morgan

Posts: 74
Joined: 15-Apr-2004

The DOORS database server does not currently serve DXL. This would make deployment of customisations much easier.

a possible alternative is to use a trigger to run some dxl which runs or installs the dxl that you want

here is some code which installs a trigger in a module...

string sTrigDXL = probeAttr_(current Module,"trigDXL")
Trigger t = trigger("installonread",module,post,open,10,sTrigDXL)

"trigDXL" is a text attribute on the module which contains the DXL that I want to run. The first line of this DXL is
if(isRead(current Module)){
so that it only runs if the module is opened read-only.

To run the DXL you request users to open the module in read-only mode. (you can define the permissions on the module so that is all they can do)

here is some code to remove the trigger...
Trigger t
for t in (current Module) do
{
delete(t)
}

The problem with this is that the user must still open the specific module to run the DXL.
You can solve this by defining a trigger at the database level which fires when any formal module is opened.
i.e project->all->module->formal->all
there will be a performance hit though.

To make this run DXL on login and logout the trigger DXL will need to install startup and finish DXL.

Ross.
Report this to a Moderator Report this to a Moderator
 16-Apr-2004 16:52
User is offline View Users Profile Print this message


Louie Landale

Posts: 2070
Joined: 12-Sep-2002

Yup, deployed a database wide trigger that fires when the user opens any module. They need a login/logout Trigger events. Using Config Files the trigger is clever enough to stop if he has been run recently.

You don't need to put your DXL in some attribute. Preceed all back slashes and quotes with a back-slash. If you want to execute:
ack("Hello.\nFrom the Administrator")
you can put:
string sTrigDXL = "ack(\"Hello.\\nFrom the Adminstrator\")" in the DXL that defines the trigger.

My define-the-trigger code all have the optio to first remove the trigger, and then option to install it. The "delete(trig ...)" paramaters need to be the same as the "create" parameters. I've got other code that reports on triggers, and another that offers to remove triggers.

- Louie
Report this to a Moderator Report this to a Moderator
Statistics
20925 users are registered to the Telelogic DOORS forum.
There are currently 0 users logged in.
The most users ever online was 15 on 15-Jan-2009 at 16:36.
There are currently 0 guests browsing this forum, which makes a total of 0 users using this forum.
You have posted 0 messages to this forum. 0 overall.

FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.