Show TOC

 Audit Log ServiceLocate this document in the navigation structure

Use

The audit log service stores events that were triggered in selected repositories in a log file.

 

Features

The events are written to the applications.log log file in the Application Server Java (AS Java). The log file is located at .../j2ee/cluster/server<n>/log/.

 

The service writes entries to the log file for the following events:

 

CREATE <object> by <user>

CREATE FOLDER <folder> by <user>

CREATE LINK from <object> to <target> by <user>

COPY <object> to <object> by <user>

MOVE <object> to <object> by <user>

RENAME <object> to <name> by <user>

UPDATE <object> by <user>

UPDATE LINK <object> to <target> by <user>

DELETE <object> by <user>

 

The syntax for <object> and <target> is as follows:

<object>=<folder>+<name>

<target>=<object>|<folder>|<ext. name>

 

You can specify the following parameters in the configuration of the service:

Audit Log Service Parameters

Parameter Required Description

Positive List

No

If this parameter is activated, the selected repositories are taken into account by the audit log service.

If this parameter is deactivated, the list of specified repositories is seen as a list of repositories to exclude, and only repositories that are not specified are taken into account.

Repositories

No

Specifies the repositories that are taken into account by the audit log service.

The effect of this entry depends on the value of the Positive List parameter.

If no selection is made, the system takes all repositories into account.

Note that audit logging does not make sense for the /etc repository.

 

Note

You cannot configure the level of detail. Program-internally, the system writes the log automatically using the INFO level of detail.

 

Activities

In the standard delivery, the audit log service is deactivated.

To activate and configure the audit log service, choose Content Management → Global Services → Audit Log Service.