Purpose

• Instructions to execute jobs are basic to workflow automation.
• Any number of jobs can be executed in a workflow.

Job

• A job is the basic unit what to execute with an Agent.
• Job implementations come in the following flavors:
  • Shell Jobs are executed with the operating system shell, e.g. the Windows Shell or one of the Unix Shells such as /bin/sh, /bin/bash etc.
    • Shell jobs include to call any shell commands, scripts and executable files.
    • Such jobs behave similarly to individual commands being executed in the command line of the operating system.
    • Shell jobs include to use scripting languages such as Perl, Ruby, Python, PowerShell etc. for which an interpreter is installed with the OS that can be executed from the command line.
  • JVM Jobs are implemented in a number of supported languages that can be operated for a Java Virtual Machine and for which the Agent exposes JS7 - Order Variables and job node arguments. Job implementation languages include
    • Java: such jobs are executed in the JVM provided by the Agent.
    • JavaScript, Ruby, Python etc.: such jobs require use of a GraalVM® Java Virtual Machine that provides the compiler for the respective scripting language.

Relationships

• A workflow can include any number of jobs.
• A job is assigned an Agent that executes the job.
  • Within a workflow jobs can be executed by different Agents (cross-platform scheduling)
• A workflow can include additional instructions
  • to manage job dependencies, e.g. by use of the JS7 - Fork / Join Instruction, 
  • to manage job resources, e.g. by use of the JS7 - Lock Instruction
  • to manage error handling, e.g. by use of the JS7 - Try / Catch Instruction and JS7 - Retry Instruction

Configuration

Jobs are managed from the JOC Cockpit Configuration -> Inventory View.

The tree panel offers the Workflows category to select and display a workflow with the JS7 - Workflow Editor.

• Jobs can be added from the Instruction Panel by dragging and dropping from the  icon.
• When a job is selected then this causes the Job Property Editor to be displayed.