| Table of Contents | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
The components installed and the methods used to start jobs depend on the architecture that is being installed:
remote execution
A JobScheduler Agent without its own configuration or a JobScheduler instance can be installed. (this is called the client). Processes on the agent or the instance of JobScheduler are remotely controlled by another JobScheduler.
Jobs are scheduled at the client according to events (e.g. heir planned starting times) or commands.
See also How does a supervisor scheduler distribute the 'central configuration directory'?/scheduler.doc/remote_execution.xml external job processing with agents] in the JobScheduler documentation.
remote configuration service (rcs)
A JobScheduler instance is installed, which then receives its configuration from a JobScheduler supervisor.
The configurations of all the remotely configured JobSchedulers in a network are centrally administered by a so-called Supervisor and which distributes the configurations to the remotely configured "workload" JobSchedulers.
If the Supervisor is temporarily not available, the Workload JobSchedulers will continue to work using their local configurations.
See also: [How does a Supervisor JobScheduler deploy the central configuration directory?
SSH execution
It is not always necessary to install a JobScheduler instance on a client to execute jobs remotely.
The JobScheduler can start Jobs (scripts) per SSH.
See also: What is the difference between SSH -Job job execution and remote JS-JobScheduler Agents? and category__SSH.