Jobs
Jobs in DATAmaestro Lake execute an action at a given frequency. The following types of jobs are available at DATAmaestro Lake.
...
Enter Job id: /folder/Job Name. Example: /demo/Automotive/Computed Tag/PercentageValue.
Select Scheduling.
Standard: Job will be executed a first time after the initial delay and then execution will occur at regular intervals. This regular interval is defined by the period.
Every day: Job will be executed every day at the same time.
Enter Initial delay, if the initial delay is equal to zero the job starts as soon as the Save button is clicked.
Put Period, time interval between each job execution. Important remark: it is necessary to put the units, example, for a period of 10 minutes: 10m.
Letter
Description
d
day
h
hour
m
minute
s
second
Period for a Computed tag: The period does not influence the frequency or number of output values written by the Computed Tag job itself, only when the calculation will run. The frequency and number of output values written by the Computed Tag job depend on the input variable(s) frequency and number. For example, a job with a Period set to 24h will run every 24 hours. If the data uses input tags sampled every minute, then it will write values every minute. Each time the job runs, it looks to see the last output value and continues the calculation from that point. Therefore, if the job last ran 24 hours ago, it will write an output value every minute (for minute sampled data) for the last 24 hours. The resulting calculation does not depend on the period.
Put the Class name, this indicates the type of job:
Computed tags: be.pepite.pepito.data.historian.tm.jobs.ComputedTagTask
Exports to Analytics: be.pepite.pepito.data.historian.tm.jobs.ExportToAnalyticsTask
...
If for example, you would like to calculate a computed tag with data that is uploaded every minute, however, there is a laboratory measurement that is uploaded only once per day. In this case, you can decide to save this same value during 24 hours (tag validity = 24h). In Advanced properties write the script below. In this example, there is a 3 days validity. Warning: This option should only be used with highly rare data measurements. Please contact PEPITe support for more information.
| Code Block | ||||||||
|---|---|---|---|---|---|---|---|---|
| ||||||||
{
"outputTag": "demo/tagAB",
"tagValidityMap": {
"/demo/tagA": 259200000,
"/demo/tagB": 259200000
},
|
...
| Info | ||
|---|---|---|
| ||
DMFF file name, Project id and Task Id are very important information for the job export, they allow the job to automatically update the project data source and, consequently, all tasks in DATAmaestro. |
| Info | ||
|---|---|---|
| ||
Note on DMFF file the will replace an existant DMFF both with the same name. This means that if the same file is used in two different Analytics projects (for example, if you create a copy of the project) and if the DMFF is updated in only one project, but both projects have the same file name, the DMFF file will be automatically updated in the other project too. |
On Advanced tab:
In this tab it is possible to edit all the properties of the job in a JSON format. For export to DATAmaestro the properties that can be edited are:
...