Health Servlet Tomcat Configuration

Products

• CA Service Management - Service Desk Manager
• CA Service Desk Manager

Issue/Introduction

The following article clarifies on the Tomcat configuration aspect, namely if one can share the existing Tomcat implementation that comes with SDM with the Health Servlet component.

Environment

Release:  17.2 or higher
CA Service Desk Manager (Advance Availability)

Cause

Implementing the Health Servlet component on the existing Service Desk Tomcat install, that is, to place the Health Servlet under NX_ROOT\bopcfg\www\CATALINA_BASE, is not supported.

Resolution

The existing documentation indicates that the Health Servlet should be installed on a separate instance of Tomcat server than CA SDM.

Running the Health Servlet on the same Tomcat instance as SDM defeats the purpose of the Health Servlet to assist in monitoring the SDM Server and processes.  Under such conditions, a loss of SDM Services may not be reliably reported by the Health Servlet as such a loss may include SDM Tomcat, which would also adversely impact the Health Servlet if it was deployed in such a manner.

Best practice is to always deploy a new Tomcat instance on its own port to run the Health Servlet.  It is not recommended to deploy the Health Servlet on any Tomcat instance provided by SDM, even under testing conditions.  

Additional Information

KB Article 4230 touches on the notion that the Health Servlet is intended for Advance Availability installations only.