Table of Contents |
---|
| outlinh1. true |
---|
| outlinh1. true |
---|
1 | printablefalse |
---|
2 | stylh1. none |
---|
3 | indent20px |
---|
|
The <process../> element in a job configuration was useful to start an executable.
Code Block |
---|
|
<job >
<params />
<process file="/path/to/my_executable" param="my_param">
<environment />
</process>
<run_time />
</job>
|
This above configuration is DEPRECATED.
You can use the following instead:
Code Block |
---|
|
<job >
<params />
<environment />
<script language="shell">
<![CDATA[
/path/to/my_executable my_param
]]>
</script>
<run_time />
</job>
|
You can download a converter "process2script.xsl".
Extract the archive i.e. in the ./config directory of the JobScheduler installation.
Then call it ...
Code Block |
---|
java -jar /path/to/saxon9he.jar -xsl:"process2script.xsl" -s:"live/a.job.xml" -o:"live/a.job.xml" is_windows=true
|
Code Block |
---|
java -jar /path/to/saxon9he.jar -xsl:"process2script.xsl" -s:"live/a.job.xml" -o:"live/a.job.xml"
|
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:
Code Block |
---|
|
<job >
<params />
<script language="shell"/>
<process file="/path/to/my_executable" param="my_param">
<environment />
</process>
<run_time />
</job>
|
In this case please use the converter "process2script.xsl" or JOE to put the data from the job's process file tab into the job's script tab.