Page History

...

1. JobChainA contains 3 Task nodes i.e. TaskA1,TaskA2,TaskA3
2. JobChainA contains 1 job node i.e. Submit_End_Event, which will send a EVENT notification to JobScheduler that job has finished.
3. JobChainB also contains 3 Task nodes i.e. TaskB1,TaskB2,TaskB3
4. JobChainB contains 1 job node i.e. Check_End_Event, which will check if required EVENT notification is present in the JobScheduler DB.

Requirements

1. The JobScheduler must run using a database.
2. The JobScheduler must be installed with the Event-Service (JobChain sos/
   Image Added
3. events are stored permanently in the table "SCHEDULER_EVENTS".

Instructions

• Unzip all files of test_event.zip into the ./config folder of your active instance of the eventservice JobScheduler installation. After unzipping you will have all the objects needed to run the example in the live/test_events subfolder.
• Open the JS operations gui for the workload JobScheduler in your browser using http://scheduler_host:scheduler_port
• Find the {{test_event/job chain_example_wait_for_event }} job chain and click on it.
• There is an order assigned to the job chain. In the order menu press Start order now
• You see the order will run until the step 3 is reached. As the EVENT event does not exist, the order will wait for 10s and then check again.
• Switch to the tab Jobs.
• Find the {{test_event/job_event_add }} job chain and click on it.
• In the Job menu press Start task immediately. This will create the EVENT event.
• Switch to the tab Job Chains.
• See the order proceeding with execution of the next step

...