...

• A job is the basic unit what to execute with an Agent.
• Job implementations come with 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.
    • Consider that jobs executed by an Agent cannot successfully request interaction from a console or from a user. If the application, command, script or binary file that is executed tries to bring up a popup window for user interaction then this will fail as in scheduling mode there is no console window to display messages and to request a user to confirm a popup window.
  • JVM Jobs are can be 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.

Job 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 and JS7 - If Instruction.

Job Parameterization

Jobs can be parameterized from the following sources:

• Shell Jobs
  • The Agent provides JS7 - Job Environment Variables that are available for any shell jobs.
  • Order variables and job node arguments are exposed as environment variables from a mapping that is performed at job level, see below.
• JVM Jobs
  • Jobs running in a JVM provided by the Agent are forwarded a parametrization object that holds similar information as from environment variables for shell jobs.

Job Configuration

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

...