search cancel

How To Place the WCC Reporting Collector into Debug Mode

book

Article ID: 42118

calendar_today

Updated On:

Products

CA Workload Automation AE - Business Agents (AutoSys) CA Workload Automation AE - Scheduler (AutoSys) Workload Automation Agent

Issue/Introduction

Introduction: 

At times, the reporting collector can experience issues that are not logged by default logging levels.  To gather further information, we need to put the collector into debug mode.

Environment:  

Workload Control Center 11.3+

Instructions: 

1. Navigate to $CA_WCC_INSTALL_LOCATION/log/application/reporting/reporting-collectors_log4j.properties on UNIX/Linux or %CA_WCC_INSTALL_LOCATION%/log/application/reporting/reporting-collectors_log4j.properties on Windows

2. Change the INFO to DEBUG or add DEBUG to the following lines:

log4j.rootLogger=WARN, CONSOLE, ROLLING, DEBUG

log4j.logger.com.ca.autosys.services=DEBUG

log4j.logger.com.ca.uejm.adapter=DEBUG

log4j.logger.com.ca.uejm.datawarehouse=DEBUG

log4j.logger.com.ca.wcc=DEBUG

 

3. You  also need to set some parameters for the remote services. Navigate to $CA_WCC_INSTALL_LOCATION/log/application/remoteservices/log4j.properties on UNIX/Linux or %CA_WCC_INSTALL_LOCATION%/log/application/remoteservices/log4j.properties

4. Add DEBUG to the following parameters:

log4j.rootLogger=WARN, CONSOLE, ROLLING, DEBUG

log4j.logger.com.ca.wcc=DEBUG

 

5. You also need to add the following 2 entries to the file:

log4j.logger.com.ca.autosys.services=DEBUG

log4j.logger.com.ca.uejm.adapter=DEBUG 

 

These changes are immediate and do not require any services to be restarted to take effect. 

 

Environment

Release: ATSYHA99000-11.3.6-Workload Automation AE-High Availability Option
Component: