Product Knowledge Base

Space shortcuts

Page tree

Versions Compared

Old Version 14

changes.mady.by.user Andreas Püschel

Saved on

compared with

New Version Current

changes.mady.by.user Andreas Püschel

Saved on

Key

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

Table of Contents

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_class="com.sos.eventhandlerservice.plugin.SOSConditionsPlugin"/> should be enabled to allow use of the Job Streams functionality, see 

Jira
serverSOS JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId6dc67751-9d67-34cd-985b-194a8cdc9602
keySET-181
There are two points in time when the Job Streams functionality can be enabled:

  1. At the time of installation
  2. After the installation

How to enable the Job Streams Functionality at the time of Installation

...

You just need to enable the Conditions-Job Streams Plugin via a checkbox at Step 9 of the installation process. 


How to enable the Job Streams Functionality after Installation

...

The scheduler.xml configuration file of JobScheduler Master can be used to enable the Job Streams functionality like this:

  • Step 1

    Edit the scheduler.xml file present in the SCHEDULER_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
languagexml
titleConfiguration file scheduler.xml
collapsetrue
<?xml version="1.0" encoding="iso-8859-1" standalone="no"?>
<spooler>
		<config mail_xslt_stylesheet="config/scheduler_mail.xsl" http_port="40130" port="4130"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>

				<security ignore_unknown_hosts = "yes">
						<allowed_host host = "localhost" level = "all"/>
				</security>
			
				<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>

  • Step 3

    Restart JobScheduler Master after updating the SCHEDULER_DATA/config/scheduler.xml file to apply your changes.

...