COGNOS Business Intelligence Series 7
pes.pdf pes.pdf
Chapter 6: Audit Server Activity ❑ ❑ ❑ ❑ • using the scripts installed with PowerPlay Enterprise Server to create a relational database, such as Oracle or Microsoft SQL Server if you want to run the reports on data collected by the PPESAuditFileProcessor command line utility (p. 73). Set up a connection to the audit database. Run the PPESAuditFileProcessor command line utility to transfer audit data from text files to an audit database. Use the sample Impromptu catalog to query the audit database. Use the sample reports to assess cube, report and system activity. Enable Auditing In PowerPlay Enterprise - Server Administration, you can enable auditing for servers, cubes and reports. You can control the location where the log files are saved, and the maximum size of the log file. When you enable auditing in PowerPlay Enterprise - Server Administration, activity information is continuously recorded in the ppes_audit.log file. By default, log files are created in the installation_location\ppserver\audit directory. A new log file is opened each time the server is started, or when the size of the log file exceeds the maximum file size setting. The previous file is renamed ppes_auditxxx.log, where xxx is an incremental number representing the generation of the audit log. Steps 1. In PowerPlay Enterprise - Server Administration, select one of the following: • A server, to enable server auditing. • A cube or report, to enable cube or report auditing. 2. From the Edit menu, click Properties, and then click the Settings tab. 3. In the Auditing Level box (Options), select Summary or Detail. 4. Optionally, change the default values for the Maximum size of each file in kilobytes (kB) and Location for audit files settings. 5. Click OK. Set Up an Audit Database You can set up an audit database two ways: • restore the sample backup SQL Server database from the file PPESBackup Use this method if you want to run the sample Impromptu reports or view the Transformer cube that is installed with PowerPlay Web. • run the following database table creation (DDL) scripts available in the installation location\cern\samples\ppwb\audit\scripts folder dbl_udb.sql mssql.sql oracle.sql Use this method if you want to populate the database with real data from PowerPlay Enterprise Server audit logs. Restore the Sample Backup Database You can restore a sample backup SQL Server database for PowerPlay Enterprise Server if you want to run reports on the sample data. To restore the sample database, you must install the samples. Steps 1. Open Microsoft SQL Server. 72 Cognos PowerPlay (R)
Chapter 6: Audit Server Activity 2. Right-click Databases. 3. Click All Tasks. 4. Click Restore Database. 5. Enter a name in the Restore as Database box. 6. Click From Device as the Restore option. 7. Click Select Devices. 8. Click Add. 9. In the Filename box, click the browse button, navigate to installation location\cern\samples\ppwb\audit and click PPESBackup 10. Click OK. The sample PPES audit database is restored. Set Up a Connection String to the Audit Database Before you set up a connection to the audit database, ensure that you configure a namespace. For more information about namespaces, see the Configuration Manager User Guide. You set up a data source name in Access Manager Administration to record the connection string to the audit database. Steps 1. Start Access Manager - Administration. 2. Log on to the namespace. 3. In the Authentication Information pane, right-click the Data Sources folder and select Add Database. 4. In the Name box, type a name for the data source. 5. On the Connection tab, select a database type from the DatabaseType drop-down list. 6. Click Edit, and then enter or verify database definition settings. The database connection string appears in the Connection String box. Record all the text in the connection string after the equal sign (=) so you can enter it, enclosed in double quotes ("), when you run the PPESAuditFileProcessor utility. For example, enclose the following text in double quotes when you specify the -dbconnect argument (p. 74): ^UserID:^ ?Password:;LOCAL;OR;ORACLE@%s@cyborg/%s 7. Click Test to verify that the connection string is valid. 8. When prompted, type a userid and password with read/write access to the database. 9. Click Apply, and then close Access Manager - Administration. PPESAuditFileProcessor Utility Description Run the PPESAuditFileProcessor command line utility to process instances of audit log files generated by PowerPlay Enterprise Server and upload the information to a database. Discussion PowerPlay Enterprise Server can generate audit log files for servers, cubes, or reports. You specify one of the following auditing levels: None, Summary, or Detail. If the file ppes_audit.log exists, it is renamed to ppes_audit.logn when the dispatcher starts. Otherwise, a new ppes_audit.log file is created. A separate log file is created for each server. The PPESAuditFileProcessor processes all instances of ppes_audit.logn into a common database format, for example, Oracle, MS SQL Server, or DB2. Enterprise Server Guide 73
- Page 21 and 22: Chapter 2: Configure Servers Securi
- 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: Chapter 6: Audit Server Activity Us
- Page 75 and 76: Chapter 6: Audit Server Activity Th
- 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
Chapter 6: Audit Server Activity<br />
2. Right-click Databases.<br />
3. Click All Tasks.<br />
4. Click Restore Database.<br />
5. Enter a name in the Restore as Database box.<br />
6. Click From Device as the Restore option.<br />
7. Click Select Devices.<br />
8. Click Add.<br />
9. In the Filename box, click the browse button, navigate to installation<br />
location\cern\samples\ppwb\audit and click PPESBackup<br />
10. Click OK.<br />
The sample PPES audit database is restored.<br />
Set Up a Connection String to the Audit Database<br />
Before you set up a connection to the audit database, ensure that you configure a namespace. For<br />
more information about namespaces, see the Configuration Manager User Guide.<br />
You set up a data source name in Access Manager Administration to record the connection string<br />
to the audit database.<br />
Steps<br />
1. Start Access Manager - Administration.<br />
2. Log on to the namespace.<br />
3. In the Authentication Information pane, right-click the Data Sources folder and select Add<br />
Database.<br />
4. In the Name box, type a name for the data source.<br />
5. On the Connection tab, select a database type from the DatabaseType drop-down list.<br />
6. Click Edit, and then enter or verify database definition settings.<br />
The database connection string appears in the Connection String box.<br />
Record all the text in the connection string after the equal sign (=) so you can enter it,<br />
enclosed in double quotes ("), when you run the PPESAuditFileProcessor utility. For example,<br />
enclose the following text in double quotes when you specify the -dbconnect argument<br />
(p. 74):<br />
^UserID:^ ?Password:;LOCAL;OR;ORACLE@%s@cyborg/%s<br />
7. Click Test to verify that the connection string is valid.<br />
8. When prompted, type a userid and password with read/write access to the database.<br />
9. Click Apply, and then close Access Manager - Administration.<br />
PPESAuditFileProcessor Utility<br />
Description<br />
Run the PPESAuditFileProcessor command line utility to process instances of audit log files<br />
generated by PowerPlay Enterprise Server and upload the information to a database.<br />
Discussion<br />
PowerPlay Enterprise Server can generate audit log files for servers, cubes, or reports. You specify<br />
one of the following auditing levels: None, Summary, or Detail. If the file ppes_audit.log exists, it<br />
is renamed to ppes_audit.logn when the dispatcher starts. Otherwise, a new ppes_audit.log file is<br />
created. A separate log file is created for each server.<br />
The PPESAuditFileProcessor processes all instances of ppes_audit.logn into a common database<br />
format, for example, Oracle, MS SQL Server, or DB2.<br />
Enterprise Server Guide 73
Change language