5.1 JobScheduler Demon on Unix®
On Unix® systems, the JobScheduler is operated as a demon.To start and stop the JobScheduler use the script:
$SCHEDULER_HOME/bin/jobscheduler.sh start
$SCHEDULER_HOME/bin/jobscheduler.sh stop
In addition to start and stop, this script accepts additional parameters, e.g.debug, restart, abort and kill. If you want the JobScheduler to be started automatically at server startup then please follow the steps which are described in the How do we get JobScheduler to auto start on Linux? article.
If the JobScheduler doesn't start then look into the $SCHEDULER_DATA/logs/scheduler.log for the reason. You may be missing dependent libraries.This can be checked with:
$SCHEDULER_HOME/bin/jobscheduler.sh ldd
5.2 JobScheduler Service for Microsoft® Windows®
On Microsoft® Windows® systems, the JobScheduler is installed as service.You can find the JobScheduler service by opening the Microsoft® Windows® service panel and looking for a service with a name starting with "SOS JobScheduler". The service has the system account after the setup. The service is configured to be started automatically at server startup.
You can start and stop the service in the Microsoft® Windows® service panel or with:
sc.exe start sos_scheduler_[JobSchedulerId]
sc.exe stop sos_scheduler_[JobSchedulerId]
...where [JobSchedulerId] is the Id of the JobScheduler.
Further you can start the JobScheduler from the command line. Ensure that the service has not already been started and use the following script:
$SCHEDULER_HOME\bin\jobscheduler.cmd start
$SCHEDULER_HOME\bin\jobscheduler.cmd stop
In addition to start and stop, this script accepts additional parameters, e.g.debug, restart, abort and kill. If the JobScheduler doesn't start then look into the $SCHEDULER_DATA/logs/scheduler.log for the reason.