JobScheduling - sos-berlin.com

1 Software- und Organisations-Service GmbHGiesebrechtstr. 1510629 Berlin GermanyTelephone +49 30 86 47 90-0 Job AutomationJob SchedulingJOBSCHEDULERT echnical DescriptionApril 2016 JobScheduler2 Software- und Organisations-Service GmbHApril 2016 Contact InformationSoftware- und Organisations-Service GmbHGiesebrechtstr. 15D- 10629 BerlinTelephone +49 (30) 86 47 90-0 Telefax +49 (30) 8 61 33 35 Mail Updated: April 20161 Configuring the JobScheduler .. XML Configuration .. Example .. Coding the XML Configuration .. Configuration Schema .. Configuration Using Hot Folders .. Configuration Directory .. Files for Process Classes, Locks, Jobs, Job Chains and Permanent Orders .. Directory Mirroring with the JobScheduler .. Effects of the Change and Delete Commands .. Behaviour of Individual Object Types .. The <show_state> Command.

2 Central Configuration Using a Supervisor JobScheduler .. A Typical Configuration .. The Supervisor JobScheduler .. Registering a JobScheduler with the Supervisor JobScheduler .. Effectiveness of Local Changes to the Configuration .. Taking Over an Existing Configuration in the Central Administration .. Behaviour of the JobSchedulers on Starting .. File .. Settings which Allow Environment Variables with ${..} to be Called .. XML Attributes .. Files .. Files .. Command Line Operation .. JOE - JobScheduler Object Editor .. Configuration and Documentation of JobScheduler objects .. Database .. Settings .. Application Programming Interface .. Commands .. Error-Tolerance .. History .. 1. Purpose of the History .. 2. History File .. 3. Task Recognition and Extra Fields .. 4. Reading the History via the TCP Interface.

3 5. Error Handling .. Running the JobScheduler as a Service or Daemon .. Backup JobSchedulers .. JobScheduler Backup Cluster .. 1452 Jobs .. What is a Job? .. Job Configuration .. Implementation .. The Status of a Job .. Changing the Status of a Job .. Starting a Task .. Locks .. Directory Monitoring .. Monitor Scripts .. 154 JobScheduler3 Software- und Organisations-Service GmbHApril 2016 Table of Implementation of JobScheduler scripts as COM Classes .. Locks .. Lock Configuration .. Non-Exclusive Locking .. Locks in Job Chains .. External Job Processing with Agents .. Application .. Requirements for External Job Processing .. Configuration .. Monitor Scripts .. The Context of API Calls .. Configuration Files .. Log Files .. 1623 Order processing and File Monitoring .. Orders and Job Chains.

4 Job Chains .. Order Queue and Tasks .. Recognition of Double Orders .. Directory Monitoring with File Orders .. Priority .. Ending Tasks .. Accelerated Order Processing .. Database .. Directory Monitoring with File Orders .. File Order Sources .. File Monitoring With a File Order .. File Order Sink: Removes or Moves a File .. Blacklist .. Directory Errors .. When is a Directory Read? .. Order Controlled Non-API Jobs (<script language="shell">) .. Directory Monitoring .. Definition of a Directory Change: .. The Regular Expressions Filter .. The Directory in Which a Change has Taken Place .. The Files in the Directory .. Errors when Directory Monitoring .. Example .. Distributed Orders .. Distributed Order Processing .. 1704 Protocols and Forwarding of E-mails .. Logs .. Log File Size.

5 Message Codes .. Full Disc Drive .. Database Storage of Protocols .. Program Interface .. E-mail Forwarding .. Protocol Display .. Sending E-mails .. E-mail Settings .. E-mails Sent after Task Completion .. Settings Priorities .. E-mails Sent when the JobScheduler Terminates because of an Error .. Installation with JavaMail .. Log Categories .. 177 JobScheduler4 Software- und Organisations-Service GmbHApril 20165 Communication and Operation .. HTTP Server and Web Services .. Web Services .. Operation with a Browser .. Security .. Show Protocols in a Browser .. Job Descriptions .. Built-In Graphical User Interface .. XML Commands .. XML Answers .. Terminating the JobScheduler .. Correct Stopping .. Correct Stopping with a Time Limit .. Termination ..233 Appendix A: Messages .. Messages for the Scheduler Package.

6 Messages for the Separate processes Package .. Messages for the Charset Package .. 257 Appendix B: Change Log .. 258 Appendix C: SQL Instructions Used by the JobScheduler .. SQL Instructions Used by the JobScheduler for DB2 .. SQL Instructions Used by the JobScheduler for Microsoft SQL Server .. SQL Instructions Used by the JobScheduler for MySQL .. SQL Instructions Used by the JobScheduler for Oracle .. SQL Instructions Used by the JobScheduler for PostgreSQL .. SQL Instructions Used by the JobScheduler for Sybase ASE .. 351 Appendix D: Scripts in JavaScript .. Java-Exceptions in Spidermonkey .. 354 Index .. 356 JobScheduler5 Software- und Organisations-Service GmbHApril 2016 Configuring the JobScheduler6 Software- und Organisations-Service GmbHApril 20161 Configuring the XML ConfigurationThe file containing the XML configuration should be specified when starting the ExampleThe following shows a simple configuration file with a shell job:<?

7 Xml version=" "> <spooler> <config> <jobs> <job name="hello_world"> <script language="shell"> <![CDATA[echo hello world]]> </script> <run_time repeat="10"/> </job> </jobs> </config> </spooler>This example shows the configuration of thehello_worldjob, which the JobScheduler repeats every 10 this configuration is saved in , the JobScheduler could be started as follows (forWindows):..scheduler installation \bin\ -config= that if the JobScheduler has been started at the command line, it can be stopped using the "Ctrl-C" you could create individual configuration files per job, job chain etc. that would contain exclusively theelements required by these objects:<?xml version=" "> <job> <script language="shell"> <![CDATA[echo hello world]]> </script> <run_time repeat="10"/> </job>When this configuration is saved in a filescheduler installation path/config/ ,then it would be automatically used by a running the JobScheduler7 Software- und Organisations-Service GmbHApril Coding the XML Configuration<?

8 Xml encoding="UTF-8"?> and<?xml encoding="ISO-8859-1"?> are that the JobScheduler only processes 8 bit Characters (ISO-8859-1). Configuration SchemaThe JobScheduler verifies the XML configuration according to the JobScheduler XML Schema (Is only showncorrectly in IE).Clicking on an XML element in the schema list below leads to a description of the element:<spooler<configcentral_configura tion_directory = ".."configuration_add_event = ".."configuration_delete_event = ".."configuration_directory = ".."configuration_update_event = ".."include_path = ".."ip_address = ".."log_dir = ".."mail_xslt_stylesheet = ".."param = ".."port = "4444"priority_max = "1000"spooler_id = ""supervisor = ".

9 "tcp_port = "4444"udp_port = "4444">time_zone = ".."> <basefile=".."/> <params> <paramname=".." value=".."/> </params> <security> <allowed_hostname=".." level=".."/>..</security> <plugins> <plugin java_class=".."/>..</plugins> <clusterheart_beat_own_timeout = ".."heart_beat_timeout = ".."heart_beat_warn_timeout = ".."/> <process_classesignore = "no">Configuring the JobScheduler8 Software- und Organisations-Service GmbHApril 2016<process_classmax_processes = ".."name = ".."spooler_id = ".."> <remote_schedulersignore = "no"> <remote_schedulerremote_scheduler = ".."http_heartbeat_period = ".."http_heartbeat_timeout = ".."> </remote_scheduler> </remote_schedulers> </process_class>..</process_classes> <schedules> <schedulename = ".."substitute = ".."valid_from = ".."valid_to = ".

10 "/>..</schedules> <locks> <lockname= ".." ../>..</locks> <scriptcom_class = ".."filename = ".."java_class = ".."language = ".." > <includefile=".."/> <![CDATA[ ]]> </script> <http_server> < "basic"> < > < ".." password_md5=".."/>..< > < > <http_directorypath=".." url_path=".."/> <web_servicejob_chain=".." url_path=".." ..> <params> <paramname=".." value=".."/>..</params> </web_service>..</http_server> <holidays>Configuring the JobScheduler9 Software- und Organisations-Service GmbHApril 2016<holidaydate=".."/> <includefile=".."/> <weekdaysdate=".."/> </holidays> <jobs> <jobforce_idle_timeout = "yes|no"idle_timeout = ".."ignore_signals = ".."java_options = ".."min_tasks = ".."name = ".."order = "no"priority = ".."process_class = ".."spooler_id = ".."stop_on_error = "yes"tasks = "1"temporary = "no"timeout = ".