The document provides the Java support, compatibility, and major upgrade steps on Customer Voice Portal (CVP) and Call Studio.
Cisco recommends that you have knowledge of these topics:
The information in this document is based on these software and hardware versions:
Call Studio Version 8.5 and later
The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, make sure that you understand the potential impact of any command.
Support and Compatibility
CVP Call Studio
Run the supported default Java Runtime Environment (JRE) version as mentioned in this table:
CVP Studio Version
Default JRE Versions
Note: A JRE upgrade is not supported on Call Studio. This limitation is due to the eclipse and plugins that do not support a later version of JRE.
The current list of supported JRE versions is shown in this table:
Default JRE Versions
Additional JRE Versions Tested for Support
Note: Check the supported JRE version before you upgrade the current installation. Any other versions (earlier or later) that are not listed in the previous table are not supported.
Use the JREUpdate.bat script in order to complete a minor update of the JRE version on your Unified CVP Server. For example, the script does a minor update from JRE version 1.6.0_24 to 1.6.0_81.
Note: The script does not support a major upgrade of JRE versions. For example, the JREUpdate.bat script cannot complete an upgrade from JRE version 1.6.0_81 to 1.7.0_45.
Download and install the preferred Java Development Kit (JDK) version on your personal computer.
Copy the JRE folder available within the installed JDK to a known location on the Unified CVP Server.
The JRE folder is available inside the root folder of the JDK installation. For example, C:\JRE or C:\jdk1.7.0_67\jre.
Unzip the JREUpdate.zip contents to a known location on your CVP Server.
For example, C:\Cisco\CVP\bin.
In order to update the JRE version on the Unified CVP Server, run this script from the command prompt:
C:\Cisco\CVP\bin >JREUpdate.bat apply C:\JRE
The script executes and the CVP JRE gets updated to the new version. Ensure that the script output displays the updated JRE version.
The JREUpdate.bat script takes a backup of the old JRE at C:\Cisco\CVP\jre.old.
In order to revert to the previous backup version of JRE, run this script from the command prompt:
Note: The CVP JRE contains JConsole tool. After a successful update to the JRE, the tool is available inside the backup folder only - jre.old/bin. In case you need to debug issues, use the tool directly from within the backup folder.
Major Upgrade of JRE
In order to upgrade Java (for example, from version 1.6.x to 1.7.y), complete this procedure.
This tool is created in order to upgrade CVP 10.0, 9.0, and 8.5 JRE from its current version to version 1.7.0_45. The tool is tested on CVP servers with only CVP services running. If there are any other services that use CVP JRE (such as C:\Cisco\CVP\jre), then this tool might not be able to upgrade properly and might leave the system in an incorrect state.
Ensure that apart from CVP services, no other service uses CVP JRE (located under C:\Cisco\CVP\jre). It is highly recommended to take a backup of the old CVP JRE before you run this tool.
Download the JREUpdate.zip file and unzip it in any directory on the CVP machine.
Under the unzipped directory, there should be a JRE directory, JREUpdate.cmd file, and a readme.txt file.
Enter this command in order to check the current CVP JRE version.
In order to upgrade CVP JRE, launch JREUpdate.cmd.
Once the batch file execution is finished, enter this command in order to check the CVP JRE version:
You should see output as shown here:
java version "1.7.0_45"
Java(TM) SE Runtime Environment (build 1.7.0_45-b18)
Java HotSpot(TM) Client VM (build 24.45-b08, mixed mode, sharing)
The old JRE should be moved to jre.old in the C:\Cisco\CVP folder.
Note: You should always have the same version of Call Studio as CVP. Even though Call Studio might have an earlier version of JRE, it should work fine if CVP has a later version of JRE.
In order to check compatibility (due to customer-owned Java), this needs to be tested in the lab before deployment.
Stop the CVP services.
Grab the old CVP JRE and place it in the c:\cisco\cvp folder.