Packaged CCE 2000 Agents Deployment
Single-stage Configurations
Prerequisite:
Upload CA Certificates or import Self-signed Certificates of upgraded components.
The following table outlines the post-upgrade configurations required for components.
Note |
|
Sequence |
Task |
---|---|
1 |
|
2 |
|
3 |
Configure External HDS (optional) |
4 |
|
5 |
Configure Cisco Unified Customer Voice Portal Reporting Server (optional) |
6 |
|
7 |
Email and Chat (optional) |
8 |
|
9 |
|
10 |
|
11 |
|
12 |
|
13 |
|
14 |
Update Inventory
After you perform a Technology Refresh upgrade, sign in to the Unified CCE Administration of Principal AW on the destination server. On the Inventory page, you can update the IP address or hostname, and choose to rebuild Virtual Machines (VMs) for the upgraded solution components. For more information, see Update IP Address or Hostname.
Note |
|
Configure CCE Components
The following table outlines the configuration tasks required for CCE components in Packaged CCE 2000 Agent deployments.
Sequence |
Task |
---|---|
1 |
|
2 |
Configure Cisco SNMP Setup for Rogger (optional) |
Configure External HDS
The following table outlines the configuration tasks required for External HDS in Packaged CCE deployments.
Sequence |
Task |
---|---|
1 |
|
2 |
Configure Customer Voice Portal
Note |
The CVP configurations are site specific. Side A and Side B configurations per site must be the same. |
Configuration Tasks |
---|
For CVP security details, see Configuration Guide for Cisco Unified Customer Voice Portal at https://www.cisco.com/c/en/us/support/customer-collaboration/unified-customer-voice-portal/products-installation-and-configuration-guides-list.html. |
Solution Synchronization and Cutover
Synchronize Source Server to the Destination Server
During the staging and testing of the newer 12.6(x) systems, the existing 12.0(x)/12.5(x) production servers continue to process calls. On the day of the cutover, the data in the 12.6(x) staged servers can be updated with that of the production server, by running the EDMT tool on Logger, BA, AW, and HDS database on 12.6(x) staged systems.
This updates the database with production server schema version. However, due to the 12.6(1) database schema version being different from its base 12.0(1) or 12.5(1) version, the updated database is incompatible with 12.6(1). The administrator would have to manually use upgrade.exe utility to upgrade the database schema before starting the CCE Logger or Distributor service.
The utility is present in the icm\bin folder, and needs to be run against each of the database that was updated from the production server.
Perform the following steps to use the Upgrade.exe Utility:
<Install Drive>: \icm\bin>upgrade.exe -s <Server Name> -d <Database name> -dt <Database Type> -i <Instance Name> where <Database Type> - can be either " logger" or "hds", depending on the database that requires the schema to be upgraded.
For Example C:\icm\bin>upgrade -s PRGR-A -d abc_sideA -dt logger -i abc
# - The value as stored in columns Major, CCMinor, and AWMinor of Version table in the CCE database.
Note |
|
Synchronize Components on the Destination Server using Inventory
Note |
You can do a full synchronization of all components (using sync-all) from Principal AW; however it cannot be initiated after the cutover is completed. |
Procedure
Step 1 |
Navigate to . |
Step 2 |
On the banner message, click sync-all. |
Step 3 |
Click Next to confirm initiating full synchronization. Full synchronization may take several minutes. |
Step 4 |
After the successful initiation of synchronization, click Done. If initiation of synchronization fails, an error message appears. Click Close to exit and fix the error as required. |
Complete Upgrade on the Destination Server
Procedure
Step 1 |
Navigate to the . |
Step 2 |
On the banner message, click cutover. |
Step 3 |
Click Next to initiate validations for cutover.
|
Step 4 |
After the successful completion of cutover, click Done. |