Business Objects XI R3.1 Auditing


How Business Objects XI R3.1 Auditing works.


Before using Auditing in Business Objects   you need to know how to configure the auditing database, how to select actions to audit, and eventually how to create a custom auditing report.

Auditing allows you to keep a record of significant events on BusinessObjects Enterprise servers.

Auditor refers to any system responsible for recording or storing information on any auditable event. Auditee refers to any system responsible for performing an event that is audited.


While the audit database can exist as part of the system database, it is recommended that it be kept separate, to minimize the impact on system performance due to the constantly growing size of the database.

As the auditor, the CMS is responsible for collecting events and writing them to the auditing database. When an audited event is triggered, the server responsible will generate a record and store it in a local temporary file. At regular intervals the CMS communicates with the auditee servers to request
copies of records from their local temporary files. When the CMS receives these records, it writes the data to the auditing database.


There is always a delay between the time an event occurs and its final transfer
to the Auditor database. While this delay is configurable, any of the following
conditions may increase the delay beyond the configured limit.
• Unavailability of the CMS or auditing database.
• Loss of network connectivity.
• An auditee has generated more events then the CMS-Auditor is configured to retrieve in a single batch. See the links at the bottom of this page for instructions on increasing batch size.


Once the data is in the auditing database, you can run the auditing reports against the database or design custom reports to suit your business needs.



Configuring auditing

If you set up auditing when you installed BusinessObjects Enterprise, your auditing database is already configured and has established a connection with the Central Management Server (CMS). If you did not set up auditing when you installed, you must configure all your Server Intelligence Agent
(SIA) to connect to an auditing database.


To be able to audit an event in BusinessObjects Enterprise, you will need to configure the following components:
• Determine which server controls the event
• You must enable auditing of that action in the Servers management area of the Central Management Console (CMC).
• If it is a client-generated event, you must also enable auditing from the Applications area of the CMC.
As the auditee, the BusinessObjects Enterprise server will then begin to trigger these auditing events in a local log file.

Events that can be audited



You can audit the events of individual users of BusinessObjects Enterprise as they log in and out of the system, access data, or create file-based events.
You can also monitor system events like the success or failure of scheduled objects. For each event, BusinessObjects Enterprise records the time of the event, the name and user group of the user who initiated the event, the server where it was performed.


Ahead you will read which server-based events can be audited and which server can be used to activate them:

Objects (Category)


Events:


Object Created
Objects
Object Deleted
Object Modified
Object Rights Modified
Unresponsive Scheduling


Category Event Enterprise Service: CMS


BusinessObjects Enterprise Server: CMS

Crystal reports (Category)

Events:
Report Viewing Succeeded
Report Viewing Failed

Crystal Reports Cache Service

Crystal Reports Cache Server

Events:
Scheduling Succeeded
Scheduling Failed
Scheduling Failed But Will Be Reattempted
Destination Delivery Succeeded
Destination delivery Failed

Destination Job Server

Destination Job Service


Web Intelligence (Category)

Events:
Document Retrieved
• A user has saved a Web Intelligence document within BusinessObjects Enterprise.
Universe Selected
• A user has selected a universe as they create a new Web Intelligence document, or as they edit
an existing Web Intelligence document.
Document Refreshed
• User manually refreshes a Web Intelligence document, or opens a Web Intelligence document that
is set to "refresh on open", or schedules a Web Intelligence document.
List Of Values Retrieved
• A list of values is retrieved from the database to populate a picklist associated with a prompt used
to filter the data in a document.
Document Edited
• User enters "Edit document" mode for an existing Web Intelligence document.
Format Applied
• User applies a formatting change to an existing Web Intelligence document in a query panel.
SQL Generated
• This is triggered when a new Web Intelligence document is created.
It then builds an SQL query for the document, but it its not submitted to the database.
Drilled out of scope
• User drills past the scope of the data currently in memory, and triggers a call to the database for
more data. 
Prompt Selected
• User enters or selects a value for a report prompt.
Document Saved
• User opens an existing Web Intelligence document.

Web Intelligence Cache Service

Web Intelligence Cache Server


Web Intelligence scheduling and publishing (Category)

Events:
Scheduling Succeeded
Scheduling Failed
Scheduling Failed But Will Be Reattempted
Destination Delivery Succeeded
Destination Delivery Failed

Publishing Service
Adaptive Job Server 

Desktop Intelligence scheduling and delivery (Category)


Events:
Scheduling Succeeded
Scheduling Failed
Scheduling Failed But Will Be Reattempted
Destination Delivery Succeeded
Destination Delivery Failed
Document Retrieved
• User opens an existing Desktop Intelligence document.
Document Refreshed
• User manually refreshes a Desktop Intelligence document, or opens a Desktop Intelligence
document that is set to "refresh on open", or schedules a Desktop Intelligence document.
Prompt Selected
• User enters or selects a value for a report prompt.


Desktop Intelligence Job Service
Desktop Intelligence Job Server

Desktop Intelligence documents (Category)

Events:
Document Retrieved
• User opens an existing Desktop Intelligence document.
Document Refreshed
• User manually refreshes a Desktop Intelligence document, or opens a Desktop Intelligence
document that is set to "refresh on open", or schedules a Desktop Intelligence document.
List of values Retrieved
• A list of values is retrieved from the database to populate a picklist associated with a prompt used to filter the data in a document.
Page Retrieved
• Server renders the pages of a Desktop Intelligence document in response to a user request to
display all or part of a document.
Prompt Selected
• User enters or selects a value for a report prompt.

Desktop Intelligence Cache Service
Desktop Intelligence Cache Server

Publication Scheduling (Category)

Events:
A job has been:
• successfully scheduled
• unsuccessfully scheduled
• unsuccessfully scheduled but will be reattempted

Publishing Job service
Publishing Job Server

Access levels (Category)

Events:
An access level has been created
Custom access level modified
An access level has been deleted

CMS 
CMS

Users (Category)

Events:
Concurrent Logon
Named User Logon
User Logon Failed
Password Changed
User Logoff

CMS 
CMS

Send an object to destination (Category)

Events:
Destination Delivery Succeeded
(A user has successfully sent an object to a destination)
Destination Delivery Failed
(An object has failed to be sent to a destination)
Scheduling Failed But Will Be Reattempted

Destination Job Service
Destination Job Server

File-based events (Category)

Events:

File Event Registered
• Event is created, and registered with system File Event Updated
• The name, description, or filename of an event is modified File Event Unregistered
• Event is removed from system File Event Triggered
• An event is triggered within the system

Event Service
Event Server

Default auditing reports 

User activities for session report


Modifiying and update activies report


Most frequent Activities in the year report

Most required reports in the year 


Top 10  updated reports 


Auditing Action  report



See also

BO XI R3.1 Auditing DeskI Reports

BusinessObjects Auditor - Structure and tables

Business Objects Query builder

Query Builder:queries for extract reports refreshed after o before a specific date



Comments

Post a Comment

Popular posts from this blog

SAP HANA Introduction

Image
SAP HANA:The future of database technology The capacity of main memory in servers has continuously increased over the years, whereas prices have dramatically dropped. Today, a single enterprise class server can hold several  terabytes of main memory. At the same time, prices for server main memory dramatically  dropped over the last few decades. This increase in capacity and reduction in cost makes it a  viable approach to keep huge amounts of business data in memory. This section discusses  the benefits and challenges. In few words you can understand SAP HANA plus  analyzing this evaluation: Typical access speeds Disk     4,000,000 ns Memory         0.4 ns Speed   10,000,000 Falling prices move processing from Disk/SSD to In-Memory In-Memory Computing The elements of In-Memory computing are not new. However, dramatically improved hardware economics and  technology innov...
Read more

SAP Dashboard Error - Cannot find the BusinessObjects Enterprise report source. (LO 26608)

<!-- Google tag (gtag.js) --> <script async src="https://www.googletagmanager.com/gtag/js?id=G-NL0CYP13VZ"></script> <script>   window.dataLayer = window.dataLayer || [];   function gtag(){dataLayer.push(arguments);}   gtag('js', new Date());   gtag('config', 'G-NL0CYP13VZ'); </script> Cannot find the BusinessObjects Enterprise report source. (LO 26608) Environment SAP BO XI 4.1 SP 5 two nodes Cluster Windows Server 2012 While refreshing dashboard (based on Live Office connection) from BI Launchpad with a no administrator user the above exception was erased. SAP says: Cause The document is not available; for example it does not exist, or it has been removed. Action Check the report path from CMS and use SetLocation in Live Office to re-define the report source. Otherwise, check if the user has sufficient rights to view the object. Solution In our case  we fixed this problem was to remo...
Read more

FWM 01002 - Unable to reconnect to the CMS. The session has been logged off or has expired.

An error has occurred: Unable to reconnect to the CMS.  The session has been logged off or has expired. (FWM 01002) Environment BO XI R 3.1 SP 4 In order to solve this issue we found a  SAP released note 1422296  1422296 - Error:' Unable to reconnect to CMS :6400. The session has been logged off or has expired.(FWM 01002)' with BusinessObjects XI 3.1. Symptom Not able to schedule WebIntelligence reports. Reports fail with error:'Unable to reconnect to CMS :6400. The session has been logged off or has expired.(FWM 01002)' Environment BusinessObjects XI 3.1. Reproducing the Issue Schedule a WebIntelligence report to run now. Reports fails with error:u2018Unable to reconnect to CMS :6400. The session has been logged off or has expired.(FWM 01002)' Resolution 1. From Central Configuration Manager, disable all the services and re-enable them. 2. Log into Central Management Console and go to the server area. 3. Go to the properties of Central Man...
Read more