Documente Academic
Documente Profesional
Documente Cultură
1
Patents Business Objects owns the following U.S. patents, which may cover products that are offered and sold by Business Objects: 5,555,403, 6,247,008 B1, 6,578,027 B2, 6,490,593 and 6,289,352. Business Objects, the Business Objects logo, Crystal Reports, and Crystal Enterprise are trademarks or registered trademarks of Business Objects SA or its affiliated companies in the United States and other countries. All other names mentioned herein may be trademarks of their respective owners. Copyright 2005 Business Objects. All rights reserved. Business Objects products in this release may contain redistributions of software licensed from third-party contributors. Some of these individual components may also be available under alternative licenses. A partial listing of third-party contributors that have requested or permitted acknowledgments, as well as required notices, can be found at: http://www.businessobjects.com/thirdparty Trademarks
Contents
Chapter 1
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 What is Auditor? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 Comparing Auditor with BusinessObjects Auditor . . . . . . . . . . . . . . . . . 9 Comparing Auditor with auditing in BusinessObjects Enterprise . . . . . 10 Chapter 2 Managing Auditing 11
How does auditing work? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 Configuring the auditing database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 Which actions can I audit? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 Reference list of auditable actions . . . . . . . . . . . . . . . . . . . . . . . . 15 Enabling auditing of user and system actions . . . . . . . . . . . . . . . . . . . . . . 19 Configuring the universe connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 Using sample audit reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 Controlling synchronization of audit actions . . . . . . . . . . . . . . . . . . . . . . . . 23 Optimizing system performance while auditing . . . . . . . . . . . . . . . . . . . . . 24 Chapter 3 Auditing Reports 27
Using auditing reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 Why are reports important? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 Auditor report names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 Average Number of Users Logged In . . . . . . . . . . . . . . . . . . . . . . 28 Average Refresh Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 Average Session Duration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 Average Session Duration per Cluster . . . . . . . . . . . . . . . . . . . . . 29 Average Session Duration per User . . . . . . . . . . . . . . . . . . . . . . . 29 Cluster Nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 Document Information Detail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 Document Scheduling and Viewing Status . . . . . . . . . . . . . . . . . . 30 Job Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 Jobs per Job Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 Jobs per User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 Job Servers on the System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Contents
Last Login for User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 Least Accessed Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 Most Accessed Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 Most Active Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 Most Popular Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 Most Popular Actions per Document . . . . . . . . . . . . . . . . . . . . . . . 33 Number of User Sessions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 Number of Users in the System . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 Password Modifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 Peak Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 Refresh and Edit Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 Rights Modification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 Total Users Logged In by Day . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 User Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 User Activity per Session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 Users Who Logged Off Incorrectly . . . . . . . . . . . . . . . . . . . . . . . . . 35 Viewing sample auditing reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 Creating custom audit reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 Auditing database schema reference . . . . . . . . . . . . . . . . . . . . . . . . . . 36 Audit_Event . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 Audit_Detail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 Server_Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 Event_Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 Application_Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 Detail_Type table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 Appendix A Business Objects Information Resources 49
Documentation and information services . . . . . . . . . . . . . . . . . . . . . . . . . . 50 Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50 Whats in the documentation set? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50 Where is the documentation? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50 Documentation from the products . . . . . . . . . . . . . . . . . . . . . . . . . 50 Documentation on the web . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Contents
Documentation on the product CD . . . . . . . . . . . . . . . . . . . . . . . . 50 Send us your feedback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51 Customer support, consulting and training . . . . . . . . . . . . . . . . . . . . . . . . . 51 How can we support you? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51 Online Customer Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51 Looking for the best deployment solution for your company? . . . . . . . 52 Looking for training options? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52 Useful addresses at a glance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Contents
chapter
Overview
BusinessObjects Enterprise Auditor provides you with a way to monitor and record key facts about your BusinessObjects Enterprise deployment. The information about who is using your system, and which objects they are accessing allows you to answer system-level questions like which groups within the company use our BusinessObjects Enterprise system the most? or 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. This information lets you be more proactive in managing the operation and deployment of your BusinessObjects Enterprise system, while helping you better evaluate the value that BusinessObjects Enterprise provides to your organization. This chapter gives you high level information on BusinessObjects Enterprise Auditor. In the remainder of this document, this product will be referred to as Auditor. This chapter also contains a section that outlines the difference between the current and previous implementations of auditing.
Comparing Auditor with BusinessObjects Auditor on page 9 Comparing Auditor with auditing in BusinessObjects Enterprise on page 10
What is Auditor?
Auditor is a product that allows you to audit your BusinessObjects Enterprise deployment. Auditor has these key features:
It monitors and records key facts that you want audited in your deployment of BusinessObjects Enterprise. It contains many predefined reports designed to answer many of the questions you may have about your deployment of BusinessObjects Enterprise. It includes the universe on which these reports are built so you can customize the reports that are included or create your own reports.
Auditor consists of a universe and two sets of reports that allow users to report off of the auditing database. The Auditor reports are available in two formats: Web Intelligence or Crystal Reports. Both sets of reports are published in the Auditor folder.
Provided you have a BusinessObjects Enterprise premium license, or a BusinessObjects Enterprise Auditor Add-On license, Auditor can be installed with BusinessObjects Enterprise. The auditing database can be configured in two places:
When you install BusinessObjects Enterprise, the auditing database can be configured on the CMS Database Information dialog box. For further installation information, see the BusinessObjects Enterprise Installation Guide.
After you install, Auditor can be configured from the Central Configuration Manager. For further configuration information, see Configuring the auditing database on page 13.
Auditor Application The Auditor application contained predefined indicators. The multiple tabs or sections within the indicators, which were known as reports.
Auditor in BusinessObjects Enterprise XI Release 2 Auditor uses the term reports instead of indicators. In Auditor, the multiple tabs or sections in the report are known as report sections.
The indicators were accessed through Auditor reports are now integrated a custom JSP interface. with BusinessObjects Enterprise, and are accessed through InfoView. The indicators were BusinessObjects or Full Client documents. The auditor application was installed separately. There were five categories for the reports. Business questions would open specific indicators. Auditor reports are now available as either Web Intelligence or Crystal Reports documents. Auditor is installed with BusinessObjects Enterprise. Auditor reports are in stored in the Auditor folder. Auditor reports are opened from the Auditor folder.
In previous versions, the auditing database could only be configured after the install.
In previous versions, if you wanted to report off of your auditing database, you would need to create your own reports. In previous versions, if you wrote your own audit custom reports, you would have to configure each report to use the auditing database.
10
Managing Auditing
chapter
You must configure the auditing database. If you installed Auditor, and provided the authentication details for your auditing database when you installed BusinessObjects Enterprise, you have already configured the auditing database. If you did not install Auditor, you must configure the auditing database before you can use Auditor. For step by step instructions, see Configuring the auditing database on page 13. Note: Auditor is installed by default when you install and use a keycode that authorizes you to Auditor, unless you cleared the Auditing Database check box during the install, or did a custom install and specifically excluded Auditor.
You must first determine which server controls that action. To determine which server controls an action, see Reference list of auditable actions on page 15. You must enable auditing of that action in the Servers management area of the Central Management Console (CMC). For step by step instructions, see Enabling auditing of user and system actions on page 19. You must configure the universe connection. The auditing reports are written against the Activity universe, this universe connection must be configured so it can connect to the auditing database. For step by step instructions, see Configuring the universe connection on page 21.
As the auditee, the BusinessObjects Enterprise server will then begin to record these audit actions in a local log file. As the auditor, the CMS controls the overall audit process. Each server writes audit records to a log file local to the server. At regular intervals the CMS communicates with the auditee servers to request copies of records from the auditees local log files. When the CMS receives these records it writes data from the log files to the central auditing database.
12
The CMS also controls the synchronization of audit actions that occur on different machines. Each auditee provides a time stamp for the audit actions that it records in its log file. To ensure that the time stamps of actions on different servers are consistent, the CMS periodically broadcasts its system time to the auditees. The auditees then compare this time to their internal clocks. If differences exist, they make a correction to the time stamp they record in their log files for subsequent audit actions. Once the data is in the auditing database, you can run the sample reports against the database or design custom reports to suit your own needs.
It is recommended that you develop a back up strategy for your auditing database. If necessary, contact your database administrator for more information. Note:
The CMS system database and the auditing database are independent. If you choose, you can use different database software for the CMS system database and the auditing database, or you can install these databases on separate servers. If you have a CMS cluster, every CMS in the cluster must be connected to the same auditing database, using the same connection method and the same connection name. Note that connection names are case sensitive. (See BusinessObjects Enterprise Administrators Guide for more information on setting up CMS clusters.)
13
1. 2. 3. 4.
To configure the auditing database on Windows Start the Central Configuration Manager (CCM). Stop the CMS. Click Specify Auditing Data Source. In the Select Database Driver dialog box, specify whether you want to connect to the new database through SQL Server (ODBC), or through one of the native drivers. Click OK. The remaining steps depend upon the connection type you selected:
5. 6.
If you selected ODBC, the Windows Select Data Source dialog box appears. Select the ODBC data source that you want to use as the auditing database; then click OK. (Click New to configure a new Data Source Name (DSN).) Use a System DSN, and not a User DSN or File DSN. By default, server services are configured to run under the System account, which only recognizes System DSNs. When prompted, provide your database credentials and click OK. If you selected a native driver, you are prompted for your database Server Name, your Login ID, and your Password. Provide this information and then click OK.
The SvcMgr dialog box notifies you when the auditing database setup is complete. 7. 8. Click OK. Start the CMS. When the CMS starts, it will create the auditing database.
Note: You can also configure the auditing database using the Properties option for the CMS. Stop the CMS, select Properties, and then go to the Configuration tab. Select Write server audit information to specified data source, and then click Specify. To configure the auditing database on UNIX For more information on UNIX scripts, see Unix Tools in the BusinessObjects Enterprise Administrators Guide. 1. 2. Use ccm.sh to stop the CMS. Run cmsdbsetup.sh.
14
3. 4. 5. 6.
Choose the selectaudit option, and then supply the requested information about your database server. Run serverconfig.sh. Choose the Modify a server option. Select the CMS, and enable auditing. Enter the port number of the CMS when prompted (the default value is 6400).
Use ccm.sh to start the CMS. When the CMS starts, it will create the auditing database. Note:
The CMS acts as both an auditor and as an auditee when you configure it to audit an action that the CMS itself controls. 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.
15
User Actions
Actions Objects An object is created. An object is deleted. An object is modified. A report has been viewed successfully. A report could not be viewed. A report is opened successfully using: the Advanced DHTML viewer. BusinessObjects Enterprise Server CMS
Crystal reports
A report fails to open. A report has been created successfully using: a custom application that uses the RAS SDK. A report fails to be created. A report is saved successfully (using a custom application based on the RAS SDK). A report fails to save using a custom application based on the RAS API. Get list of universes. Web Intelligence Web Report Server Intelligence A user has begun creating a new Web documents Intelligence document, which triggers a request to the server for the list of available universes. Save document to repository. A user has saved a Web Intelligence document within BusinessObjects Enterprise. Read Document. User opens an existing Web Intelligence document. Selection of universe.
A user has selected a universe as they create a new Web Intelligence document, or as they edit an existing Web Intelligence document.
16
Actions
Refresh document. Web Intelligence Web Report Server Intelligence User manually refreshes a Web documents Intelligence document, or the user opens a Web Intelligence document that is set to refresh on open. Edit document. User enters Edit document mode for an existing Web Intelligence document. Apply format.
User applies a formatting change to an existing Web Intelligence document in a query panel.
Get page. Server renders the pages of a Web Intelligence document in response to a user request to display all or part of a document. Generate SQL. Server generates an SQL query in response to a user action that requires data to be retrieved from a database. Drill out of scope.
User drills past the scope of the data currently in memory, and triggers a call to the database for more data. List of values. 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. Select prompt.
17
Actions Desktop A job has been run successfully. Intelligence Either a Desktop Intelligence document documents has been scheduled or a publication based of that document has been scheduled.
A job has failed to run. Users A job failed but will try to run again. A concurrent user logon succeeds. A named user logon succeeds. A user logon fails. A users password is changed. User logs off. Send an object to a destination A job has been run successfully. (A user has successfully sent an object to a destination.) Destination Job Server CMS
File-based events
A job has failed to run. (An object has failed to be sent to a destination.) A job failed but will try to run again. An event is registered. Event Server (Event is created, and registered with system) An event is updated. (The name, description, or filename of an event is modified.) An event is unregistered. (Event is removed from system.)
18
System Actions
Actions Scheduled objects A job has been run successfully. For example, a scheduled Crystal report or publication has run successfully. A job has failed to run. For example, a scheduled Crystal report or publication has failed to run. BusinessObjects Enterprise Server Job Servers
Tip: To audit every failure of a scheduled Crystal report, a scheduled program, or a scheduled List of Values, enable auditing of A job has failed to run on the Job Server, and Communication with a running instance is lost. on the Central Management Server. A job failed but will try to run again. Communication with a running instance is lost. CMS For example, a scheduled Crystal report has failed to run because communication with the instance was lost, and the scheduled time for running the report expired. Note: You do not need to enable this option to audit every failure of a scheduled Web Intelligence document. An event is triggered. Event Server
File-based events
19
In some special cases you may wish to enable auditing on only one server of a given type. For example, if you are interested in the success or failure of only one kind of scheduled report and you have configured your system so that these reports are processed on one particular Job Server, it is not necessary to enable auditing on every Job Server in your system. You only need to enable auditing on the Job Server where the reports are processed. Note: You must configure the auditing database before you can collect data on audit actions. See Configuring the auditing database on page 13 for information on how to configure the auditing database. 1. 2. To enable audit actions Go to the organize Servers area of the CMC. Click the server that controls the action that you wish to audit. (See the Reference list of auditable actions on page 15 to find the correct server.) 3. Click the Auditing tab.
4. 5. 6.
Select the Auditing is enabled check box. Select the audit actions that you wish to record. Ensure that your audit log file is located on a hard drive that has sufficient space to store the log files. (See Optimizing system performance while auditing on page 24 for information on adjusting the size of log files.)
20
7. Tip:
Click Update. To audit every failure of a scheduled Crystal report, a scheduled program, or a scheduled List of Values, enable auditing of A job has failed to run on the Job Server, and Communication with a running instance is lost. on the Central Management Server. Auditing is enabled independently on each server. If you want to audit all actions of a given type, enable identical audit actions on every server that supports those actions. Otherwise your audit record will be incomplete. For example, if you want to track the total number of concurrent logons to your BusinessObjects Enterprise system, you must enable logging of concurrent logons on every Central Management Server in your system.
Tip: You may want to write down the name of your data source as it will be required when you create or edit the universe connection. 1. 2. 3. To configure the Activity universe connection Start Designer from the BusinessObjects Enterprise program group. Click on the connections icon in the toolbar. The Connection List dialog box appears. Click Add, and then click Next.
21
4. 5. 6. 7. 8. 9.
Expand the database type and the version that corresponds with the your auditing database. Select the driver or client to use. Enter a name for your connection. Enter the User Name and Password for your connection. Select the Data source name from the list, and then click Next. Click Next on the Perform a Test dialog box.
10. Click Next on the Advanced Parameters dialog box. 11. Click Finish on the Custom Parameters dialog box. 12. Click Finish to exit and finalize your connection.
One set was created using Crystal Reports. One set was created using Web Intelligence.
Both sets of reports are available in the collateral folder on your product distribution in the file auditing.biar. These sample reports are published to the Auditor folder when you install BusinessObjects Enterprise with a product keycode which authorizes you to use Auditor. The Crystal Reports audit reports are available as object packages with the report sections as individual documents. The Web Intelligence audit reports are available as Web Intelligence documents with the report sections as tabs within the documents. Both sets of reports are based on the Activity universe. Note: You can also deploy the auditing samples to another node. To do this, use the Import Wizard to deploy the auditing.biar to the CMS on the node where you want the reports. For further details, see the BusinessObjects Enterprise Administrators Guide. If you configured the auditing database when you installed BusinessObjects Enterprise, you must do these things before using the sample audit reports:
Enable the auditing of the user and server actions needed to provide data for the sample reports. For information on how to enable auditing on servers, see Enabling auditing of user and system actions on page 19.
22
For procedural details, see Configuring the universe connection on page 21. If you did not configure the database when you installed BusinessObjects Enterprise, before you use the reports, you must do these things:
Configure the auditing database before you use the sample reports. For information on how to configure the auditing database, see Configuring the auditing database on page 13 Enable the auditing of the user and server actions needed to provide data for the sample reports. For information on how to enable auditing on servers, see Enabling auditing of user and system actions on page 19
Configure the universe connection used for the sample reports. For procedural details, see Configuring the universe connection on page 21.
After you enable auditing of the user and server actions, the auditing database will then begin to be populated with the audit data you specified. Note: If you have recently enabled auditing, the sample audit reports may contain little or no data the first time you view them.
You can turn off this option by setting minutes to zero. For more information on the CMS, see Server Command Lines in the BusinessObjects Enterprise Administrators Guide. This built-in method of time synchronization will be accurate enough for most applications. For more accurate and robust time synchronization, configure the auditee and auditor machines to use an Network Time Protocol (NTP) client, and then turn off internal synchronization by setting
-AuditeeTimeSyncInterval 0
23
Tip: If you have a CMS cluster, apply the same command-line options to each server. Only one CMS in the cluster acts as the auditor. However, if this CMS fails, another CMS takes over auditing. This CMS will apply its own command-line options. If these options are different than those of the original auditor, audit behavior may not be what you expect.
default value is 5.) The CMS requests audit records from each audited server every audit interval.
-AuditBatchSize number, where number is between 50 and 500. (The
default value is 200.) The CMS requests this fixed number of records from each audited server, every time interval.
-auditMaxEventsPerFile number (number has a default value of 500
and must be greater than 0). The maximum number of records that an audited server will store in a single audit log file. When this maximum value is exceeded, the server opens a new log file. Note: Log files remain on the audited server until all records have been requested by the CMS. Changing each of these options has a different impact on system performance. For example, increasing the audit interval reduces frequency with which the CMS writes events to the auditing database. Decreasing the audit batch size decreases the rate at which records are moved from the audit log files on the audited servers to the auditing database, thereby increasing the length of time that it takes these records to get transferred to the central auditing database. Increasing the maximum number of audit events stored in each audit log file reduces the number of file open and close operations performed by audited servers. You can use these options to optimize audit performance to meet your needs. For example, if you frequently need up-to-date information about audited actions, you can choose a short audit interval and a large audit batch size. In this case, all audit records are quickly transferred to the auditing database, and you can always report accurately on the latest audit actions. However, choosing these options may have an impact on the performance of BusinessObjects Enterprise.
24
Alternatively, you may only need to review audit results periodically (weekly, for example). In this case you can choose to increase the audit interval, and to decrease the number of audit records in each batch. Choosing these options minimizes the impact that auditing has on the performance of BusinessObjects Enterprise. However, depending upon activity levels in your system, these options can create a backlog of records stored in audit log files. This backlog is cleared at times of low system activity (such as overnight, or over a weekend), but means that at times your audit reports may not contain records of the most recent audit actions. For more information on changing command-line options, see the BusinessObjects Enterprise Administrators Guide.
25
26
Auditing Reports
chapter
You can use the auditing reports that are included with BusinessObjects Enterprise. You can modify the auditing reports that are included with BusinessObjects Enterprise. You can create your own auditing reports.
the list of the report names the report sections included with the reports the report prompts
Average Number of Logged In select reporting year Sessions Users Logged In Average Number of Users Logged In select reporting month
28
29
Report sections Average Session Duration in Minutes per Month per User Average Session Duration in Minutes per Week per User
Report prompts
Cluster Nodes
Report sections Servers in the Cluster Report prompts None
Job Summary
Report sections Jobs per Status Successful Jobs Failed Jobs Report prompts
30
31
32
Password Modifications
Report sections Password Modifications - By Month Password Modifications - By Week Password Modifications - By Details Report prompts select start date select end date
33
Peak Usage
Report sections Users Login Peaks Session Login Peaks Number of Action Peaks Report prompts select year
Rights Modification
Report sections Rights Modification - By User Report prompts select start date
Total Users Logged In by Day - enter a date Total Number of Logged In Users Total Users Logged In by Day Total Number of Logged in Sessions
User Activity
Report sections User Activity by Month User Activity by Week User Activity by Day Report prompts select start date select end data
34
To open a Web Intelligence audit report, click on the report you want to view. To open a Crystal Reports audit report, open the object package, and then open the report you want to view.
35
Audit_Event on page 36 Audit_Detail on page 37 Server_Process on page 38 Detail_Type table on page 40 Event_Type on page 39 Application_Type on page 39
The following diagram shows the Activity universe which is based on the auditing database.
Audit_Event
The Auditt_Event table stores one record per action that is audited and contains general information about each audit event.
36
Field
Server_CUID
Description Server process ID. Combined with the Event_ID to form the primary key for the Audit_Event table. A unique ID generated by the server to identify the audit event. Combined with Server_CUID to form the primary key for the Audit_Event table. Name of user who performed the action. Time for start of action in UTC (Coordinated Universal Time) to the nearest millisecond. The time stamp is created by the server recording the action in its log file, and includes any correction necessary to synchronize with CMS time. You may want to correct this time to your local time zone when creating audit reports. Duration, in seconds, of the action that is audited. Number that uniquely identifies the type of action the entry represents. Foreign key for the Event_Type table. Info Object ID of object associated with the action. This number uniquely identifies an object. Field reserved for error codes generated by the Web Intelligence Report Server.
Event_ID
User_Name Start_Timestamp
Duration Event_Type_ID
Object_CUID Error_Code
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.
37
Field
Server_CUID
Description Server process ID. Combined with the Event_ID and the Detail_ID to form the primary key for the Audit_Detail table. A unique ID generated by the server to identify the audit event. Combined with Server_CUID and the Detail_ID to form the primary key for the Audit_Detail table. The Detail_ID field is used to number the individual details associated with each audit action. That is, if there are two details associated with a particular audit action, the first will have a Detail_ID of 1, and the second will have a Detail_ID of 2. Number that uniquely identifies the type of detail about the audit action that the entry represents. Foreign key for the Detail_Type table. Information about the audit detail being recorded. For example, if the Detail_Type_Description were universe name, the detail text would contain the name of that universe.
Event_ID
Detail_ID
Detail_Type_ID
Detail_Text
Server_Process
The Server_Process table contains information about the servers running within your BusinessObjects Enterprise system which can generate audit events. Field
Server_CUID Server_Name
Description Server process ID. Primary key for the Server_Process table. Machine name of the server that produced the action. That is, the host name. that generated the audit action. Foreign key to the Application_Type table.
38
Field
Server_FullName
Description Friendly name of the server that produced the action. The servers friendly name is the name displayed in the CMC. The default friendly name is
hostname.servertype.
Server_Version
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 Field
Event_Type_ID
Description Number that uniquely identifies the type of audit event that the entry represents.
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. Field Name
Application_Type_ID
Description A unique ID that identifies the type of application that generated the audit action. The description of the application generating the audit event.
Application_Type_Description
39
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 Detail_Type table. The information in the Detail_Type table is equivalent to the information that was recorded in variable AuditStrings in Crystal Enterprise 10. Field
Detail_Type_ID Detail_Type_Description
Description Number that uniquely identifies the type of audit detail that the entry represents. The description of the type of audit detail generated by the audit event.
65538
40
Event_Type_ ID Event_Type_Description Description 65542 New folder created. A new folder is created, or an existing folder is copied. Note that this audit string will not be recorded when a new user account is created, even though creating a user creates a user folder. A folder is deleted. Note that this audit string will be recorded when a user account (and therefore the users folder) is deleted. The name, location, or description of the folder was changed. A scheduled report or scheduled program failed to run because communication with the running instance was lost, and the scheduled time for running the job expired. Note: This action must be audited by the CMS as Job Servers are not aware of losing communications with a job. Cache Server audit events Event_Type_ ID Event_Type_Description 196609 Crystal report viewed successfully. A report could not be viewed. Description User successfully viewed a Crystal report that has saved or live data. User attempted to view a Crystal report, but was not successful.
65543
Folder deleted.
65544
Folder modified.
65545
196610
41
Job Server audit events For scheduled objects, the audit messages give you information about the status of scheduled actions. For example, the audit messages can tell you if a scheduled report ran successfully. For the Destination Job Server, the audit messages give you information on whether an object was sent to a destination, as requested by a user. Event_Type Event_Type_Description _ ID 327681 Job successful. Description The object ran as scheduled (or requested) and the job completed successfully. The scheduled job did not complete successfully. The scheduled job did not complete successfully. The job will be retried by the CMS at a later time. For more information on scheduling jobs, see the BusinessObjects Enterprise Administrators Guide.
327682 327683
Event Server audit events Event_Type_ ID Event_Type_Description 262145 Event registered Description User creates a file-based event that can be used to schedule objects. User deletes a file-based event. Event object was modified by a user, or by the system. Events are updated when a user modifies the name or description of the file-based event. File-based event was initiated.
262146 262147
262148
Event triggered
42
Report Application Server audit events The Report Application Server (RAS) is used to view reports opened with the Advanced DHTML viewer, and to create reports using custom applications developed with the RAS SDK.
43
Description
Report was opened for User opened a report for viewing and/or modification viewing or modification. Note: In a few cases, this Event_Type_ID may be generated when the report opens but cannot be viewed. This may occur when:
There are problems with the database setup for the report. For example, you may see this message when the database driver for the report is not present on the client machine A processing extension associated with the report aborts viewing, or fails. The report used Business Views and the user did not have permissions to refresh the underlying data connections. The machine running the RAS ran out of space in its temporary directory.
458754
generated when a custom application created using the RAS SDK saves a report (using the Save method). Consult your RAS SDK documentation for details.
44
Event_Type_ ID Event_Type_Description 458755 Report was created and saved to the CMS
Description A new report was created and saved. This Event_Type_ID is generated when a custom application created using the RAS SDK saves a new report (using the Save As method). Consult your RAS SDK documentation for details. The report could not be opened by the RAS. An existing report could not be saved by RAS. This Event_Type_ID is generated when a custom application created using the RAS SDK cannot save a new report (using the Save As method). Consult your RAS SDK documentation for details. A newly created report could not be saved by RAS.
458756 458757
Report could not be opened. Report could not be saved to the CMS.
458758
Web Intelligence Report Server audit events Event_Type_ ID Event_Type_Description Description 6 Get list of universes User accesses a list of universes as part of a document creation workflow. User saves a Web Intelligence document to BusinessObjects Enterprise. User opens an existing Web Intelligence document. User selects a universe as part of a document creation workflow. This event occurs when a user opens the query panel.
11 13
45
Event_Type_ ID Event_Type_Description Description 19 Document refresh User manually refreshes a Web Intelligence document, or user opens a Web Intelligence document that has the refresh on open document property assigned. 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. User has moved into Edit document mode. User applies a formatting change to a document, in a query panel. User action results in a request to server to generate the necessary data and layout to display all or part of a Web Intelligence document. Appears when a user refreshes a document. User drills past the scope of the data currently in memory, and triggers a call to the database for more data.
21
List of values
22 28
40
Get page
41 42
46
appendix
Documentation
You can find answers to your questions on how to install, configure, deploy, and use Business Objects products from the documentation.
Index
A
audit actions enabling auditing of 19 reference list 15 synchronizing records 23 audit enablement 19 auditable actions CMS 19 Destination Job Server 18 Event Server 18 Job Server 19 auditee 12 auditing configuring database 13 database schema 36 enabling 19 information flow 12 optimizing performance 24 reporting results 22, 36 synchronizing records 23 user and system actions 15 auditing database configuring 13 database schema 36 Application_Type table 39 Audit_Detail table 37 Audit_Event table 36 Detail_Type table 40 Event_Type table 39 Server_Process table 38 auditor 12 Auditor report names 28 Average Number of Users Logged In 28 Average Refresh Time 29 Average Session Duration 29 Average Session Duration per Cluster 29 Average Session Duration per User 29 Cluster Nodes 30 Document Information Detail 30 Document Scheduling and Viewing Status 30 Job Servers on the System 31 Job Summary 30 Jobs per Job Server 31 Jobs per User 31 Last Login for User 31
Least Accessed Documents 32 Modifications 33 Most Accessed Documents 32 Most Active Users 32 Most Popular Actions 32 Most Popular Actions per Document 33 Number of User Sessions 33 Number of Users in the System 33 Peak Usage 34 Refresh and Edit Activity 34 Rights Modification 34 Total Users Logged in by Day 34 User Activity 34 User Activity per Session 35 Users Who Logged Off Incorrectly 35 Auditor, explanation of 8
B
Business Objects consulting services 52, 53 support services 51 training services 52, 53, 53 BusinessObjects 5.x/6.x Auditor 9 BusinessObjects Enterprise auditing 10
C
Cache Server auditable actions 16 CMS auditable actions 19 comparing BusinessObjects Enterprise Auditor with BusinessObjects 5.x/6.x Auditor 9 with BusinessObjects Enterprise auditing 10 configuring auditing database 13 auditing database on UNIX 14 auditing database on windows 14 universe connection 21 consultants, Business Objects 52 creating custom audit reports 36 Crystal Reports sample audit reports 22 custom audit report creation 36 customer support 51
D
Destination Job Server auditable actions 18
55
Index
P
Password Modifications 33 Peak Usage 34 performance 24 performance while auditing 24 Program Job Server 19 Program Job Server auditable actions 19
E
education. See training enabling auditing 19 Event Server auditable actions 19 Event Server auditable actions 18
R
Refresh and Edit Activity 34 Report Application Server auditable actions 16 Report Job Server 19 auditable actions 19 reports audit 22, 36 custom 36 sample 22 required steps to audit actions 12 resources 50 Rights Modification 34
F
feedback, on documentation 51
I
information resources 50
J
Job Servers auditable actions 19
S L
Least Accessed Documents 32 List of Values Job Server auditable actions 19 sample audit reports 22 steps to audit actions 12 support customer 51 locations 51 technical 51 web site 51 synchronizing audit actions 23 system actions, list of auditable 19
M
Most Accessed Documents 32 Most Active Users 32 Most Popular Actions 32 Most Popular Actions per Document 33
T
technical support 51 Total Users Logged in by Day 34 training, on Business Objects products 52
N
Number of User Sessions 33 Number of Users in the System 33
O
Online Customer Support 51 optimizing system 24 Optimizing system performance 24
U
universe connection configuration 21 user actions, list of auditable 16 User Activity 34 User Activity per Session 35
56
Index
W
web customer support 51 getting documentation via 50 useful addresses 53 Web Intelligence Job Server auditable actions 19 Web Intelligence Report Server auditable actions 16, 17 Web Intelligence sample audit reports 22 web sites support 51 training 52
57
Index
58