Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Note: This text only applies to JobScheduler version up to and including 1.6.x

Question:

If we are using JOE for a JobScheduler running without a database then do we need to restart the JobScheduler every time after making changes to a job?

Answer:

No, this is not necessary, JOE stores information about jobs, orders, etc. in XML files in the so-called "hot folder" (default location: ./config/live).
On Unix systems it may take up to a minute for changes made using JOE to become effective.

For a quick introduction to using JOE we recommend you take a look at our Quickstart Guide.

Note also that JobScheduler objects (jobs, orders, etc.) can be stored in a scheduler.xml file. This method of storage does require that the JobScheduler is restarted after changes are made.
This method of storage is still mentioned in our documentation although we no longer recommend using it.

Note also that in a productive environment, we recommend using JobScheduler with a database. Amongst other advantages, this allows use of JID - the JobScheduler Information Dashboard - which provides calender, monitoring and reporting functions.