BusinessObjects Enterprise Auditor provides you with a way to monitor and record key facts about your BusinessObjects Enterprise deployment.
The information provided by the auditor answers the following queries
- Who is using your Business Objects Enterprise system?
- Which objects they are accessing?
- Which groups within the company use our BusinessObjects Enterprise system the most?
- How many concurrent user licenses are we using at any given time?
Auditor also allows you to better administer individual user accounts and reports by giving you more insight into what actions users are taking and which reports they are accessing.
Configuring Auditor in Windows
Once you configured the CMS Repository then the next step is to configure the Auditing database.
The audit database can be configured in the same CMS Repository. The Repository will have the following tables gets created in the Database.
- CMS_Aliases6
- CMS_IDNumbers6
- CMS_InfoObjects6
- CMS_Locks6
- CMS_Relations6
- CMS_VersionInfo
Auditing Tables
- Audit_Event
- Audit_Detail
- Server_Process
- Detail_Type table
- Event_Type
- Application_Type
Configure Auditing in UNIX Platform
- Run the script CCM.SH to stop the CMS
- Run CMSDBSETUP.SH
- Choose the “SELECTAUDITOPTION” and then supply the requested information about the database server (Ex: Oracle, SQLServer or MYSQL) where you want to configure the Audit DB.
- Run SERVERCONFIG.SH
- Choose the “MODIFY A SERVER” Option
- Select the CMS and Enable Auditing. Enter the port number of the CMS when prompted (You can use the default port 6400)
- Use CCM.SH to start the CMS, when the CMS Starts then it will create the auditing database in the given DB Server.
- In a CMS cluster, the cluster will nominate one CMS to act as system auditor. If the machine that is running this CMS fails, another CMS from the cluster will take over and begin acting as auditor.
Auditing Database Schema
BusinessObjects Enterprise Auditor provides you with a way to monitor and record key facts about your BusinessObjects Enterprise deployment.
Auditing Tables
The Audit database contains Six tables:-
- Audit_Event
- Audit_Detail
- Server_Process
- Detail_Type table
- Event_Type
- Application_Type
Audit_Event:-
The Audit_Event table stores one record per action that is audited and
Contains general information about each audit event
Audit_Detail:-
The Audit_Detail table records more details about each audit action recorded in the Audit_Event table. For example, when a user logon fails, the reasons for that failure are recorded as audit details. There may be more than one record in this table for each audit action
recorded in the Audit_Event table.
Server_Process:-
The Server_Process table contains information about the servers running within your BusinessObjects Enterprise system which can generate audit events.
Event_Type:-
The Event_Type table contains a static list of the kinds of events that can be audited in your BusinessObjects Enterprise system. This table provides information roughly equivalent to that provided by AuditIDs and AuditStrings in Crystal Enterprise
Application_Type:-
The Application_Type table contains a static list of the applications that can produce audit events. In BusinessObjects Enterprise XI, the applications that can be audited are servers.
Detail_Type table:-
The Detail_Type table contains a static list of the standard details that can be recorded about audited events. For example, a user logon can fail for a number of different reasons. These reasons are listed as entries in the
Once the tables are created, we need to enable the auditing features through Central Management Console.
Logon to CMC->Go to Server->Click CMS
Select the Audit events for the CMS Server.
Build the sample universe based on the auditing database
Sample reports created to track the users.
