BDI's Education Analytics Platform

SAP Business Objects BI provides insight into your system by recording web activity and allowing you to inspect and to monitor the details. The configuration dialogue for Auditing allows you to select the server or servers that you want to audit and the relevant attributes - such as time, date, IP address, port number, and so on - that you want to record. The auditing data is logged to disk and stored in comma-delimited text files, so you can easily report off the data or import it into other applications.

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 audited 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. 

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. You can audit the events of individual users of SAP BusinessObjects BI 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.

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 audited 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. 

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 audited 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. 

News & Events