Versions Compared

Key

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

Table of Contents
outlinh1. true
outlinh1. true
1printablefalse
2stylh1. none
3indent20px

A simple way to reduce the number of jobs or job - chains for shell scripts is to use a generic job. job, job chain and orders:

Code Block
languagexml
titleExample Job (Windows)
  <job 
Code Block

  <[http://www.sos-berlin.com/doc/en/scheduler.doc/xml/job.xml job ]order="yes"
       stop_on_error="no"
       title="This job is a example showing the generic execution of a shell- script or a shell- command">
      <[http://www.sos-berlin.com/doc/en/scheduler.doc/xml/script.xml script ]<script language="shell">
          <![CDATA[
  '''echo %SCHEDULER_PARAM_SCRIPT2EXECUTE%'''
  '''%SCHEDULER_PARAM_SCRIPT2EXECUTE%'''
          ]]>
      </script>
      <[http://www.sos-berlin.com/doc/en/scheduler.doc/xml/run_time.xml run_time]<run_time/>
  </job>

This job will execute a script or a command which name that is specfied with the parameter "Script2Execute".

Putting Adding this job in to a job chain like the one belowthis:

Code Block
languagexml
titleExample Job Chain
  <job_chain
  <[http://www.sos-berlin.com/doc/en/scheduler.doc/xml/job_chain.xml job_chain] orders_recoverable="yes"
             visible="yes"
             title="ShellExecutor: generic Executionexecution of a shell- script or ashell command">
      <[http://www.sos-berlin.com/doc/en/scheduler.doc/xml/job_chain_node.xml job<job_chain_node] state="Step.100"
                      job="GenericShellExecutor"
                      next_state="success"
                      error_state="error"/>
      <[http://www.sos-berlin.com/doc/en/scheduler.doc/xml/job_chain_node.xml job<job_chain_node] state="success"/>
      <[http://www.sos-berlin.com/doc/en/scheduler.doc/xml/job<job_chain_node.xml job_chain_node] state="error"/>
  </job_chain>

will start this job every time an order for the job chain is scheduled like this one:

Code Block
languagexml
titleExample for Order
  <order>
  <[http://www.sos-berlin.com/doc/en/scheduler.doc/xml/order.xml order]>
      <[http://www.sos-berlin.com/doc/en/scheduler.doc/xml/params.xml params]><params>
          <[http://www.sos-berlin.com/doc/en/scheduler.doc/xml/param.xml param ]<param name="Script2Execute"
                 '''value="dir c:\temp"/>'''
      </params>
      <[http://www.sos-berlin.com/doc/en/scheduler.doc/xml/run_time.xml run_time]<run_time let_run="no"/>
  </order>

At the end, one have to create for each script/command to execute an additional order.

...