How to have debug logs of ENCServer component ?
search cancel

How to have debug logs of ENCServer component ?

book

Article ID: 221369

calendar_today

Updated On:

Products

CA Client Automation - IT Client Manager CA Client Automation

Issue/Introduction

Logs for encserver (manager, server and/or router) are in files CA\DSM\logs\TRC_CF_ENCSERVER*.log
 
By default the log level is ERROR.
How to increase this log level to have details logs ?

Environment

Client Automation - All Versions

Resolution

1- Edit the file C:\Program Files (x86)\CA\DSM\ENC\Tomcat\webapps\encServer\WEB-INF\log4j.xml and update the lines in bold

<?xml version="1.0" encoding="UTF-8" ?>
<!DOCTYPE log4j:configuration SYSTEM "log4j.dtd">

<log4j:configuration xmlns:log4j="http://jakarta.apache.org/log4j/">

    <appender name="mainLog" class="org.apache.log4j.RollingFileAppender">
        <param name="maxFileSize" value="60000KB" />
        <param name="maxBackupIndex" value="9" />
        <param name="File"   value="..\\logs\\TRC_CF_ENCSERVER.log" />
        <layout class="org.apache.log4j.PatternLayout">
            <param name="ConversionPattern" value="%d{dd MMM yyyy HH:mm:ss,SSS} %t %x %m %n"/>
        </layout>
    </appender>

   <root>
    <priority value ="ALL" />
      <appender-ref ref="mainLog" />
   </root>

</log4j:configuration>

2- Restart enccserver

caf stop encserver
caf start encserver

Additional Information

Possible values for priority are :

TRACE : The TRACE Level designates finer-grained informational events than the DEBUG.
DEBUG : The DEBUG Level designates fine-grained informational events that are most useful to debug an application.
INFO : The INFO level designates informational messages that highlight the progress of the application at coarse-grained level.
WARN : The WARN level designates potentially harmful situations.
ERROR : The ERROR level designates error events that might still allow the application to continue running.
FATAL : The FATAL level designates very severe error events that will presumably lead the application to abort.
ALL : The ALL has the lowest possible rank and is intended to turn on all logging.
OFF : The OFF has the highest possible rank and is intended to turn off logging.