This is documentation of an archived release.
For documentation on the current version, please check Knowledge Base.
For documentation on the current version, please check Knowledge Base.
Logging User Logins and Resource Behaviour
In EOS, there is a possibility to log the behaviour of users and resources. For every user login/logout and every action on a resource, a record is stored in an Access-database.
The database-size can grow fast. Follow up the logdatabase and clean the tables from time to time.
Enabling the logging
To enable the logging, you can do the following:
- Download an empty logdatabase: logging.zip
- Put the database by example in the folder ..\server\program\log of your installation.
- Make an ODBC-connection with the following characteristics:
(Control Panel → Administrative Tools → Data Sources (ODBC))- Driver: Microsoft Access Driver (*.mdb)
- Data Source Name: logdatabase
- Database: ..\server\program\log\logging.mdb
- Make a JDBC-connection with the following characteristics:
(..\server\program\bin\JDSA.exe)- Name: logdatabase
- Driver: ODBC
- Database: logdatabase
Don't forget to generate the URL by clicking the arrow down.
- Open the file ..\server\program\config\eos.ini. The first three lines of this file are:
OrbitServer= Version=3 AdministratorGroup= ...
- Add a few lines so that these are the first lines of the file:
OrbitServer= Version=3 LoginLogConfiguration= Enabled=true DataSourceName=logdatabase TableName=logins AccessLogConfiguration= Enabled=true DataSourceName=logdatabase TableName=datasets DataSetMasks=*multi*,*cadmap* AdministratorGroup= ...
- Enabled: you can enable the logging of user login/logout (LoginLogConfiguration) and/or the logging of resource behaviour (AccessLogConfiguration) by adjusting this parameter to 'true'. To disable the logging, adjust this parameter to 'false'.
- DataSourceName: name of the JDBC-connection (logdatabase, see 4)
- TableName: name of the table in the database logging.mdb. This is 'logins' for the logging of user login/logout (LoginLogConfiguration) and 'datasets' for the logging of resource behaviour (AccessLogConfiguration).
- DataSetMasks: here you can list de Registry Names of the resources that need to be logged. You can separate the resources with a ','. It is also possible to use the wildcard '*'. By typing *multi*, every resource with the word 'multi' in his Registy Name will be logged. By typing only the wildcard, every resource will be logged.
Structure of the logdatabase
Table logins
- Loginidentifier: a unique identifier for every new login
- When: data and time of login/logout
- Description: indicates whether the user is logging in or logging out
- Usergroupname: the EOS-usergroup from which the user is part of
- Username: the EOS-user who is logging in or logging out
- Localhostadress: the IP adress of the PC from where the user is logging in or logging out
- Localhostname: the name of the PC from where the user is logging in or logging out
- Localusername: the loginname of the user on the PC from where he is logging in or logging out
Table datasets
- Datasetname: Registry Name of the resource which is logged
- When: data and time of the action on the resource
- Usergroupname: the EOS-usergroup from which the user who is taking the action, is part of
- Username: the EOS-user who is taking the action
- Loginidentifier: the unique identifier of the EOS-user who is taking the action
- Description: description of the executed action on the logged resource
Last modified:: 2019/03/25 11:36