This functionality is only available for certain module packages.

You are here: EEC > Job Server and Worker > Worker


An EEC with activated Worker plugin on the same computer on which the Job Server is also installed is called a Local Worker. If the installation with activated Worker plugin is on a different computer, it is called a Remote Worker.

The following figure shows the Worker variants.

Workers can create files or execute long-running processes asynchronously in the configuration phase, on the basis of a model with corresponding actions and commands. These processes are called Jobs below.

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:

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).

The data created are stored in a folder, which is also specified in the job definition (see Storing created files and Job definitions).

See also: