1 / 30

SAP BO Business Intelligence Platform 4.0 Auditing Auditing in BI 4.0

SAP BO Business Intelligence Platform 4.0 Auditing Auditing in BI 4.0. Confidential. Lesson Objectives. After completing this lesson, you will be able to: Describe what auditing is Describe how to configure and troubleshoot auditing Describe the purpose and benefits of auditing dashboard

leander-thady
Télécharger la présentation

SAP BO Business Intelligence Platform 4.0 Auditing Auditing in BI 4.0

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. SAP BO Business Intelligence Platform 4.0 AuditingAuditing in BI 4.0 Confidential

  2. Lesson Objectives After completing this lesson, you will be able to: • Describe what auditing is • Describe how to configure and troubleshoot auditing • Describe the purpose and benefits of auditing dashboard • Explain the meaning and structure of new auditing events • Describe the ADS schema • Describe how auditing events are stored in ADS

  3. Agenda What is Auditing? Auditing Dashboard Auditing Data Store Consistent Auditing Events

  4. What is Auditing? • Auditing subsystem keeps a record of events from SAP BusinessObjects Business Intelligence (BI) platform servers and applications. • How, what and when? • Recorded in Auditing Data Store (ADS). • Once the data is in the ADS, you can report on operations performed in system.

  5. Agenda What is Auditing? Auditing Dashboard Auditing Data Store Consistent Auditing Events

  6. Auditing Install in 4.0 • Special license keys not required in 4.0 • For performance reasons it is recommended to have auditing DB separate from Central Management Server (CMS) DB • After install, auditing is preconfigured, enabled and running • Option to not configure auditing disables auditing and hence no auditing events are fired • Silent install provides no auditing command line parameter

  7. Auditing Dashboard

  8. Auditing Dashboard: Status Summary SectionOverview • The Auditing Status Summary section is a new feature • Metrics to optimize auditing configuration • Alerts of potential issues with auditing • 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 (CAPS) • An Auditee has events that could not be retrieved

  9. Auditing Dashboard: Status Summary SectionMetrics • CMS collects events from all auditees once every 3 minutes. • CMS automatically adjusts polling cycle duration. • Manual configuration of polling cycle duration is not possible.

  10. Auditing Dashboard: Status Summary Section

  11. Auditing Dashboard: Configuring Auditing Events and Event Details • “Auditing Level” slider in “Set Events” to chose the level of auditing • “Custom” level to select individual auditing events. • Changes to auditing events and event details apply to all servers and applications. • You can enable and disable some event details. • Query • Folder Group Details • Rights Details • User Group Details • Property Value Details Note: For client auditing it may take up to two minutes after the changes have been made before the system will start recording data for any new events. Make sure you allow for this delay when implementing changes to the system.

  12. Auditing Dashboard

  13. Auditing Dashboard : Configuring ADS Database • If Auditing is enabled and ADS database not configured, audit events accumulate. • CMS must be restarted for changes in ADS database configuration to take place. • Multiple clusters can write events to the same ADS • Auto-delete: Delete events older than (days) • ADS Auto Reconnect – CMS automatically reconnects to ADS when connection is lost.

  14. Summary of Audit Configuration in CMC All auditing configuration is done in CMC, no more in CCM. • You can configure: • In CMC > Servers > Nodes > Placeholders • The location of temporary auditing files • In CMC > Audit (Audit Dashboard) • Auditing levels and events details • Audit ADS database • No user configurable settings for: • Auditing polling interval duration • Which events are retrieved • AuditInterval and AuditMaxEventsPerFile command line CMS parameters no longer supported.

  15. Agenda What is Auditing? Auditing Dashboard Auditing Data Store Consistent Auditing Events

  16. Migration • New auditing events and Auditing Data Store (ADS) schema are not compatible with SAP BusinessObjects Enterprise XI 3.1 auditing database. • No migration of auditing data between releases. • Event structure and information collected has changed. • Audit events have more information in 4.0. • Consistency of event data. • No out of the box sample auditing universe and reports.

  17. ADS: schema

  18. ADS: ADS_EVENT • Key tables are ADS_EVENT and ADS_EVENT_DETAIL • ADS_EVENT contain all event properties for each event (one row per event), and includes: • Event ID • Origin: • Cluster_ID • Server_ID • Service_Type_ID • Client_Type_ID • Time (when event took place): • Start_Time (in GMT) • Duration_ms • Time_Added_To_ADS • User (who caused auditable operation) • User ID • User Name • Session ID • Event type (which operation) • Event_Type_ID • Status ID • Action ID • Object Properties(on which resource the operation is performed) • Object_ID • Object_Name • Object_Type • Folder_Path • Folder ID • Top_Folder_Name • Top_Folder _ID

  19. Agenda What is Auditing? Auditing Dashboard Auditing Data Store Consistent Auditing Events

  20. Auditing Transversal Consistency • Auditing events are now transversally consistent. • There are two types of events: • Common • Specific

  21. Auditing Common Events

  22. Auditing Common Events (cont.) -Doesn’t apply. No auditing events is triggered by the component. -Auditing event is triggered by the component. -The component relies on CMS event with the same name. No auditing event is triggered by the component. -The “Save” results in CMS firing Create or Modify events. No auditing event is triggered by the component. S -The component relies on Search Service event. No auditing event is triggered by the component -The event generated by Live Office Web Services provider on behalf of the client • - The event generated by Query as a Web Service and Live Office Web Services provider on behalf of the client

  23. BI Platform Components Generating Events BI Platform Specific Events

  24. SAP BusinessObjects Web Intelligence Specific Events • SAP BusinessObjects Web Intelligence (WEBI) Events: • Components Generating Events:

  25. SAP BusinessObjects Analysis Specific Events • SAP BusinessObjects Analysis Events:

  26. Auditing Events: Workflow Example 1 • Example of sequence of events for viewing an SAP Crystal Reports report (document A) on demand with prompts in BI Launchpad.

  27. Auditing Events: Workflow Example 2 • Example of sequence of events for viewing an SAP BusinessObjects Web Intelligence document (document A) in CMC with two prompts.

  28. Lesson Summary After completing this lesson, you are now able to: • Describe what auditing is • Describe how to configure and troubleshoot auditing • Describe the purpose and benefits of auditing dashboard • Explain the meaning and structure of new auditing events • Describe the ADS schema • Describe how auditing events are stored in ADS

  29. Thank You

More Related