| Table of Contents | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
JobScheduler is creating and starting a separate process for a each scheduled job or jobchain-node a separate processjob chain node . The number of parallel processes can be limited. The workload of the job has no impact on JobScheduler. Sometimes the size of the logging-file log files could have create a problem due to some restrictions on the used database in use.
If the program which that has to be scheduled by JS JobScheduler can be started in a shell (Windows or Unix) then the job - type must has to be a shell - job. All programs , which that are started by cron or taskplaner should be running in the shell - job of JobScheduler as well.
It is important to keep in mind , that JobScheduler is running as a service (windowsWindows) or as a demon daemon (Unix). JobScheduler must have at least all the required permissions for accessing the resources , which that are needed to execute the program.
If Should it should not be not possible to start an executable file in a shell then it could be possible to implement a wrapper (e.g. in Java, ...) and execute this program as an API-AP job (like the "standard" jobssimilar to Standard JITL Jobs).