Automic Workload Automation

  • 1.  How to Enable and Disable Trace on the Automation Engine and Agents

    Posted 08-02-2016 09:58 AM
    When an issue occurs, sometimes you are able to fix it on your own.  However, you still want to know the root cause analysis (RCA) why it happened.  In order for Support to provide a root cause analysis, the issue needs to be captured in a trace.  Below are steps how to enable and disable the trace from the UserInterface.

    Depending on the issue, tracing needs to be turned on for 5 minutes to capture the issue.
    If you are reproducing a specific, on-demand issue, leave the trace on until you complete the reproduction then turn it off. 

    Here are the standard trace settings:

    Automation Engine


    Enable the trace on every single CP.
    Go to your System Overview > Automation Engine > right-click one of the CP > Properties > set TCP/IP=9

    h36darxzd7lp.jpghttps://us.v-cdn.net/5019921/uploads/editor/s5/h36darxzd7lp.jpg" width="1111">

    Enable the trace on just one WP.
    Go to your System Overview > Automation Engine > right-click one of the WP > Properties > set TCP/IP=2 and DB=4

    q5ehdh51tx8m.jpghttps://us.v-cdn.net/5019921/uploads/editor/ef/q5ehdh51tx8m.jpg" width="1028">

    Agents

    Go to your System Overview > Agents > right-click on the agent > Properties

    db0djz4ep0r8.jpghttps://us.v-cdn.net/5019921/uploads/editor/mq/db0djz4ep0r8.jpg" width="1066">

    These are standard tracing:

    1. For OS agents (i.e. Windows, Unix, etc)

    Set TCP/IP=9

    2. For RA agents (i.e. RA FTP)

    Set TCP/IP=9, RA=9

    For tracing on specific issues:

    3. File transfer issue

    TCP/IP=9

    4. If there is a content issue with the file transfer (i.e. corrupted)

    TCP/IP=9, Filetransfer=9

    Note:  Sometimes recommended tracing differ from standard tracing because it needs to be customized specifically for the type of issue you are facing (i.e. SAP, etc).  In this case, please contact Support.

    How to Disable the Trace


    To disable the tracing, simply return the value back to 0 and save.

    What Files Are Needed


    Now that you have captured the issue in a trace, it is time to provide Support the appropriate files.

    For Automation Engine:
    A.  CP logs and CP trace files
    B.  WP logs and WP trace files

    For Agents:
    C.  Agent logs and Agent trace files
    D. The problematic job's RUNID and/or Date and Timestamp of  when the issue occurred
    E.  ALL of the problematic job's Job Reports and Job Details

    Note:  Please do not turn on tracing at all times.  Only turn it on when you want to capture an issue.  Once issue is captured in a trace, please turn off the trace.



  • 2.  How to Enable and Disable Trace on the Automation Engine and Agents

    Posted 08-08-2016 08:27 AM
    You can also set tracing with scripting: SET_UC_SETTING SET_TRACE
    http://docs.automic.com/documentation/AE/11.2/english/AE_WEBHELP/help.htm?product=awa#ucaawg.htm

    With Scripting you have the option to capture occurances during odd hours, just activate tracing for a single run of an object or even set up rolling traces for issues that only happen sporadically. An example on how to do it can be found here:
    https://automic.force.com/support/apex/CommunityArticleDetail?id=ka4b00000004MCp

    And, for completeness sake: Tracing can also be set in the ini files of the components which makes sense if you need to capture problems on startup of the component.


  • 3.  How to Enable and Disable Trace on the Automation Engine and Agents

    Posted 08-09-2016 12:59 PM
    Since it has happened so many times, please note if you are capturing startup problems and set the trace on the .ini, please turn it off once captured. :)

    Running out of space due to leaving tracing active has happened in multiple cases and its an easily stopped major system hiccup. 


  • 4.  How to Enable and Disable Trace on the Automation Engine and Agents

    Posted 08-10-2016 11:40 AM
    Regrading tracing of an startup: If you set the trace parameters in the ini-file, don't forget to set them back again. Because if you restart a component later, the trace flags are taken from the ini-file and tracing starts again.
    E.g. following example:
    1. You want to trace something at startup of a WP. You set the trace flags in the ini and start only one WP (and a CP) to keep the amount of trace data small.
    2. You captured your issue and deactivate the trace flags in the GUI for the WP.
    3. You start your other WPs and suddenly tracing is started again, as it is still in the ini-file.