For the current version of CA Service Desk Manager (CA SDM) in the environment, you may have upgraded the version of Tomcat.
For example, when installing CA SDM 14.1 in a clean environment (not an upgrade), Tomcat 7.0.23 is installed and the NX.env file would include statements like these:
@NX_TOMCAT_INSTALL_DIR=C:/Program Files (x86)/CA/SC/tomcat/7.0.23
@NX_TOMCAT_INSTALL_DIR_CAWF=C:/Program Files (x86)/CA/SC/tomcat/7.0.23
Likewise, when installing CA SDM 17.1 in a clean environment (not an upgrade), Tomcat 8.5.6 is installed and the NX.env file would include statements like these:
@NX_TOMCAT_INSTALL_DIR=C:/Program Files (x86)/CA/SC/tomcat/8.5.6
@NX_TOMCAT_INSTALL_DIR_CAWF=C:/Program Files (x86)/CA/SC/tomcat/8.5.6
You may have upgraded the Tomcat version in your environment separately after installing CA SDM.
For example, in your CA SDM 14.1, you may have upgraded Tomcat to version 8.5.16 by following the instructions in the documentation on this page: https://docops.ca.com/ca-service-management/14-1/en/implementing/implementing-ca-service-management-14-1/step-4-install-or-upgrade/implementing-ca-service-desk-manager/how-to-install-ca-sdm/step-3-install-other-components/install-and-configure-apache-tomcat-8-5-16
A common reason for upgrading Tomcat is to avoid Tomcat vulnerabilities that have been discovered in the various versions of Tomcat.
If CA SDM is upgraded to a later version, is Tomcat upgraded to the latest supported version?
CA Service Desk Manager on Windows
No, not necessarily.
For upgrades, the Tomcat version included in the target CA SDM version would be installed in a separate directory and any existing Tomcat directory for the previous CA SDM version would not be deleted.
So, for example, if you had upgraded Tomcat from version 7.0.23 to version 8.5.16 in your CA SDM 14.1 environment, then when you upgrade 14.1 to 17.1, the 8.5.16 directory would remain in-place under the CA Service Desk manager installation path (i.e. $NX_ROOT) and a new directory for Tomcat 8.5.6 would be created since 8.5.6 is the version of Tomcat that is included with CA SDM 17.1.
After the upgrade from 14.1 to 17.1, you should ensure that the NX_TOMCAT_INSTALL_DIR variable in the $NX_ROOT\NX.env file refers to the desired Tomcat version and restart the CA SDM service if it is already up and running..
You could also upgrade Tomcat 8 to the latest/current Tomcat 8 version. On 06-March-2019, the current/latest version of Tomcat is 8.5.38.
For more information about upgrading Tomcat separately, please see knowledge article KB000107928 ( upgrading Apache Tomcat to avoid known fixed vulnerabilities ) which answers the question: "Are the Tomcat releases listed in the CA Service Management Supportability Matrix the only releases that are supported?"
On 06-March-2019, Tomcat 8 versions can be downloaded from https://archive.apache.org/dist/tomcat/tomcat-8/