1. Cisco Unity Connection Reports Administration Radha Radhakrishnan 10/13/2005

2. Reports Basics Select Report –CUC Admin>Monitoring and Reports>Reports Set Report Parameters Select Output Format Generate Report View/Save Output Refer to Reports Section in CUC Administration and Call Management Guide or User Moves, Adds, and Changes Guide for more info

3. Reports Settings Located at: – CUC Admin>System Settings>Advanced>Reports Data Collection Cycle Time (in Milliseconds) Maximum Age of Data (in Days) Maximum Number of Records in Output Minimum Records to Show Progress Page

4. Tips Narrow search criteria –For fast report generation, Easy to analyze data, Less CPU usage, Less impact on server Use off hours to generate large reports Use Mozilla Firefox for large HTML reports Use off-box client for large HTML/PDF reports Archive reports periodically to prevent data loss

5. Data Flow 1.Conversations store call data into log files. 2.Data Collector gets data from file. 3.Data Collector creates records in Reports DB. 4.User (Client) initiates action to Generate Report. 5.Reports GUI gathers data from the Reports DB. 6.Reports GUI invokes Jasper Reports to format data. 7.Jasper Reports provides the report in user requested form (HTML, PDF). 8.Reports GUI forwards the report to the Client. Conver- sations Data Collector Data File Reports DB 1 2 3 Reports GUI Jasper Reports User 5 4 6 7 8 Server Client

6. Troubleshooting Problems in Report Generation –Understand the error message –Check input parameters and re-Generate Reports –Look for error/exception logs in stdout.log file located at: \Java\jakarta-tomcat-5.0\logs –Set log level for reports component to DEBUG in log4j.properties in folder: \Java\jakarta-tomcat-5.0\webapps\cuadmin\WEB-INF\classes Property - log4j.logger.com.cisco.unity.reports=DEBUG –Verify data using SQL tools (e.g. Query Analyzer) –Refer to UnityRptDb Data Dictionary for DB schema info

7. Troubleshooting Problems in Reports Data Collection –Verify that Reports Data Collector role is active in CUC Server Status application –Verify using CUC Admin that maximum age of data is sufficiently large –Check for data in UnityRptDb views using SQL tools (e.g. Query Analyzer) –Check for data_*.txt files in Logs folder (e.g. \Logs) –Check for errors in diag_CuScavenger*.txt in the Logs folder –Activate diagnostics logging for Unity Scavenger service using Cisco Unity Tools Depot –Check config settings in UnityDirDb.vw_ConfigurationValue for: System.Reports.DataCollection.CuCsMgr_LastDataFile System.Reports.DataCollection.Notifier_LastDataFile

8. Q & A