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

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

book

Article ID: 17171

calendar_today

Updated On:

Products

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

Issue/Introduction

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



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.

 

Environment

ALL

Resolution

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++">

     <iTechSDK>

...

       <Debug>

         <!--possible values are ERROR/WARNING/TRACE/NOLEVEL-->

         <logLevel>TRACE</logLevel>    

...

       </Debug>

     </iTechSDK>   

Also open the $AUTOUSER/logger.server.config file 

At the near bottom of the file find the following:

 

<root>

     <priority value="error" />

     <!-- <appender-ref ref="SDK" /> -->

     <!-- <appender-ref ref="Console" /> -->

</root>  

Replace with:

 

<root>

     <priority value="trace" />

     <!-- <appender-ref ref="SDK" /> -->

     <!-- <appender-ref ref="Console" /> -->

</root>   

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

 

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