Below is provided information on what tracing to enable to debug EEM issue in AutoSys.
AutoSys 12.x , 24.x
Before making any changes to file please create a backup for easy roll back once the the trace is complete.
EEM SDK Tracing for App Server
==============================
Open $AUTOUSER/logger.server.config and change...
1. Replace everywhere com.ca.eiam by org.apache
(Note: this is in total on 6 lines)
2. a) From:
<!--
<logger name="Perform" additivity="false">
<level value="warning"/>
<appender-ref ref="Performance" />
</logger>
-->
To:
<logger name="Perform" additivity="false">
<level value="trace"/>
<appender-ref ref="Performance" />
</logger>
b) From:
<!--
<logger name="Network" additivity="false">
<level value="warning"/>
<appender-ref ref="Network" />
</logger>
-->
To:
<logger name="Network" additivity="false">
<level value="trace"/>
<appender-ref ref="Network" />
c) From:
<!--
<logger name="SDK" additivity="false">
<level value="warning"/>
<appender-ref ref="SDK" />
</logger>
-->
To:
<logger name="SDK" additivity="false">
<level value="trace"/>
<appender-ref ref="SDK" />
</logger>
d) From:
<root>
<priority value="error" />
<!-- <appender-ref ref="Console" /> -->
</root>
To:
<root>
<priority value="trace" />
<appender-ref ref="SDK" />
<!-- <appender-ref ref="Console" /> -->
</root>
3. Once you make these changes and save the file, the following logs will automatically be created in $AUTOUSER/out within a minute or two (no restart is required)...
EEMTRACE.SERVER.NET.log
EEMTRACE.SERVER.PERF.log
EEMTRACE.SERVER.SDK.log
These logs will need to be sent to Broadcom Support once the problem occurs.
The EEM SDK traces will be written to these logs from that point forward.
The appender settings allow to set the max filesize per file before it rolls over and number of files you want to have
<param name="maxFileSize" value="10000KB" />
<param name="maxBackupIndex" value="10" />
Total size of log files can be calculated.
EEM SDK Tracing for WCC
=======================
Edit <WCC_HOME>/data/config/application/config/resources/eiam.log4j.config and change...
1 a) From:
<!--
<logger name="Perform" additivity="false">
<level value="warning"/>
<appender-ref ref="Performance" />
</logger>
-->
To:
<logger name="Perform" additivity="false">
<level value="trace"/>
<appender-ref ref="Performance" />
b) From:
<!--
<logger name="Network" additivity="false">
<level value="warning"/>
<appender-ref ref="Network" />
</logger>
-->
To:
<logger name="Network" additivity="false">
<level value="trace"/>
<appender-ref ref="Network" />
</logger>
c) From:
<root>
<priority value="off" />
<appender-ref ref="SDK" />
<level value="warning"/>
<!-- <appender-ref ref="Console" /> -->
</root>
To:
<root>
<priority value="trace" />
<appender-ref ref="SDK" />
<!-- <appender-ref ref="Console" /> -->
</root>
2. Once the changes are made and the file is saved, the following logs will start automatically being created in <WCC_HOME>/log/eem within 1 minute (no restart required)...
eiam.sdk.java.log
eiam.performance.java.log
eiam.network.java.log
These logs will need to be sent to Broadcom Support once the problem occurs.
The EEM SDK traces will be written to these logs from that point forward.
The appender settings allow to set the max filesize per file before it rolls over and number of files you want to have
<SizeBasedTriggeringPolicy size="10mb" />
<DefaultRolloverStrategy max="1"/>
Total size of log files can be calculated.
EEM Server Tracing
==================
Open /opt/CA/SharedComponents/EmbeddedEntitlementsManager/config/logger/server.xml
Find these four lines...
<logger name="eiam.server.ipoz" additivity="false">
<logger name="eiam.server" additivity="false">
<logger name="eiam.server.ldap" additivity="false">
<logger name="eiam.server.performance" additivity="false">
Below each of these lines is a "level value" tag.
Change all four of these tags to...
<level value="trace"/>
Once the file is saved, tracing is enabled. No restart is necessary.
This will not create any additional logs.
It will start putting additional info in the existing logs.
All logs under /opt/CA/SharedComponents/EmbeddedEntitlementsManager/logs will need to be sent to Broadcom Support once the problem occurs.