The <process../> element in a job configuration was useful to start an executable.
This above configuration is deprecated:
You can use the following replacement:
You can download a converter process2script.zip .
Extract the archive i.e. in the ./config directory of the JobScheduler installation.
Then call it ...
- ...on Windows with
- ...on Linux with
where a.job.xml is a job configuration with a process element.
The JobScheduler installation contains a saxon9he.jar in the ./lib directory.
Please note that JOE has a bug when it stores a job with a <process.../> element.
It creates a <script.../> element in addition:
In this case please use the converter process2script.zip or JOE to put the data from the job's process file tab into the job's script tab.