This example shows a simple method to control job starts using time and file-based events. The logic behind this example is of a time event AND a file event.
Use this link to download the files: Process File Example.
Unpack the zip file in the JobScheudler live folder, where you will find the following JobScheduler objects:
- a job chain (
- an order (
- a dummy job (
changeme) that symbolises the file processing.
You will also find two jobs in the "
as well as two further jobs in the "
The time event(s) are set using the RunTime for the
ProcessFile1 order. In the example this order will start once a day at 12:30. This can be changed as required. In XML the
run_time settings looks like:
The file whose presence is required (in this case
c:\temp\ProcessFileTest.dat) is set as a parameter in the
The "trick" lies in the
ExistsFile job, which checks whether a file is present.
If the file is not present then this job will be restarted every minute up to a maximum of 30 times. If no file is found the order will end in error. If a file is found, JobScheduler will continue to process the job chain.
The XML for
ExistsFile job is:
This "polling" effect is realised using "setbacks". These are defined for both the
ProcessFile job chain and for the
ExistsFile job as shown in the next two JOE screen shots:
- Nodes in the "Process File" job chain showing the settings for the error handling and the "
ExistsFile" job setbacks.
- SetBacks for the "ExistsFile" job showing the delay settings.
ExistsFile job can also start job chains, this could be carried out in two steps - which would perhaps be better for testing:
- First of all a job chain, which only consists of the
ExistsFilejob and then
- a second job chain, which is started by the
ExistsFilejob, as soon as a file (or all files) are found. An order can then be started for each file: these orders then being carried out in parallel if required.