| Table of Contents | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
In the sample below there are two different approaches described how you can start jobs on a file event.
Using a file order source
See also Documentation
the The job chain job_chain_file_order_source has a file order source looking watching for files in c:\temp\input ending with the file name extension .txt. When a file arrives, an order for the job chain will be created. The file will be erased removed at the end of the job chain by the file sinkssink node(s).
- Orders can not have additional parameters.
- Order processing starts when the file arrivesis detected, not when after the file is completly completely written.
Using JITL Job JobSchedulerExistsFile
See also Documentation
the The job chain "job_chain_file_order_source_poll" uses the job JobSchedulerExistsFile to check, wether whether a file is in c:\temp\input ending with .pdf. If so, for each file found, an order will be created for the job chain job_chain_file_order_source. The file will be erased removed by the sinks in the executed job chain.
- The created order have has the same parameters as the polling order
- The first step in the executed job chain checks, wether whether the file is completly written.
Please note, that you can mix file_order_source and JobSchedulerExistsFile by using JobSchedulerExistsFile in the first node to check, whether the file is has been completly written.