Webservices stopped working after updating Apache Tomcat
search cancel

Webservices stopped working after updating Apache Tomcat


Article ID: 272478


Updated On:


CA Service Desk Manager CA Service Management - Service Desk Manager


Updated the version of Apache Tomcat on the Service Desk servers to resolve some security vulnerabilities.  Once the upgrade was completed, however, anything that  would use the REST/Web Services to open tickets has stopped working and get a 404 error from the POST calls to open tickets. 


Release : 17.3

CA Service Desk Manager


Internal configuration needs to be redone as part of Tomcat update


- Follow steps 1 thru 5 from the "Install and Configure Apache Tomcat" (steps may have already been done, but please review this step to confirm)

- Rename all "conf" folders to "conf-org" for ALL Tomcats (bopcfg\www\CATALINA_BASE[_XXX] )

Example:  Renaming:


Change the folder names to:


- 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.  The conf folder of interest will be located in "\bopcfg\www\CATALINA_BASE"

- 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).  The files that need to be deleted are:


- Run pdm_configure again (You can enable the option to start up the services)

Once done, please test if REST Web Services on SDM are operational.

Additional Information

See also KB Article 19999 for additional information on 404 errors with REST