Applications Manager Debug Matrix

Document ID : KB000088516
Last Modified Date : 05/09/2018
Show Technical Document Details
Introduction:
When and how do you set debugging for Applications Manager?
Instructions:

Applications Manager Debug Matrix

        


Type of Debug to Enable 
 

Possible Issues  
Agent Debug
(checkbox)
RMI Debug
(checkbox)
Agent Debug(backend)RMI Debug(backend)Job level BODY DebugClient TraceRA DebugCondition Debugaw_install.log
Automation Engine or Local agent will not start  XX     
Remote Agent Startup  XX     
Agent Crash(random)  XX     
Agent Crash(reproducible)XX       
Automation Engine/Agent in Trouble status  XX     
UI Issue   X X   
Job Aborts(random)  XXX    
Job Aborts(reproducible)XX  X    
Standard Job goes to launch error*X       
RA Job Aborts(random)   X  X  
RA Job Aborts(reproducible)XX       
RA goes to Launch Error*X       
Performance Issues   X     
License Issue   X     
Condition not functioning X     X 
Failure during install/upgrade        X
  
XNeeded
*Special Cases only*Check with AM tech*

 
 













































 

 

If there are  questions regarding what to do with regards to specific Agent/Automation Engine (master) statuses refer to the online documentation:

User Guide > Automation Engine/Agent Status Values

Task statuses:

User Guide > Task Status Values

Agent Debug(checkbox)

  • Edit the Agent having the issue in the GUI 
  • Check Agent Debug
  • Close the Window
  • Debug will be written to the AgentService<timestamp>.log file in the agent’s log directory

RMI Debug(check box)

  • Click on Help About Applications Manager from the AM client 
  • Click on Debug (upper left corner area)
  • Place a check mark in the box to the left of Server
  • Close the Window
  • Debug will be written to the RmiServer<timestamp>.log file in the Automation Engine’s log directory

Agent Debug and RMI Debug(backend)

  • Navigate to the $AW_HOME/site folder of the Agent or Automation Engine having the issue
  • Open the awenv.ini file in a text editor
  • Add the following line to the [default] section: Debug=true
  • Save the file
  • Restart the Agent/Automation Engine
  • Debugging is now enabled
  • Debug will be written to the RmiServer<timestamp>.log or AgentService<timestamp>.log file in the Automation Engine’s or Agent’s log directory 

Job Level BODY Debug

  • Navigate to the $AW_HOME/debug (Unix) %AW_HOME/debug (Windows) folder 
(Create the debug folder if it is not there)
  • Create an empty file called BODY Examples:
Unix: touch BODY
Windows: echo > BODY
  • Save the file with no extensions, and no content. It should be a zero byte file 
  • Job level debugging is now enabled. Debug information will be added to the job's output file ($AW_HOME/out). Once the BODY file is removed from the $AW_HOME/debug directory debugging will be disabled.
  • Debug logs will be added to the $AW_HOME/out folder of the agent assigned to the job. 

Client Trace

  • Open the Java Control Panel on the client machine
  • On the Advance Tab check:

Enable Tracing
Enable Logging
Show Console

  • Launch the client and reproduce the error
  • Cut the text out of the Java Console and save to a text document

RA Debug

  • Navigate to the $AW_HOME/site folder of the associated Agent
  • Locate and open the file called awenv.ini
  • Add the following line to the [default] section of the file: radebuglevel=99
  • Save the file
  • A restart is required when changes are made to the awenv.ini file.
  • Debug information will be added to the Job's output file located in the Agent's $AW_HOME/out directory
  • Comment out or remove the radebuglevel=99 from the awenv.ini file, and restart the agent processes to disable debugging

Condition Debug

  • Click on the Agent Icon (top tool bar)
  • Highlight the Masters Agent
  • Click on Edit
  • Click on the Automation Engine Options Tab
  • Click on the Debug tab
  • Place a check mark to the left of Enable Full Condition Debugging
  • To disable debugging uncheck the Enable Full Condition Debugging and logout and back into the client.
  • Debug will be written to the RmiServer<timestamp>.log file in the Automation Engine’s log directory 

aw_install.log

  • If an install or upgrade fails DURING the process we will need the:

These are the older versions we do not need. The most current is the aw_install.log file.
 aw_install.<timestamp>
This is located in the $AW_HOME/install directory of whatever was being upgraded or installed. There may be multiple copies of that log formatted as:
aw_install.log file

  • Text to search for in logs (Error Codes): 

AwE-   Our standard error code.
ERR    Generally a return code from script. Found mostly in job’s output file
ORA-  The -20000 and -20999 are reserved for the application while rest are Oracle errors.

File Attachments:
ApplicationsManagerDebugMatrix.docx