A Controller knows what Workflows and Jobs to execute, when to execute and with which Agents to execute. A Controller receives the job-related inventory from JOC Cockpit and deploys this information to Agents which execute Workflows and Jobs on the respective servers. A Standalone Controller is a singe instance that orchestrates Agents.

A number of JOC Cockpit instances act in a passive cluster for high availability that allows manual switch-over and automated fail-over between instances. For details see JS7 - JOC Cockpit Cluster.

Jobs come in two flavors: Shell Jobs specify job scripts that are executed for an operating system shell, JVM Jobs specify use of a Java class, see JS7 - Job Templates.

For both usages the Job defines what should be executed. At the point in time when a Job is started it is called a running Task, i.e. the instance of a Job.

A Job specifies what is executed on a given machine, for example, the commands in a shell of the operating system. Jobs are stateless objects, Tasks are stateful objects that can be started, killed etc.

For details see JS7 - Job Instruction.

A Workflow is started by an Order that passes the Nodes and Instructions included with the Workflow. Any number of Orders can execute the same Workflow in parallel instances running independently of each other.

The succession of Instructions in a Workflow implements a Workflow Pattern, for example a Sequence. However, the most simple Workflow Pattern can include execution of a single Job.

Frequently used synonyms include the terms Job Net, Job Stream. For details see JS7 - Workflows.

Orders represent triggers for execution of Workflows.

• Order is the summary term for any Order instance, such as Timed Orders, Ad hoc Orders, File Orders.
• Orders are executed just once for a given date and time.
• If an Order meets a Fork/Join Instruction in a Workflow then this results in a number of Child Orders being created.

For details see JS7 - Orders.

Orders are stateful objects that pass a number of State Transitions during their lifetime. States include, for example, being scheduled for later execution, waiting for resources, running, failed, etc.

Orders are subject to State Transitions when moving from one State to the next. JS7 implements a Finite-state Machine with non-deterministic transitions that can be considered a Directed Acyclic Graph.

State Transitions are signaled by Events. For details see JS7 - Order State Transitions.

Resource Locks implement mutual exclusion and can be used to limit parallelism of Jobs. For details see JS7 - Resource Locks.

Calendars determine the days that are considered by Schedules when creating Orders. For example, a business day Calendar can specify Monday to Friday as possible days for Workflow execution. A Schedule that is assigned this Calendar can further restrict execution to more specific days. For details see JS7 - Calendars.

Schedules make use of Calendars that specify possible days for Workflow execution. Schedules can create Orders for any days of the assigned Calendar and they can further restrict the days on which Orders are created.:

• Schedules create and parameterize Orders for execution of Workflows.
• Schedules can restrict execution dates of a Calendar, for example, creating Orders exclusively for Mondays, for the 1st Tuesday in the month, for the last day of the month, etc.
• Schedules determine the point in time during the day when an Order should be executed.

For details see JS7 - Schedules.