The installation variant Job Server with Worker installation is created on a workstation or on a server. The Job Server and Worker run in a joint process. If a restart of the Job Server is required, the Worker is also restarted and the other way around. If the process is terminated via the Task Manager this can lead to an error in the database of the server. A known memory leak in the browser being used results, at an opened Job Server, in a continuously increased memory usage that makes a restart mandatory.
Stand-alone installation with EOX file or EECX file for data storage:
After the installation of the application as a Stand-Alone installation on the computer, further manual installation steps are required.
Access to an EOX file instead of a FastObjects database can be configured subsequently in ec.ini.
To run the Job Server with Worker, at least three folders must be set up that can be named freely (the following names have been chosen freely):
- Job definitions: This folder must also be specified as the directory for JMX files in the user preferences. This is where job definitions in the JMX format are stored that trigger a defined job.
- Successful jobs: In this folder, or its subfolders, the job definition is stored, as are the data created after successfully processing a job definition.
- Failed jobs: In this folder, or its subfolders, the job definition is stored, as are the data created after a failed processing of a job definition.
If the generation of target data requires further resources, another, random, folder must be provided for this as well.
The Job Server with Worker can be set up as a Windows service and can be run without a user interface.
More: