Crontab Syntax

Introduction: You can find a description of this phase in section Phase 1 (Introduction).

images/download/thumbnails/131696234/image2020-3-17_15-39-1-version-1-modificationdate-1677823668456-api-v2.png

The following screenshot shows how to configure time-driven Input Agents with crontab syntax. Corresponding templates and a cron wizard are available via the context menu . In addition, you can define your own templates in a configuration file, which are then also selectable, see sections below.


images/download/attachments/131696234/545-version-1-modificationdate-1677823668449-api-v2.png


The syntax used in Lobster_data is similar to the crontab syntax in UNIX systems. However, the numbering of weekdays differs from the UNIX syntax. It starts with 1 for Sunday.

In column Day, for example, a 1 stands for the first day of the month, an L stands for the last day of a month, and a * means every day.

Important note: In any case, avoid a single asterisk (*) in the Seconds column, because that means every second and would have a very strong impact on performance.

Important note: If a job still runs when a new start time is reached, the new start time is ignored.


The following table shows some examples of setting the time points using crontab syntax. For comprehensive explanations and examples on the topic of crontab syntax, please refer to external sources. This is a commonly used concept.


Seconds

Minutes

Hour

Day

Month

Weekday

Meaning

0

0

*

*

*

*

Every hour.

0

15

10

*

*

1

Every Sunday at 10:15.

0

*/20

*

*

*

*

Every 20 minutes, starting from full hours and on the full hour. Example: Let's assume you save your profile at 16:56 with these settings. Then it runs at 17:00, 17:20, 17:40, 18:00, 18:20, ...

0

*/21

*

*

*

*

Every 21 minutes, starting from full hours and on the full hour. Example : Let's assume you save your profile at 16:56 with these settings. Then it runs at 17:00, 17:21, 17:42, 18:00, 18:21, ...

Note: If you really want the next profile run 21 minutes after the last run, please use intervals.

*/10

*

*

1

12

*

Every 10 seconds on the 1st of December (starting from full minutes and to the full minute).

0

*/10

6-8,16-19

*

*

*

Every 10 minutes between 6-8 and 16-19 hours (starting from full hours and on the full hour).

Cron Wizard


images/download/attachments/131696234/1409-version-1-modificationdate-1677824549722-api-v2.png

Defining Custom Cron Templates


You can define custom templates in the configuration file ./etc/admin/datawizard/cron_templates.txt. It is not necessary to restart the Integration Server.

# here you can define custom cron templates
# <name of template> = <cron syntax>
# the name should not contain "="
 
# Example - values on right separated by single blank
Every Friday at 22:00 = 0 0 22 * * 6