10222015 Applications Manager Debug Options When which should
10/22/2015 Applications Manager Debug Options When & which should I used?
Common debug + RMI Debug + Job Level Debug + Conditional Debug + Agent Debug + RA Agent Debug + SURUN Debug + Client Debug 3 Property of Automic Software. All rights reserved
RMI Debug • By default debug on the RMI process is not enabled. The Rmiserver. <YYMMDDHHMM>. log will only show an -Awe error within it and nothing else. – This should be enabled if errors are seen within Applications Manager or its logs. When RMI debug is enabled, it will show the thread/process & what it is running/occurring prior to the -Awe error message. – By default, when log files grow above 50 megabytes, Applications Manager automatically rolls them over. When Applications Manager finishes writing to a log, it auto-zips it to save disc space. When the log directory reaches 500 MB, the logs will automatically purge and start over. 4 Property of Automic Software. All rights reserved
RMI Debug • Enable RMI Debug via the Applications Manager GUI: • Enable RMI debug via Applications Manager awenv. ini file 5 Property of Automic Software. All rights reserved
Job Level Debug • Job level debug should be use when standard job (Job that are not RA or Java job) abort or does not finished successfully. – The additional debug informations will be written to the JOB output file Notes: Once the test/reproduction is done, the BOBY file should be removed from the debug folder. If it is still there, when the maintenance Process Flow job “SYSTEM” run, it will not be able to delete/clean out expired output files on the Agent in which BODY was enabled. 6 Property of Automic Software. All rights reserved
Conditional Debug • This should be enabled when you experiencing an issue with “Condition”; if it is not resolving or triggering correctly. – This should be enabled in conjunction with RMI debugging. 7 Property of Automic Software. All rights reserved
Conditional Debug 8 Property of Automic Software. All rights reserved
Agent Debug • This should be enable when you are experiencing issue with the Agent or Jobs running on the Agent producing errors or failing. – If the agent fail to startup, debug should be enabled via the Agent awenv. ini file 9 Property of Automic Software. All rights reserved
Agent Debug • Enabling Agent Debug via the Applications Manager GUI: Options 1 10 Property of Automic Software. All rights reserved
Agent Debug • Enabling Agent Debug via the Applications Manager GUI: Options 2 11 Property of Automic Software. All rights reserved
Agent Debug • Enable Agent Debug via the Applications Manager Awenv. ini file 12 Property of Automic Software. All rights reserved
RA Agent Debug • This should be enabled when you are experiencing issue with the RA Agent or Jobs running on the RA Agent producing errors or failing. – This should be enabled in conjunction with RMI debugging. 13 Property of Automic Software. All rights reserved
RA Agent Debug • Enabling RA Agent Debug via the Agents awenv. ini file 14 Property of Automic Software. All rights reserved
SURUN Debug • This should be enabled when the SURUN Jobs are erroring out with a SURUN error message – Debug informations will be shown in the standard job output file 15 Property of Automic Software. All rights reserved
Client Debug • This should be enabled when you are experiencing display issue within the Java User interface or client connection issue. – This should be enabled in conjunction with RMI Debug 16 Property of Automic Software. All rights reserved
Client Debug • Enabling Java Client Debug Log into Applications Manager & Reproduce the Issue 17 Property of Automic Software. All rights reserved
- Slides: 17