Date: Thu, 28 Mar 2024 17:30:36 +0000 (UTC) Message-ID: <2061866615.11773.1711647036862@change.sos-berlin.com> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_11772_1456726010.1711647036862" ------=_Part_11772_1456726010.1711647036862 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
On Unix systems, the JobScheduler is operated as a demon.To start and st= op the JobScheduler use the script:
$SCHEDU= LER_HOME/bin/jobscheduler.sh start
$SCHEDU= LER_HOME/bin/jobscheduler.sh stop
In addition to start
and stop
, this script acc=
epts 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_DA=
TA/logs/scheduler.log
for the reason. You may be missing dependent l=
ibraries.This can be checked with:
$SCHEDU= LER_HOME/bin/jobscheduler.sh ldd
On Microsoft Windows systems, the JobScheduler is installed as service.Y= ou can find the JobScheduler service by opening the Microsoft Windows servi= ce panel and looking for a service with a name starting with "SOS JobSchedu= ler". The service has the system account after the setup. The service is co= nfigured to be started automatically at server startup.
You can start and stop the service in the Microsoft Windows service pane= l with:
sc.exe = start sos_scheduler_[JobSchedulerId]
sc.exe = stop sos_scheduler_[JobSchedulerId]
...where [JobSchedulerId]
is the Id of the JobScheduler.&nb=
sp;
Further you can start the JobScheduler from the command line. Ensure tha= t the service has not already been started and use the following script:
$SCHEDU= LER_HOME\bin\jobscheduler.cmd start
$SCHEDU= LER_HOME\bin\jobscheduler.cmd stop
In addition to start
and stop
, this script acc=
epts additional parameters, e.g.debug, restart, abort
and=
kill
. If the JobScheduler doesn't start then look a=
t the $SCHEDULER_DATA/logs/scheduler.log
for the reason.