Describing the Central Management Server (CMS) System Database For Auditing

Objective

After completing this lesson, you will be able to examine the Central Management Server (CMS) system database for auditing.

Role of Auditing

Auditor and Auditees

The Central Management Server (CMS) is used for auditing events sent by users, applications or servers. An auditor server and some auditee servers are used for auditing client (web client and rich-client) on SAP BusinessObjects BI Platform 2025.

Definition:
The Central Management Server (CMS) acts as the auditor to track SAP BusinessObjects BI Platform 2025 interactions.
  • The auditable events are stored in the Auditing Data Store (ADS).
  • All auditing events time stamp is controlled by the Central Management Server (CMS).
Auditing Clients:
Beside the server auditing, the following clients can also be audited by the Central Management Server (CMS):
  • Web Intelligence Rich Client
  • BI Launch Pad
  • Central Management Console (CMC)

Auditing Data Store (ADS)

Auditing in CMC

Administrators have a dedicated Auditing page in Central Management Console (CMC).

In the Auditing page of Central Management Console (CMC), administrators can also see some status summary metrics on SAP BusinessObjects BI Platform 2025.

Auditing Page:
The Auditing page in Central Management Console (CMC) is a powerful tool for administrators to manage, monitor, and analyze auditable events stored in the Audit Data Store (ADS).

Four areas are available in this Auditing page:

  • Summary
  • Set Events
  • Set Event Details
  • Configuration
Status Summary Metrics:
  • The Auditing Status Summary shows a set of metrics that help you optimize your auditing configuration and alert you to any issues that might affect the integrity of your auditing data.
  • The summary will also display warnings under the following circumstances:
    • The connection to the Auditing Data Store (ADS) database is unavailable.
    • There is no running or enabled Client Auditing Proxy Service, which prevents client events from being collected.
    • An auditee has events that could not be retrieved (the server or servers affected will be identified). This usually indicates a server was not properly stopped or shut down and still has events in the temporary files.
  • The status summary is at the top of the Auditing page in the Central Management Console.

    Note

    The status summary metrics are marked green, yellow, or red to indicate the health of the auditing feature.
The following link explains the auditing status metrics: (Auditing Status Metrics).

In the Auditing page of Central Management Console (CMC), administrators can select events to be audited on SAP BusinessObjects BI Platform 2025.

Set Events:
  • The CMC Auditing page can be used to activate auditing and select which events will be audited across your entire system.
  • If you are not interested in certain events or event details, you can leave them unselected to gain additional system performance.
  • To configure the auditing events, set the Set Events slider to the desired auditing level, where each auditing level corresponds to a specific metric value (Off, Minimal, Default, Complete, Custom).

    Note

    For Custom, you can select events for customizing your choice.
The following link explains how to configure audit events: (Configure Audit Events).

In the Auditing page of Central Management Console (CMC), administrators can select optional events details to be audited on SAP BusinessObjects BI Platform 2025.

Set Events Details:
  • Optionally, you can select optional details under Set Event Details.
  • With the events, you will record fewer details that increases system performance like Query, Folder Path Details, Rights Details, User Group Details and Property Value Details.
The following link explains how to configure audit events: (Enhanced Event Detail Recording in Audit Detail Table).

In the Auditing page of Central Management Console (CMC), administrators can see and update the Auditing Data Store (ADS) database connection on SAP BusinessObjects BI Platform 2025.

Configuration:
  • The CMC Auditing page displays in this area all technical information of the Auditing Data Store database (ADS).
  • It is possible to change any connection setting to ADS (for instance, you want to use another ADS database).

    Note

    Any change in this area will need to restart the Central Management Server (CMS) to be taken in account.
  • The Delete Events Older Than (Days) field specifies the number of days you want information to remain in the database (minimum value: 1, maximum value: 109200).

    Note

    Data older than the number of days set here will be permanently deleted from the ADS; it cannot be recovered. You may want to consider periodically moving records to an archive database if you want to maintain long-term records.
The following link explains how to configure your Auditing Data Store database settings: (To configure your Auditing Data Store database settings).
Auditing Page

Process Flows for Auditing

Watch this video to learn about the workflows used for auditing.

Installing and Using Auditing

In this exercise, you will deploy and use auditing objects.

Summary

  • CMS acts as the auditor, tracking and storing BI platform interactions in the Auditing Data Store (ADS) with controlled timestamps.
  • Specific clients support auditing, including Web Intelligence Rich Client, BI Launch Pad, and CMC.
  • CMC Auditing page allows administrators to manage, monitor, and analyze auditable events stored in the ADS.
  • Auditing process flows vary depending on the type of auditee, with different workflows for server auditing and non-logon auditing for clients connecting through HTTP.
  • Auditing Status Summary metrics indicate the health of the auditing configuration.