Cisco Cisco IPCC Web Option Release Note
Cisco Unified ICM/Unified CC Enterprise & Hosted Editions, Release 7.2(x)
Rev. 1.30
Hardware and System Software Specification
0BOverview
©2010 Cisco Systems, Inc.
1
1 Overview
This Hardware and System Software Specification was formerly known as the ICM/IPCC Bill of Materials (BOM). It has
been renamed to better reflect its content and purpose. That purpose is to specify the hardware and system software
compatible with, and required for, the Cisco Unified Intelligent Contact Management (Unified ICM) and Cisco Unified
Contact Center (Unified CC) product
been renamed to better reflect its content and purpose. That purpose is to specify the hardware and system software
compatible with, and required for, the Cisco Unified Intelligent Contact Management (Unified ICM) and Cisco Unified
Contact Center (Unified CC) product
This document is applicable to both the Enterprise and Hosted options of the Unified ICM and Unified Contact Center
solutions.
solutions.
for Release 7.2(1) and subsequent 7.2(x) Maintenance Releases (MR).
The information contained herein is intended for use by Certified Partners and Cisco sales and system engineers, for pre-
sales hardware planning and third-party software selection, as well as for incremental system updates. In all cases, the
reader is assumed to be familiar with the Unified ICM /Unified CC product at an overview level, and to understand high
level deployment models and essential application server types such as Logger and PG.
sales hardware planning and third-party software selection, as well as for incremental system updates. In all cases, the
reader is assumed to be familiar with the Unified ICM /Unified CC product at an overview level, and to understand high
level deployment models and essential application server types such as Logger and PG.
Document content will be updated periodically for technical clarification and to align with subsequently qualified hardware
and third- party software. Document updates are typically synchronized with minor and maintenance releases and include
updated support policy details for Microsoft Service Pack support qualified for the release. Note that while newly
available hardware may be added to this document following initial publication, existing hardware server specifications
originally published for a specific configuration will not be rendered obsolete by any subsequent release 7.2(x)
specification update.
and third- party software. Document updates are typically synchronized with minor and maintenance releases and include
updated support policy details for Microsoft Service Pack support qualified for the release. Note that while newly
available hardware may be added to this document following initial publication, existing hardware server specifications
originally published for a specific configuration will not be rendered obsolete by any subsequent release 7.2(x)
specification update.
Release Terminology: Major, Minor, and Maintenance Releases
Release 7.2(1) is a minor software release for the Enterprise and Hosted editions of Unified ICM and Unified CC. A minor
release includes incremental new functionality in addition to software defect fixes, delivered in an automated patch
installer that includes full rollback capability. Release 7.2(1) is the second minor release update to major Release 7.0(0).
release includes incremental new functionality in addition to software defect fixes, delivered in an automated patch
installer that includes full rollback capability. Release 7.2(1) is the second minor release update to major Release 7.0(0).
Note that minor Release 7.2(1) and subsequent maintenance releases to 7.2(1) are referenced generically in this document
as Release 7.2(x)—except where a distinction is necessary.
as Release 7.2(x)—except where a distinction is necessary.
Unified ICM /Unified CC 7.0(x) or 7.1(x) installation is a prerequisite to 7.2(1) and subsequent MRs.
Hardware, System Software
To simplify mapping of the hardware server configurations across various deployments, server hardware is identified as a
“server class” for both MCS and vendor-sourced (“generic”) servers. A server class contains one or more hardware types,
based on category of processor family, memory, and hard drive configuration appropriate for the specified application.
Server classes are detailed in
“server class” for both MCS and vendor-sourced (“generic”) servers. A server class contains one or more hardware types,
based on category of processor family, memory, and hard drive configuration appropriate for the specified application.
Server classes are detailed in
, and Capacity Sizing
Hardware and associated system software are specified by Unified ICM/Unified CC system server configuration with
consideration for both the overall deployment model and the specific server software component configuration. Capacity
sizing is an integral factor in proper requirement specification. Where requirements are tiered by system sizing, defined
operating conditions and representative sizing thresholds (such as the maximum number of supported agents) are indicated.
Special consideration is provided for installations being upgraded to Release 7.0(0) on existing hardware. A summary of
system configuration boundaries is also provided, followed by specific Unified ICM /Unified CC solution deployments and
the applicable corresponding hardware and software requirements, by server node type and capacity range. Each
configuration is prefaced with a representative set of primary operating conditions on which sizing is based, with
exceptions and special considerations called out under applicable server node.
consideration for both the overall deployment model and the specific server software component configuration. Capacity
sizing is an integral factor in proper requirement specification. Where requirements are tiered by system sizing, defined
operating conditions and representative sizing thresholds (such as the maximum number of supported agents) are indicated.
Special consideration is provided for installations being upgraded to Release 7.0(0) on existing hardware. A summary of
system configuration boundaries is also provided, followed by specific Unified ICM /Unified CC solution deployments and
the applicable corresponding hardware and software requirements, by server node type and capacity range. Each
configuration is prefaced with a representative set of primary operating conditions on which sizing is based, with
exceptions and special considerations called out under applicable server node.
Cisco strives to enhance the usefulness of this document by ensuring accurate detailed technical information backed by an
extensive in-house testing and qualification effort. We have increased the amount of sizing and system boundary
extensive in-house testing and qualification effort. We have increased the amount of sizing and system boundary
1
See the Note on Cisco Product Names on page 4.
2
System software consists of the operating system, database server, and other 3
rd
party applications.