Date: Fri, 29 Mar 2024 09:06:07 +0000 (UTC) Message-ID: <1932642958.12653.1711703167071@change.sos-berlin.com> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_12652_1021154738.1711703167071" ------=_Part_12652_1021154738.1711703167071 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
JobScheduler is creating and starting a separate process for each scheduled job or job chain node . The number of parallel proces= ses can be limited. The workload of the job has no impact on JobScheduler. = Sometimes the size of the log files could create a problem due to some rest= rictions on the database in use.
If the program that has to be scheduled by JobScheduler can be started i= n a shell (Windows or Unix) then the job type has to be a shell job. All pr= ograms that are started by cron or taskplaner should be running in the shel= l job of JobScheduler as well.
It is important to keep in mind that JobScheduler is running as a servic= e (Windows) or as a daemon (Unix). JobScheduler must have at least all the = required permissions for accessing the resources that are needed to execute= the program.
Should it not be possible to start an executable file in a shell then it= could be possible to implement a wrapper (e.g. in Java, ...) and execute t= his program as an AP job (similar to Standard JITL Jobs).