About this Document
This document provides installation instructions for Unified CCE 12.5(1) ES87. It also contains a list of Unified CCE issues resolved by this engineering special. Review all installation information before installing the product. Failure to install this engineering special as described can result in inconsistent Unified CCE behavior.
This document contains these sections:
In the Product Alert Tool,
you can set up profiles
to receive email notification of new Field Notices,
Product Alerts, or End of Sale information for your selected products.
The Product Alert Tool is available at
https://www.cisco.com/cisco/support/notifications.html.
This engineering special needs to be applied on Administration and Data Servers, prior to changing a Packaged CCE system to its equivalent Unified CCE deployment type. For example, to change a Packaged CCE 2000 Agents deployment to Unified CCE 2000 Agents deployment. Likewise, for 4000 and 12000 agents deployment types.
Unified CCE 12.5(1) ES87
This section lists the Unified CCE components on which you can and cannot install this engineering special.
You can install Unified CCE 12.5(1) ES87 on these Unified CCE components:
Do not install this engineering special on any components other than the following:
§ Download the 32 bit tomcat installer zip from http://archive.apache.org/dist/tomcat/tomcat-9/. Download the same version that is displayed when version.bat was run.
§ Unzip the installer to a temp folder.
§ Copy tomcat-util-scan.jar from the <temp>\apache-tomcat-9.0.xx\lib location to <ICM HOME>\tomcat\lib.
§ Using the ICM/CCE Service Control, start Apache Tomcat 9 service.
Note: Remove patches in the reverse order of their installation. For example, if you installed patches 3, then 5, then 10 for a product, you must uninstall patches 10, 5, and 3, in that order, to remove the patches from that product.
This section provides a list of significant Unified CCE defects resolved by this engineering special. It contains these subsections:
Note: You can view more information on and track individual Unified CCE defects using the Cisco Bug Search tool, located at: https://bst.cloudapps.cisco.com/bugsearch/search?null.
This section lists caveats specifically resolved by Unified CCE 12.5(1) ES87.
Caveats in this section are ordered by UNIFIED CCE component, severity, and then identifier.
| Identifier | Severity | Component | Headline |
|---|---|---|---|
| CSCvu25431 | 6 | dbconfig | SytemAdmin and ConfigAdmin Role update not happening during startup. |
| CSCvw62772 | 3 | web.config.api | DisableAutoSync job not running for deployment type change from UCCE to PCCE in 12.0, 12.5 and 12.6 |
| CSCvw17119 | 4 | web.config.ui | Deployment type change from PCCE to non-PCCE deployments should warn about CVP / VVB config removal |
Caveats are ordered by severity then defect number.
Defect Number: CSCvw62772
Component: web.config.api
Severity: 3
Headline: DisableAutoSync job not running for deployment type change from UCCE to PCCE in 12.0, 12.5 and 12.6
Symptom:
Either during PCCE fresh install or deployment type change from non-PCCE to PCCE, DisableAutoSync task disables the configuration change via finesse cfadmin UI on all Primary Finesse machines. This task is running after inventory is auto populated by inventory scanner but is unable to invoke finesse api as finesse credentials are not yet configured in PCCE. This task should re-try, until the inventory setup is complete, but it is exiting after only one attempt.
Conditions:
UCCE to PCCE deployment type change or PCCE fresh install.
Workaround:
Post complete inventory setup. Recycle tomcat server on AW machine. Startup task will re-run DisableAutoSync and finesse API call will take place fine.
Further Problem Description:
Customers can easily ignore this problem as it is not impacting any functionality. In PCCE system, it is recommended to use CCEAdmin UI to configure data for Finesse instead of using Finesse CfAdmin UI.
Due to this issue cfadmin UI is not disabled and admins can still modify configuration directly on Finesse instead of using CCEAdmin.
Defect Number: CSCvw17119
Component: web.config.ui
Severity: 4
Headline: Deployment type change from PCCE to non-PCCE deployments should warn about CVP / VVB config removal
Symptom:
Deployment type change does not inform about CVP and VVB configuration being removed from the AW database
Conditions:
When changing deployment type from Packaged CCE 2000, 4000 or 12000 Agent deployment to a non-Packaged CCE deployment type like UCCE 2000, UCCE 4000 or UCCE 12000 Agents deployment.
Workaround:
None
Further Problem Description:
Defect Number: CSCvu25431
Component: dbconfig
Severity: 6
Headline: SytemAdmin and ConfigAdmin Role update not happening during startup.
Symptom:
SytemAdmin and ConfigAdmin Role update not happening during startup.
Conditions:
system should be in Local Auth Administrator
create Users using Administrator Gadget but do not assign any roles.
Using Active directory Users and Computers tools add some of the User to Setup Security domain group under instance OU and some of the Users to config Security domain group under instance OU.
restart the tomcat after that.
Workaround:
Add the roles to user using Administrator and role gadgets
Further Problem Description:
You can access current Cisco documentation on the Support pages at the following sites:
To provide comments about this document, send an email message to the following address:
contactcenterproducts_docfeedback@cisco.com
We appreciate your comments.
Cisco.com is a starting point for all technical assistance. Customers and partners can obtain documentation, troubleshooting tips, and sample configurations from online tools. For Cisco.com registered users, additional troubleshooting tools are available from the TAC site.
Cisco.com provides a broad range of features and services to help customers and partners streamline business processes and improve productivity. Through Cisco.com, you can find information about Cisco and our networking solutions, services, and programs. You can also resolve technical issues with online technical support and download software packages. Valuable online skill assessment, training, and certification programs are also available.
Customers and partners can self-register on Cisco.com to obtain additional personalized information and services. Registered users can order products, check on the status of an order, access technical support, and view benefits specific to their relationships with Cisco.
The Cisco TAC site is available to all customers who need technical assistance with a Cisco product or technology that is under warranty or covered by a maintenance contract.
If you have a priority level 3 (P3) or priority level 4 (P4) problem, contact TAC by going to https://www.cisco.com/c/en/us/support/index.html.
P3 and P4 level problems are defined as follows:
In each of the above cases, use the Cisco TAC site to quickly find answers to your questions.
If you cannot resolve your technical issue by using the TAC online resources, Cisco.com registered users can open a case online by using the TAC Case Open tool at the following site: https://mycase.cloudapps.cisco.com/create/start/
If you have a priority level 1(P1) or priority level 2 (P2) problem, contact TAC by telephone and immediately open a case. To obtain a directory of toll-free numbers for your country, go to the following sites:
P1 and P2 level problems are defined as follows: