Page History

...

Now your folder should contain at least these files (windows-x64-example, other platforms differ):

• factory.ini
• jobscheduler-engine.dll
• log4j.properties(optional)
• scheduler.exe
• scheduler.xml
• sos.ini
• start.cmd

Testing the scheduler

...

1. Create a folder named "live" in your working directory (your folder). Create a simple hello-world-job in the live-folder.

   Code Block
   language xml title hello world job example collapse true
   <?xml version="1.0" encoding="ISO-8859-1"?> <job > <script language="shell"> <![CDATA[echo Hello World!]]> </script> <run_time once="yes"/> </job>

2. Open a console in your working directory and start the scheduler with the start.cmd

   strat script.

   start script.
   If you have configured logging (log4j.properties and path to the properties file in factory.ini) you should see a job and a task log for the hello-world-job, which should look like this:

   Code Block
   language text title task log collapse true
   2015-10-07 14:58:45.515+0200 [info] SCHEDULER-918 state=starting (at=never) 2015-10-07 14:58:45.516+0200 [info] SCHEDULER-987 Starting process: "C:\Users\YOUR_USERNAME\AppData\Local\Temp\\sos5051B.cmd" 2015-10-07 14:58:45.526+0200 [info] 2015-10-07 14:58:45.526+0200 [info] PATH_TO_YOUR_FOLDER>echo Hello World! 2015-10-07 14:58:45.526+0200 [info] Hello World! 2015-10-07 14:58:45.527+0200 [info] SCHEDULER-915 Process event 2015-10-07 14:58:45.556+0200 [info] SCHEDULER-918 state=closed 2015-10-07 14:58:45.556+0200 [info] SCHEDULER-962 Protocol ends in logs/task.HalloWorldExample.log

   Code Block
   language text title job log collapse true
   2015-10-07 14:58:45.507+0200 [info] SCHEDULER-893 Job is 'active' now 2015-10-07 14:58:45.512+0200 [info] SCHEDULER-930 Task 6114864 started - cause: period_once 2015-10-07 14:59:45.716+0200 [info] SCHEDULER-931 state=stopped 2015-10-07 14:59:45.717+0200 [info] SCHEDULER-962 Protocol ends in logs/job.HalloWorldExample.log