ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

How to turn on Debugging for EEM when Autosys is locked out of EEM?


Article ID: 50202


Updated On:


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



To determine why authorizations are failing, we will need to get traces from EEM. This debugging will enable EEM and ispUtil messages from within the Application Server.


To enable ispUtil/EEM messages in the Application Server, you can make the following modifications to the $AUTOUSER/eiam.server.config file:

<SDK type="C++">
         <!--possible values are ERROR/WARNING/TRACE/NOLEVEL-->

Also open the $AUTOUSER/logger.server.config file
At the near bottom of the file find the following:

     <priority value="error" />
     <!-- <appender-ref ref="SDK" /> -->
     <!-- <appender-ref ref="Console" /> -->

Replace with:

     <priority value="trace" />
     <!-- <appender-ref ref="SDK" /> -->
     <!-- <appender-ref ref="Console" /> -->

Additional logging files would then be written to $AUTOUSER/audit

See "CA Embedded Entitlements Manager r8.4 SR02 Readme" for more details regarding logging.


Release: ATSAGE99000-11.3-Workload Automation AE-Remote Agent