Enabling, Validating and Disabling Audit Trail

BaseSpace Clarity LIMS provides Audit Trail, a robust data-tracking system that allows you track:

• All user activity - i.e. who did what and when.

• Every action that is written to the database.

Audit Trail has two capture systems, Event Log and Detail Log.

• Event Log records familiar BaseSpace Clarity LIMS user actions, and presents this information in a format that is easy to read and understand.

• Detail Log records exacting information about the changes resulting from the actions recorded in the Event Log. This includes both the updated values and the previous values.

Enabling Audit Trail

All of the following steps are performed on the BaseSpace Clarity LIMS server.

With the exception of steps 1 and 8, all are performed as the glsjboss user.

1. Stop Tomcat - as the glsjboss user:

2. Access the property tool:

3. Enable Audit Trail:

Validating Audit Trail

1. Log in to BaseSpace Clarity LIMS and make a change – for example, add a project, create a sample, add a custom field, etc. The exact change is not important. There must simply be a change to the activity or the configuration data since Audit Trail was last enabled.

2. Use psql (postgres) or SQL*Plus (Oracle) to query the main BaseSpace Clarity LIMS database (clarityDB) to verify whether rows are being written to the following two tables:

   • auditeventlog

Disabling Audit Trail

All of the following steps are performed on the BaseSpace Clarity LIMS server.

With the exception of steps 1 and 8, all are performed as the glsjboss user.

1. Stop Tomcat - as the glsjboss user:

2. Access the property tool:

3. Disable Audit Trail: