The following figure shows the Worker variants.
The Job Server assigns the Jobs to be processed to registered Workers. Workers are registered automatically at a Job Server. For automatic registration a corresponding entry has to be carried out in the initialization file (see de.eplan.eec.jobserver.aliasurl).
The initial bases for the Jobs to be processed are so-called Job definitions (see Job definitions). Job definitions are XML files with the extension .JMX.
A folder in which the Job definitions are stored has to be specified in the user specifications for each Worker (see Preferences for the Job Server Worker).
The Worker reads these Job definitions in once at the start. Reading in of the Job definitions can be triggered manually through the user interface of the Job Server and of the Worker.
A Job definition always contains the following specifications:
- Name of the Job definition.
- Name of the model.
- Type of the trigger that triggers a Job (for example the file extension .px).
- Directory specification for storing the created files in case of success and failure.
- Names of actions or commands that are to be executed for a Job.
Depending on the job definition to Worker expects either a file with a defined file extension in an incoming folder (File Trigger) or a specification within the calling URL (Web Service Trigger) to start a Job (see action).
If several files are contained in an incoming folder in the case of a File Trigger, the files are processed in their chronological order (FIFO principle).