How to Enable Debug Tracing on JFM Communications from CA 7

Products

• iDash Workload Automation

Issue/Introduction

At times, there could be a discrepancy in iDash Workload Automation where an alarm may be generated or a status is not shown correctly when receiving job information from  CA 7 .  Typically, this is due to an issue with a delay in iDash receiving job information from CA 7.  Enabling the below debug levels will allow Broadcom Support to view the full XML that is sent over from CA7 to evaluate the information.

Environment

iDash 12.x on all platforms

WA CA 7 Edition

Resolution

Navigate to your $IDASH_HOME/etc (*NIX) or %IDASH_HOME%\etc (Windows) directory and open the log4j.conf file.  

Add the following lines to the end of the file:

log4j.logger.com.ca.idash.core.servlet.JFMEventListener=DEBUG,event

log4j.logger.com.ca.idash.core.instance.ca7.jfm.JfmQueryManager=DEBUG,event

log4j.appender.event=org.apache.log4j.RollingFileAppender

log4j.appender.event.File=${idash.home}/log/event.log

log4j.appender.event.MaxFileSize=20MB

log4j.appender.event.MaxBackupIndex=20

log4j.appender.event.threshold=DEBUG

log4j.appender.event.layout=org.apache.log4j.PatternLayout

 

log4j.appender.event.layout.ConversionPattern:%d{yy-MM-dd HH.mm.ss} [%5p] %t: %m%n

 

Save the file and restart the iDash server.  This will generate a new log called event.log (and up to 20 archive logs with the event.log.# filenames) each with a file size of 20MB containing full debug level trace on the inbound JFM messages from CA 7 to iDash.