SAP BusinessObjects 4.0 Auditor Configuration & Deployment End to End
This is one of the frequently asked question in our forum and most of the steps are already there in our forum. Since I got a chance to work with this, am sharing the step by step configuration of Audit reports with screen captures.
BusinessObjects Enterprise Auditor provides you with a way to monitor and record key facts about your deployment. 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. 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?
And below are some of the auditable actions
- Track when Objects are created, deleted of modified
- Track when reports are opened, saved, refreshed, created, modified and deleted
- Job monitoring and failure
In SAP BusinessObjects 4.0 auditing database schema was changed, improved. SAP BusinessObjects Business Intelligence 4.0 does not include auditing sample Universe and auditing sample reports with the installation.
Configuration in CMC
To configure Audit database in BI 4.0, you need to follow the steps below
- Login to CMC and click on Auditing from Manage.
- In the ADS database configuration select type of the database.
- Provide the credentials of the database and click on save.
4. You need to restart the Central management server (CMS) hence log off from CMC.
5. Open Central configuration manager (CCM) and restart the Server Intelligence Agent.
6. Wait for some time so that all the servers will come up because the Adaptive processing server should be running completely to enable auditing.
Auditor deployment package and contents
Compared to previous versions of BusinessObjects, Installation package will not come with a default Audit universe and reports. But SAP comes up with as- is sample to help administrators and report designers to develop custom auditing reports. This would be a starting point of the development of custom auditing universe and reports as per the requirement. Please refer http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/40711187-04e8-2d10-d190-851e20c7665a to know more.
The Audit Sample package contains:
a) Seven sample auditing .UNX universes one for each of the following database types:
b) Thirty-eight sample Crystal Reports referencing the universe.
Deployment and configuration of Audit Universe
To deploy Auditing universe please follow the steps:
- In SAP BusinessObjects 4.0 Information Design Tool create a new project and retrieve the sample auditing universe into it. This will result in a 3 objects appearing in your project: a connection, (.cnx or .cns), a data layer, (.dfx), and a business layer (.blx)
2. In Information Design Tool create a connection (.cnx or .cns) to your auditing data store (for SAP Business Objects 4.0. Then change the connection of the dfx to use the one you have created.
3. In Information Design Tool check integrity of the universe before re-publishing. Please ignore all cardinality and unlinked table warnings.
4. In Information Design Tool publish the modified universe to your SAP BusinessObjects Enterprise system. If you are using a .cnx, you will be prompted to create and switch to a secure, published .cns connection. You can publish your .cnx connection to your SAP BusinessObjects Enterprise repository to generate a secured .cns.
Deployment and configuration of Audit Reports
- In Crystal Reports Design for 4.0 open the sample auditing reports
2. Click the ‘Data’ menu and ‘Set Data Source Location’ to point the report to the auditing universe published in the previous step.
3. Publish the sample reports to the SAP Business Objects Enterprise
Audit reports are deployed in your BusinessObjects environment. You can now start using the deployed reports.
Hope this is interesting and useful. We will see BusinessObjects Monitoring in my next few blogs.
Related references :