Date: Fri, 29 Mar 2024 13:02:49 +0000 (UTC) Message-ID: <2054759596.12931.1711717369412@change.sos-berlin.com> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_12930_1662448485.1711717369412" ------=_Part_12930_1662448485.1711717369412 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
These tutorials provide an introduction to running JobScheduler Jobs and= Orders, starting from the simplest possible 'Hello World' example of an Or= der Job.
It may be useful at this stage to read the following sh= ort articles to find out more about the basic concepts behind JobScheduler = Jobs and Orders and how they differ from those of other job scheduling appl= ications:
Before starting the tutorials it is assumed that:
The tutorials start with running a pre-configured Order Job:
=
live
folder. The live
folder is used to store all the <=
em>objects - Jobs, Job Chains, Orders, etc. - used by the JobScheduler=
. The live
folder is a sub-folder of the JobScheduler's da=
ta directory. C:\ProgramData\sos-berlin.com\jobscheduler\myJobSchedulerID
live
folder,=
e.g.C:\ProgramData\sos-berlin.com\jobscheduler\myJobSchedulerID=
em>\config\live
~/sos-berlin.com<=
/span>/jobscheduler/myJobSchedulerID<=
/em>
live
folder
~/sos-berlin.com/jobscheduler/myJobSchedulerID/config/live
myJobSchedulerID
identifies the JobS=
cheduler instance and is specified during installation.
Whilst it is possible to operate JobScheduler completely from the comman= d line / in batch, these tutorials rely extensively on the JobScheduler's g= raphic interfaces JOE and the JOC Cockpit.
http://localhost:4446/
root:root
C:\Program Files\sos-berlin.com\jobscheduler\myJobScheduler=
ID
./opt/sos-berlin.com/jobscheduler/myJobSchedulerID=
code>
myJobSchedulerID
=
em>
identifies the JobScheduler instance and is sp=
ecified during installation.
bin
sub-directory of the JobScheduler installation directory by ent=
ering one of the commands: