Automic Workload Automation

  • 1.  database schedule job activation time difference

    Posted Apr 20, 2018 10:19 AM

    Hi,

    database job in schedule for example we set schedule time 16:29:00 after start we checked statistics,agent log  we see that starting 16:29:16  .difference is 16 sec.   is there such a setting for reduce this time ?  

     

     



  • 2.  Re: database schedule job activation time difference

    Posted Apr 20, 2018 10:46 AM

    Hi

     

    Short: No

     

    Long: Automation Engine is not realtime processing so its simply not possible.

     

    Lecture tip: EH_Kick (every 20 seconds is looked for new job executions for generation etc...

     

    The best you can do is using high performance hardware + database + network.

    An indicator is the test value in the WP logs at Wp start:

     

    U00003533 UCUDB: Check of data source finished: No errors. Performance CPU/DB: '30399041'/'215 (1000/4.638360 s)'
    U00003544 UCUDB: Reference values tested with Windows 2003 on XEON 1500 MHz: CPU 813865, DB 470

     

    cheers, Wolfgang



  • 3.  Re: database schedule job activation time difference

    Posted Feb 04, 2019 05:28 PM

    FrankMuffke, Question on EH_Kick.

    I noticed that in 12.2 documentation it say that default setting is 3 seconds for EH_KICK_INTERVAL.

     

    Is this the same setting?

    Had the default value been change since version v9, v10, v11?

     

    https://docs.automic.com/documentation/webhelp/english/AWA/12.2/DOCU/12.2/AWA%20Guides/help.htm#AWA/Variables/UC_CLIENT_…  

     

     

     

    Just trying to answer similar question to our internal customers why workflows don't start exactly at scheduled time/seconds.

     

    Thanks. 



  • 4.  Re: database schedule job activation time difference

    Posted Feb 12, 2019 06:06 AM

    Hi

     

    its not the same setting but similar :-)

     

    EH_KICK_INTERVAL is only responsible for activity refresh but not for the internal processing of AE.

     

    AE was never desiged for realtime processing. If you have the need to do this you can use a workaround, start an OS job some Minutes before the time it should actually start containing an OS command e.g.

    echo "ls -l" | at 07:00

    cheers, Wolfgang