Tomcat Update
Perform the following procedure to update Tomcat version on Call Server, Reporting Server, Operations Console, VXML Server, and Web Services Manager (WSM). For example, you can update from Tomcat version 7.0.24 to 7.0.47.
Before you begin
- Save a backup copy of the
Tomcat folder from the following locations:
-
For Call Server: C:\Cisco\CVP\CallServer
-
For Reporting Server: C:\Cisco\CVP\CallServer
-
For VXML Server: C:\Cisco\CVP\VXMLServer
-
For Operations Console: C:\Cisco\CVP\OPConsoleServer
-
For WSM: C:\Cisco\CVP\wsm\Server
Note
Save a backup copy of the Tomcat folder on a directory path that is different from the default destination folder (C:\Cisco\CVP).
-
-
Rename the Tomcat folders with a different name. For example: Tomcat_backup.
Procedure
Step 1 |
Stop the Tomcat service. |
||
Step 2 |
Remove the Tomcat folder from the following locations:
|
||
Step 3 |
Download the Tomcat binary apache-tomcat-7.0.47-windows-x86.zip file from the following location: https://archive.apache.org/dist/tomcat/tomcat-7. |
||
Step 4 |
Right-click the apache-tomcat-7.0.47-windows-x86.zip file and extract the files to a known location on the local drive. |
||
Step 5 |
Rename the folder apache-tomcat-7.0.47 to Tomcat. |
||
Step 6 |
Copy the Tomcat folder to the following locations:
|
||
Step 7 |
Copy the webapps folder from the Tomcat_backup folder (…\Tomcat_backup\webapps) and paste it in the following folder locations:
|
||
Step 8 |
Do not replace the existing jar files. Copy only the missing jar files from the Tomcat_backup folder (..\Tomcat_backup\lib) to the following locations.
|
||
Step 9 |
Update the new server.xml files with the existing properties from the backed up server.xml files. |
||
Step 10 |
For Tomcat upgrade of WSM, ensure the jaas.conf from the backed up Tomcat folder is copied to the new Tomcat/conf folder.
|
||
Step 11 |
Back up connector.property that was created before starting the process from:.
|
||
Step 12 |
Restore these to:
|
||
Step 13 |
Restart the following Tomcat services:
|
||
Step 14 |
Ensure that the CVP Diag portal is up and running. |
||
Step 15 |
Check Tomcat and CVP logs for any exceptions. |