Customer followed steps documented here but for upgrade to Tomcat 8.5.57
https://techdocs.broadcom.com/content/broadcom/techdocs/us/en/ca-enterprise-software/business-management/ca-service-management/14-1/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.html
After this, in pdm_tomcat_rest.log there are errors/warnings about missing .jar files in ../java/lib/CXF directory :
org.apache.tomcat.util.scan.StandardJarScanner processURLs
WARNING: Failed to scan [file:/C:/Program%20Files%20(x86)/CA/Service%20Desk%20Manager/java/lib/CXF/endorsed/geronimo-jaxws_2.2_spec-1.1.jar] from classloader hierarchy
java.io.FileNotFoundException: C:\Program Files (x86)\CA\Service Desk Manager\java\lib\CXF\endorsed\geronimo-jaxws_2.2_spec-1.1.jar (The system cannot find the path specified)
at java.util.zip.ZipFile.open(Native Method)
Release : 17.1
Component : Svc Desk Web Services
Tomcat upgrade to 8.5.57 :
- Follow steps 1 thru 5 from the 14.1 doc page referenced:
https://techdocs.broadcom.com/content/broadcom/techdocs/us/en/ca-enterprise-software/business-management/ca-service-management/14-1/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.html
+
- Rename all "conf" folders to "conf.orig" for ALL Tomcats (bopcfg\www\CATALINA_BASE[_XXX] )
- Run pdm_configure (Do NOT enable the option to start the services)
- A new conf folder will be available in 3 of the 5 Tomcats.
- Copy the new conf folder from CATALINA_BASE to CATALINA_BASE_FS and CATALINA_BASE_REST
- On the 2 copied conf folders, delete the file catalina.properties (FS and REST)
- Run pdm_configure again (You can enable the option to start up the services)
Note: If in the environment has been made any updates to any of the files in the conf folder after SDM created it, then those same changes needs to be redone on the new files.
Note: As always test the Tomcat upgrade procedure in your Test environment first and contact support for any clarification or further help needed.