Cisco Cisco Unified IP Interactive Voice Response (IVR) 8.0(1) Administrator's Guide

Page of 448
 
10-3
Cisco Customer Response Solutions Administration Guide, Release 6.0(1)
 
Chapter 10      Managing Cisco CRS Historical Reporting
Historical Reporting Configuration
Configuring Database Server Limits
To limit the performance impact of historical reporting on a particular CRS server, 
you can configure a maximum number of client/scheduler database connections 
per server. 
The maximum database connection refers to the maximum simultaneous (at any 
time) connections to the historical reporting database from the historical reporting 
client and scheduler. You can configure this value to enhance performance. 
For example, if your Call Center has 10 licensed historical reporting sessions, you 
can set the value in the Maximum DB Connections for Report Client Sessions 
field to be 5. By assigning this value, you will not impact the writing of historical 
reporting data records. However, when you configure a value of 5 (in this 
example), if the historical reporting client or scheduler attempts a 6th connection, 
this attempt will fail, as the maximum database server limit is set to be 5. 
To do so, complete the following steps:
Procedure
Step 1
From the CRS Administration menu bar, choose Tools > Historical Reporting.
The Historical Reporting configuration web page opens, displaying a list of 
Historical Datastore components in your cluster. The following fields are 
displayed in the Database Server Configuration area of the Historical Reporting 
Configuration web page.
Step 2
Enter a value in the Maximum DB Connections for Report Client Sessions field 
next to a Server Name.
Step 3
Click Update
Field
Description
Server Name
The host name or IP Address
 
of the database server.
Maximum DB Connections for 
Report Clients Sessions
The maximum number of client and scheduler connections that can 
access the Historical Reports Database server.
There is a limit of 5 instances of Historical Reporting Client and 
Scheduler based on the load that can be run on each server. The 
historical report client issues an error if you exceed this limit.