Cisco Cisco Unified Contact Center Enterprise 9.0(2) Release Notes

Page of 90
19
Release Notes for Cisco IPCC/ICM Enterprise & Hosted Editions Release 7.0(0) Installer Update C November 24, 2008
New and Changed Information
For specifics on the hardware (including RAID) requirements, and on Windows operating system 
requirements
, refer to the Cisco ICM/IPCC Enterprise and Hosted Edition Hardware and System 
Software Specification (Bill of Materials)
.
Reporting
  •
  •
  •
  •
  •
  •
  •
  •
  •
  •
  •
WebView Deployment and Installation
WebView is no longer installed as an option on a Distributor AW, but is its own entity that can be 
installed on a separate server, and pointed at the Distributor AW. The WebView database remains on a 
Distributor AW with the configuration (awdb) and historical databases (hds). The WebView Installation 
and Administration Guide for Cisco ICM/IPCC Enterprise & Hosted Editions
 and the Cisco ICM/IPCC 
Enterprise and Hosted Edition Hardware and System Software Specification (Bill of Materials)
 have 
been updated to describe how to deploy WebView given this new option, both procedurally, as well as 
from a planning perspective. WebView continues to communicate with all databases via ODBC. The 
former dblib-based backup connection functionality has been removed.
WebView can still be installed co-resident with a Distributor AW and is fully supported in that 
deployment. However, by separating WebView from the Distributor, one can deploy more WebView 
servers without adding more databases—and therefore support more total WebView users in the 
enterprise.
Stability and Serviceability Improvements
An additional service is now installed with WebView called the "Cisco ICM Jaguar WatchDog" and it 
will appear in the Services control panel. This process monitors the health of the Jaguar service, and by 
default will restart Jaguar if it detects a problem or finds the service has been stopped.
Logging and messaging have been improved in a number of areas within WebView. If a report query 
results in a SQL error, the actual error text is now returned to the user rather than a blank report. This 
error lets users know there was a problem and gives them information that can be passed along to 
technical support.