Job JobSchedulerManagedDatabaseJob

This job is used as a standalone solution or triggered by orders to execute statements in a database.
These can be database procedures or SQL statements.

The description JobSchedulerManagedDatabaseJob.xml is stored in the ./jobs directory of your Job Scheduler installation.

The SQL instructions are written in the command parameter.
It is possible to define more than one instruction in the command parameter.
Such instructions are then carried out in the order in which they are written and must be separated by a semicolon and a subsequent new line.

The Managed Jobs PHP web interface provides a textarea for this, while in the Job Scheduler Object Editor (JOE), only an input field is available.
PHP converts the textarea hexadecimal because a newline cannot be written in an XML attribute (see also Why_have_the_command_parameter_of_some_jobs_a_hexadecimal_coded_value%3F).
If you want to use the job with multiple statements without the Managed Jobs, then the statements should be changed hexadecimal or you use 
 as newline.

The following is an example of a job chain in which the command contains two statements separated by .

The job chain launchDB.job_chain.xml:

 <[http://www.sos-berlin.com/doc/en/scheduler.doc/xml/job_chain.xml job_chain] orders_recoverable="yes" visible="yes">
     <[http://www.sos-berlin.com/doc/en/scheduler.doc/xml/job_chain_node.xml job_chain_node] state="launch"  job="launchDB" next_state="success" error_state="error"/>
     <job_chain_node state="success"/>
     <job_chain_node state="error"/>
 </job_chain>

The order launchDB,updateMyTable.order.xml:
It contains an update statement and a commit. The value of the statement_newline parameter is used as separator.

 <[http://www.sos-berlin.com/doc/en/scheduler.doc/xml/order.xml order] title="update MY_TABLE">
     <params>
         <param name="command"        value="update MY_TABLE set a='foo' where b='bar';&amp;#10;commit;"/>
     </params>
     <run_time/>
 </order>

The job launchDB.job.xml:
It executes the statements.

 <[http://www.sos-berlin.com/doc/en/scheduler.doc/xml/job.xml job] title="Launch Database Statement" order="yes" stop_on_error="no">
     <description>
         <include file="jobs/JobSchedulerManagedDatabaseJob.xml"/>
     </description>
     <params>
         <param name="db_class"        value="SOSMySQLConnection"/>
         <param name="db_driver"       value="com.mysql.jdbc.Driver"/>
         <param name="db_url"          value="jdbc:mysql://localhost:3306/scheduler"/>
         <param name="db_user"         value="scheduler"/>
         <param name="db_password"     value="scheduler"/>
         <param name="command"         value=""/>
     </params>
     <script language="java" java_class="sos.scheduler.managed.JobSchedulerManagedDatabaseJob"/>
     <run_time/>
 </job>

If you prefer a shell solution, then you need only one (standalone) job and a database client:

 <[http://www.sos-berlin.com/doc/en/scheduler.doc/xml/job.xml job] title="Launch Database Statement">
     <params>
         <param name="statement_newline"       value="__x0A__"/>
         <param name="statements"              value="update MY_TABLE set a='foo' where b='bar';__x0A__commit;"/>
         <param name="db"                      value="scheduler"/>
         <param name="db_user"                 value="scheduler"/>
         <param name="db_password"             value="scheduler"/>
     </params>
     <script language="shell">
         <![CDATA[
  echo $SCHEDULER_PARAM_STATEMENTS | sed -e 's/'$SCHEDULER_PARAM_STATEMENT_NEWLINE'/\n/g' > myupdate.sql
  mysql -u$SCHEDULER_PARAM_DB_USER -p$SCHEDULER_PARAM_DB_PASSWORD $SCHEDULER_PARAM_DB < myupdate.sql
  mysqlErr=$?
  rm myupdate.sql
  exit $mysqlErr
         ]]>
     </script>
     <run_time/>
 </job>

Space shortcuts

Page tree