Time-driven


images/download/thumbnails/44944903/arrow_up-version-1-modificationdate-1582788893739-api-v2.png Introduction: You can find a description of this phase in section Phase 1 (Introduction).


images/download/thumbnails/44944903/image2020-3-17_15-38-38-version-1-modificationdate-1584412717303-api-v2.png

Time-driven Input Agents can actively fetch data from a source at a user-defined time. The times can be specified classically in cron syntax, but also in simplified form. In addition, time-driven Input Agents can be triggered via HTTP or Message.

Notes


  • The last start time and the next scheduled start time of a profile can be viewed in the Control Center.

  • Directory names can be dynamically created in all data sources with date placeholders. The directory name C:/tmp/<yyyyMMdd>, for example, will be replaced by C:/tmp/20080601.

  • The system variable VAR_SYS_TRIGGER_CHANNEL_ID (or MSG_CALL_VAR_SYS_TRIGGER_CHANNEL_ID ) allows you to replace the partner channel of a time-driven Input Agent (any type) by the channel with this ID (value of the variable) (details see there).

General Settings


images/download/attachments/44944903/544-version-1-modificationdate-1649156171772-api-v2.png


(1) This setting is available for all time-driven Input Agents. Only relevant for the add-on module Load Balancing to start a profile on a specific node.

Create Internal Cronjobs With Function


See function createScheduleEntry(a, b, [c]).