Enable EEM SDK Debug Logging in AutoSys Web UI
search cancel

Enable EEM SDK Debug Logging in AutoSys Web UI

book

Article ID: 32815

calendar_today

Updated On:

Products

CA Workload Automation AE - Scheduler (AutoSys) Autosys Workload Automation

Issue/Introduction

Steps to enable EEM SDK Debug logging in AutoSys Web UI  (WCC)

Environment

Workload Automation AutoSys

Resolution

  • Backup the file eiam.config. This file is located under:

Unix:  $CA_WCC_INSTALL_LOCATION/data/config/application/config/resources/ or /opt/CA/WorkloadCC/data/config/application/config/resources/

Windows:  %CA_WCC_INSTALL_LOCATION%\data\config\application\config\resources or C:\Program Files\CA\Workload Control Center\data\config\application\config\resources

 

  • Edit the original eiam.config:
    1. Ensure the full path and file name in the LoggerConfiguration File is correct.  (example: <LoggerConfiguration file="/opt/CA/WorkloadAutomationAE/wcc/data/config/application/config/resources/eiam.log4j.config"/>

    2. Look for <SDK type="Java'> to have below changes added

    3. Change  <logLevel>off</logLevel>    to     <logLevel>all</logLevel>    
      Note: possible values are severe/warning/info/config/fine/finer/finest/all/off 
      Note:  Original value could be this also   <logLevel></logLevel>,   so change the value to  <logLevel></logLevel>   in this situation 

    4. Change: <logToFile></logToFile>    to         <logToFile>true</logToFile>  
      Note:  Change to next item <logFile></logFile> is not needed normally

    5.  Change:  <maxLogSize>1000</maxLogSize>   to  some size in MB

    6.   Save the file

 

  • Backup eiam.log4.config, below are defailt locations where the file is file located at:

    Windows: C:/Program Files/CA/Workload Control Center/data/config/application/config/resources/eiam.log4j.config

    Unix$CA_WCC_INSTALL_LOCATION/data/config/application/config/resources/eiam.log4j.config 

 

  • Edit the original eiam.log4j.config   change the <Loggers>  section to look like below:

 <Loggers>
    <!-- Uncomment to enable Network Logging -->
    
    <Logger name="Network" level="TRACE" additivity="false">
      <AppenderRef ref="Network"/>
    </Logger>
 
    <!-- Uncomment to enable Performance Logging -->
 
    <Logger name="Perform" level="TRACE" additivity="false">
      <AppenderRef ref="Perform"/>
    </Logger>

    <Logger name="SDK" level="DEBUG" additivity="false">
      <AppenderRef ref="SDK"/>
    </Logger>

    <Root level="DEBUG">
      <AppenderRef ref="SDK"/>
      <AppenderRef ref="Perform"/>
      <AppenderRef ref="Network"/>
      <AppenderRef ref="Console"/>
    </Root>
  </Loggers>

 

  • Adjust the size of the log files it will create and how many files can be allowed in the rollover.

  <SizeBasedTriggeringPolicy size="10mb" />
      <DefaultRolloverStrategy max="1"/>

It may need to be changed to something like:

  <SizeBasedTriggeringPolicy size="50mb" />
      <DefaultRolloverStrategy max="10"/>

 

  • Save the file

NOTE: NO restart of any sort is needed to start seeing the SDK traces.  They get activated when log4j refresh interval is reached.

 

 

EEM SDK Logs go to: 

$CA_WCC_INSTALL_LOCATION/log/eem/eiam*.log   (a file is generated for each item there)

 

 

 

Additional Information

To disable the logging, revert to the backed up files above, no restart needed.