- Download the Tomcat Service Installer (http://tomcat.apache.org/download-70.cgi)
- Run the installer with 'Run as Administrator'
- Click NEXT on the initial screen
- Click I AGREE on the License Agreement screen
- Select NORMAL for the install type on the Choose Components screen and click NEXT
- On the Configuration screen, ensure to select UNIQUE ports for Tomcat. Click NEXT
- On the Java Virtual Machine screen, navigate to the JRE directory within the SC directory (i.e. C:\Program Files (x86)\CA\SC\JRE\1.7.0_10) and click NEXT
- On the Choose Install Location screen, either leave the default install directory or choose an alternate location and click NEXT
- Click FINISH on the last screen to complete the Tomcat install and start the Tomcat service
- Open the Services Control Panel and verify that the Apache Tomcat 7.0 service is listed and started. If desired, change start-up type from Manual to Automatic
Deploying CA SDM 12.9 Health Servlet
- Copy NX_ROOT\SAMPLES\HealthServlet\HealthServlet.WAR to the Apache Tomcat Webapps directory (i.e. C:\Program Files (x86)\Apache Software Foundation\Tomcat 7.0\webapps)
- Via the Services Control Panel, restart the Apache Tomcat 7.0 service. The HealthServlet Tomcat application will be deployed. This can be verified by checking to see if the Tomcat HealthServlet Webapps directory is created (i.e. C:\Program Files (x86)\Apache Software Foundation\Tomcat 7.0\webapps\HealthServlet).
After the successful deployment, the Health Servlet is ready to perform health checks. It includes checking the status of the SLUMP and health of the CA SDM processes that are defined in the health.xml file (C:\Program Files (x86)\Apache Software Foundation\Tomcat 7.0\webapps\HealthServlet\WEB-INF\classes). Refer to page 316 of the CA SDM 12.9 Implementation Guide for further information on modifying the processes monitored by the Health Servlet.
- Via a web browser, navigate to the Tomcat HealthServlet URL (i.e. http://<server-name>:<port>/HealthServlet/GetHealth). Gives an "OK" or "NOT OK" message to determine if there is a problem.
**WARNING** make sure the HealthServlet?URL is protected - refer to TEC611801 for additional details