This functionality is only available for certain module packages.

jobdefinition

The tag <jobdefinition> is the top-level element. All other tags are contained within this element.

Attribute Usage Values Default value Description
failedMailRecipients optional <mail address>,<mail address> In the event of an error, e-mails are sent to these addresses. Additional addresses should be separated by commas.
globalMutex optional <mutex name> Name of a globalMutex. This type of Mutex prevents the parallel execution of Jobs with a globalMutex of the same name across all Workers.
model required <path to eox file>

UNC path to EOX or EECX file of the basic model. A relative path specification is possible if a path is specified for the repository folder in the user specifications or the initialization file. If this specification is missing, the path to the JMX file is used instead.

The path to the model can also be specified with a formula as =trigger.filePath. Then a search is carried out for an EON or EECX file in the incomingFolder. A corresponding filter has to be set for this purpose.

If a webTrigger is specified with the formula =trigger.params.<model parameter>, the path to the EON or EECX file has to be specified as a parameter in the Web call.

name required <job name> Name of the job. If the name is defined by means of a formula, the name with the extension trigger.fileName can be dynamically combined into a name including job file name.
successMailRecipients optional <mail address>,<mail address> In the event of success, e-mails are sent to these addresses. Additional addresses should be separated by commas.
workerMutex optional <mutex name> Name of a workerMutex. This type of Mutex prevents the parallel execution of Jobs with a workerMutex of the same name on the same Worker.
xmlns:xi required if not specified in the <xi:include> tag http://www.w3.org/2001/XInclude Namespace extension to facilitate use of xi:include
Allowed sub-elements Quantity
fileTrigger 1
webserviceTrigger 1
actions 1
custom 1

Note:

In the event of success or failure, e-mails can be sent to predetermined addresses. This is only possible when the send e-mails in the event of success check box or the send e-mails in the event of an error check box is selected and values that are valid for the SMTP server have been entered.

Job designation:

The job name actually combines the value of the Name attribute with the time stamp (Local Time of the Job Server), e.g. "_140805_1544_01000", where the 1000 represents the number of milliseconds that have elapsed since the previous minute. This ensures that each job name is unique.

In this case (see the above definition) the list of jobs (e.g. as sub-folders containing job results, definition, UMC logs) would appear as follows:

File_Werk1_140805_1544_00012

File_Werk1_140805_1546_56435

File_Werk2_140805_1546_03455

Example of a Job definition that specifies the storage location for the basic model via fileTrigger:

Example of a Job definition that specifies the storage location for the basic model via webserviceTrigger:

Example of a Job definition with webserviceTrigger in order to name Jobs differently depending on the call:

Exclude parallel execution of Jobs

If the Maximum number of parallel Jobs is set to a value greater than 1 in the preferences, several Jobs can be executed parallel. However, for specific Jobs, parallel execution cannot be allowed and it must be possible to exclude it.

Mutual exclusion is generally abbreviated as Mutex. The parallel execution of Jobs can be excluded in two levels through the attributes workerMutex and globalMutex.

See also:

https://en.wikipedia.org/wiki/Mutual_exclusion