...
There was an event handling mechanism that works as an add on to the JobScheduler. Event handler determines on which condition what jobs should be started. Now this "Job Streams" feature adds a capability to the product which allows graphical configuration of job dependencies. This feature is provided by a JobScheduler SOS Conditions Plugin. The plugin <plugin java<plugin java_class="com.sos.eventhandlerservicejobstreams.pluginplugins.SOSConditionsPluginJobStreamsPlugin"/> > should be enabled to allow the use of the Job Streams functionality, see Jira server SOS JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 6dc67751-9d67-34cd-985b-194a8cdc9602 key SET-181
...
Step 1
Edit thescheduler.xml
file present in theSCHEDULER_DATA/config
directory of JobScheduler Master.Step 2
By default the plugin <!-- plugin java_class="com.sos.eventhandlerservicejobstreams.pluginplugins.SOSConditionsPluginJobStreamsPlugin"/ --> is commented out. Remove the comment from the configuration.
Code Block | ||||||
---|---|---|---|---|---|---|
| ||||||
<?xml version="1.0" encoding="iso-8859-1" standalone="no"?> <spooler> <config mail_xslt_stylesheet="config/scheduler_mail.xsl" http_port="40444"> <params> <param name="scheduler.variable_name_prefix" value="SCHEDULER_PARAM_"/> <param name="scheduler.order.keep_order_content_on_reschedule" value="false"/> <param name="sos.use_notification" value="false"/> </params> <plugins> <plugin java_class="com.sos.scheduler.engine.plugins.newwebservice.NewWebServicePlugin"/> <plugin java_class="com.sos.scheduler.engine.plugins.nodeorder.NodeOrderPlugin"/> <plugin java_class="com.sos.jitl.inventory.plugins.InitializeInventoryInstancePlugin"/> <plugin java_class="com.sos.jitl.reporting.plugin.FactPlugin"/> <plugin java_class="com.sos.eventhandlerservicejobstreams.pluginplugins.SOSConditionsPluginJobStreamsPlugin"/> </plugins> <process_classes> <process_class max_processes="100"/> </process_classes> </config> </spooler> |
...