COGNOS Business Intelligence Series 7
pes.pdf pes.pdf
Chapter 6: Audit Server Activity A typical command line contains the following entries. Command Line Argument -dbname -dbconnect -dbuser -dbpass -auditlocation -errorlog -nbrows -exitonerror Description The database name. The database connection string that contains the database type and connection information. Copy all the text in the connection string after the equal sign (=) from the Connection Tab in Access Manager - Administration and enclose it in double quotes. For more information, see "Set Up a Connection String to the Audit Database" (p. 73) A database user name with read and write access to the database. The password for the database user name. The location of the generated audit log files, usually the installation location\cern\ppserver folder. The name of the log file. The number or rows processed for each transaction. Stop processing when an error occurs. Example In the following example, audit data is transferred to an Oracle data source. C:\cd Program Files\Cognos\cer4\bin C:\Program Files\Cognos\cer4\bin\PPESAuditFileProcessor -dbname OracleDataSource -dbconnect "^UserID:^ ?Password:;LOCAL;OR;ORACLE@%s@cyborg/%s" -dbuser Admin -dbpass AdminPW -auditlocation C:\Program Files\Cognos\cer4\ppserver Use the Sample Audit Reports Rather than creating an Impromptu catalog from scratch, you can use the sample audit catalog provided with PowerPlay Enterprise Server to query the audit database. Using the catalog means that you must have access to a computer that has Impromptu installed on it. Steps 1. Open Impromptu. 2. From the Catalog menu, click Open. 3. Locate the PPES.cat file and double-click it. By default, the PPES.cat file is installed in the installation location\cern\samples\ppwb\audit folder. 4. From the File menu, click Open and go to installation location\cern\samples\ppwb\audit folder. 5. Select the report that you want to view. Understand the Sample Audit Reports The following is a list of the sample reports included with PowerPlay Enterprise Server. You can run the sample audit reports from the Impromptu client, or you can publish the reports and run them on the Web. 74 Cognos PowerPlay (R)
Chapter 6: Audit Server Activity The Dimension Usage, Level Usage, and Measure Usage reports all record usage counts. Usage counts represent the number of crosstab cells generated by a user’s query. Therefore, a usage count is only an approximation of the actual usage. We recommend that you segment the range of usage counts into high, medium, and low categories, as shown in the example reports. This will help you to differentiate users who generate large queries from users who perform their analysis at a summary level. User Information This report lists the information in the audit database that is most often of interest to administrators. The report identifies the user, user class, source analyzed, and the number of times that the source was accessed. Dimension Usage This report shows the dimension counts for each dimension per cube. These are broken down by user. Use this report to evaluate how particular users view dimension data. Level Usage This report shows the level counts for each level per dimension in a cube. These are broken down by user. Use this report to evaluate how particular users view level data. Measure Usage This report shows the measure counts for each measure in a cube. These are broken down by user. Use this report to evaluate how particular users view measure data. Understand the Audit Database The PowerPlay Enterprise Server audit file processor extracts the auditing information from the audit files and populates the database with the processed audit information. The following diagram shows a model of the tables used to persist all audit data and their relationship to each other. Enterprise Server Guide 75
- Page 23 and 24: Chapter 2: Configure Servers Perfor
- Page 25 and 26: Disable Saving of Cognos Sub-Cubes
- Page 27 and 28: Chapter 3: Control Processes This c
- Page 29 and 30: Chapter 3: Control Processes In a m
- Page 31 and 32: Chapter 3: Control Processes Exampl
- Page 33 and 34: Monitor Windows Connections Chapter
- Page 35 and 36: Chapter 3: Control Processes When y
- Page 37 and 38: Chapter 4: Deploy Cubes and Reports
- Page 39 and 40: Chapter 4: Deploy Cubes and Reports
- Page 41 and 42: Add a Cube or Report Chapter 4: Dep
- Page 43 and 44: Chapter 4: Deploy Cubes and Reports
- Page 45 and 46: Add Dimension Line Information to a
- Page 47 and 48: Chapter 4: Deploy Cubes and Reports
- Page 49 and 50: Chapter 4: Deploy Cubes and Reports
- Page 51 and 52: Chapter 4: Deploy Cubes and Reports
- Page 53 and 54: Chapter 4: Deploy Cubes and Reports
- Page 55 and 56: Chapter 4: Deploy Cubes and Reports
- Page 57 and 58: Chapter 4: Deploy Cubes and Reports
- Page 59 and 60: Chapter 4: Deploy Cubes and Reports
- Page 61 and 62: Chapter 5: Provide Drill-through Ac
- Page 63 and 64: Chapter 5: Provide Drill-through Ac
- Page 65 and 66: Chapter 5: Provide Drill-through Ac
- Page 67 and 68: Chapter 5: Provide Drill-through Ac
- Page 69 and 70: Chapter 5: Provide Drill-through Ac
- Page 71 and 72: Chapter 6: Audit Server Activity Us
- Page 73: Chapter 6: Audit Server Activity 2.
- Page 77 and 78: Chapter 6: Audit Server Activity Co
- Page 79 and 80: Level Usage Table Chapter 6: Audit
- Page 81 and 82: Appendix A: Context Help This secti
- Page 83 and 84: Appendix A: Context Help Maximum Re
- Page 85 and 86: Appendix A: Context Help Parent Sho
- Page 87 and 88: Appendix A: Context Help When this
- Page 89 and 90: Appendix A: Context Help If most in
- Page 91 and 92: Appendix A: Context Help Report Lig
- Page 93 and 94: Appendix A: Context Help Text Color
- Page 95 and 96: Appendix A: Context Help Button Set
- Page 97 and 98: Appendix A: Context Help Impromptu
- Page 99 and 100: Appendix A: Context Help Delete Del
- Page 101 and 102: Appendix B: Batch Administration Th
- Page 103 and 104: Appendix B: Batch Administration De
- Page 105 and 106: Appendix B: Batch Administration KI
- Page 107 and 108: Appendix B: Batch Administration Yo
- Page 109 and 110: Appendix C: Managing Temporary File
- Page 111 and 112: Appendix C: Managing Temporary File
- Page 113 and 114: Glossary Agent A user-defined proce
- Page 115 and 116: NewsItem In Upfront, an entry that
- Page 117 and 118: Index Symbols .crr files, 62, 68 .c
- Page 119 and 120: Index cubes, 13 location, 14 mirror
- Page 121 and 122: Index O definition, 114 OLAP, 13 P
- Page 123 and 124: Index Server groups, 28 server mirr
Chapter 6: Audit Server Activity<br />
The Dimension Usage, Level Usage, and Measure Usage reports all record usage counts. Usage<br />
counts represent the number of crosstab cells generated by a user’s query. Therefore, a usage count<br />
is only an approximation of the actual usage. We recommend that you segment the range of usage<br />
counts into high, medium, and low categories, as shown in the example reports. This will help you<br />
to differentiate users who generate large queries from users who perform their analysis at a<br />
summary level.<br />
User Information<br />
This report lists the information in the audit database that is most often of interest to<br />
administrators. The report identifies the user, user class, source analyzed, and the number of times<br />
that the source was accessed.<br />
Dimension Usage<br />
This report shows the dimension counts for each dimension per cube. These are broken down by<br />
user.<br />
Use this report to evaluate how particular users view dimension data.<br />
Level Usage<br />
This report shows the level counts for each level per dimension in a cube. These are broken down<br />
by user.<br />
Use this report to evaluate how particular users view level data.<br />
Measure Usage<br />
This report shows the measure counts for each measure in a cube. These are broken down by user.<br />
Use this report to evaluate how particular users view measure data.<br />
Understand the Audit Database<br />
The PowerPlay Enterprise Server audit file processor extracts the auditing information from the<br />
audit files and populates the database with the processed audit information.<br />
The following diagram shows a model of the tables used to persist all audit data and their<br />
relationship to each other.<br />
Enterprise Server Guide 75
Change language