[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference utrop1::linkworks_v3

Title:LinkWorks V3.0 Notes Conference
Notice:LNX_APO = APO issues, LINKWORKS_V3 = V3.0 issues
Moderator:tacklr.apd.dec.com::TACK_Lm::TACK_L
Created:Tue Jun 28 1994
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:2269
Total number of notes:8338

2204.0. "Help on Event Tracking" by TROOA::QIAN () Tue Apr 22 1997 00:44

    	In our VB appliction, users can create Account objects which are
    compound object classes(something like "Folder"). Users can also
    modify the attributes of these objects.
    
    	We want to set up our special event tracking to record all the
    actions that users have done (via VB program)for every Account object, 
    and write down the records into a UNIX log file in the LinkWorks Server. 
    So at any time the customer can access the log file to know what has 
    happened for Account objects. Every Account Object has its own Event Log 
    File. The format of this log file is like the follows:
    
    ----Start log
    #This file is an event tracking file 
    #The file name can be ObjectName-CreateDate.log
    #The record is write down in this format: 
    #     What-happen  When    Who
    #This file must start with the "Create" event and finish with "Delete"
    #event
    Create Object               04/21/1997 17:38    Cecilia Qian
    Read Attributes:AccountNo       04/21/1997 18:40    Tom Smith
    Edit Attributes:CustomerName:"ABC Company" 04/21/1997  Peper Mina
    
    ...
    
    Delete Object          06/06/1997  9:30     Business Administrator
    ---End
    
                                                           
    	By the way, our LinkWorks Server is Digital UNIX 3.2C, LinkWorks
    3.0.8 and Oracle 7.1.6.
    
    	Any comments and advices are warmly welcome.
    
    Cecilia
    
     
    
     
T.RTitleUserPersonal
Name
DateLines
2204.1elec1.uto.dec.com::wijermars_vTue Apr 22 1997 17:4611
Hi,

You could use the audit method.
For every method you want auditing on you could override the method to call the original method 
and the audit method.
If you are not happy with the audit method, you could implement thios functionality yourselves by 
calling an external method on the server (using a shared library call[mext_dll]).
The sharedf library would have to support a nummer of calls like createlog, updatelog etc.
You could pass all kind of info to this logging utility such as attributes,user etc.

Vincent 
2204.2elec1.uto.dec.com::wijermars_vTue Apr 22 1997 17:486
BTW,

In Linkworks 3.2 auditing can be configured to a certain degree, like audit all unsuccessfull 
edits and all successfull updates of attributes.

Vincent
2204.3Thanks, and examples neededTROOA::QIANWed Apr 23 1997 21:3711
    Hi Vincent,
    
    	Thanks a lot for your reply. 
    
    	I'm more interested in the second way you mentioned in your first
    reply(2204.1).  But I don't know how to build up an shared library and
    an external method on the server(Digital UNIX), and how to write/update the
    record to a UNIX file. Would you please provide me some step-by-step 
    examples to do this?  
    
    Cecilia