Managing Servers › Tomcat Logging

Tomcat Logging

CA SDM uses a separate log4j.properties file for its web components such as Servlets and PDM_RPC. Support Automation, CMDB Visualizer, and REST also have a separate log4j.properties file. Starting or stopping Tomcat logging does not require you to recycle the Tomcat daemons.

The following list describes how the log4j.properties files of CA SDM components differ:

• CA SDM monitors the log4j.properties in the NX_ROOT\site\cfg and in the NX_ROOT\bopcfg\www\CATALINA_BASE\webapps\CAisd\WEB-INF for changes.
• Support Automation monitors the log4j.properties in the NX_ROOT\bopcfg\www\CATALINA_BASE_SA\webapps\SupportAutomation\WEB-INF.
• CMDB Visualizer monitors the cmdbvisualizerlogging.properties in the NX_ROOT\bopcfg\www\CATALINA_BASE_VIZ\webapps\CMDBVisualizer\WEB-INF\classes.
• REST monitors the rest.log4j.properties in the NX_ROOT\site\cfg.

Use the pdm_log4j_config utility only for changing variables in the log4j.properties, cmdbvisualizerlogging.properties, and rest.log4j.properties files. You cannot use the pdm_log4j_config utility to modify the polling interval.

CA SDM checks the log4j properties files for any changes periodically. Configure the time interval by modifying the NX_LOG4J_REFRESH_INTERVAL variable in the NX.env file.