Introduction
Each product brings its own wording, this also applies to JS7. Therefore, find explanations from the following sections about
- the wording for objects used with JS7,
- the mapping of terms used with the predecessor product JS1 (branch 1.x).
Terminology with JS7
Generic Term | Specific Term | Meaning |
---|---|---|
Job | The smallest unit of what can be executed on a given machine, for example from the command line (shell) of the operating system. Jobs are stateless objects, the instance of a Job is called a Task. Jobs are available as Shell Jobs and they can run in a Java Virtual Machine as JVM Jobs, see JS7 - Job Templates. For details see JS7 - Job Instruction. | |
Task | The instance of a Job that is executed. A Job can run in a number of parallel Tasks. | |
Process | The operating system view of a Task. In addition, Tasks can have child Processes. | |
Return Code | A summary term for the Exit Code of a Process and the Return Code provided by Jobs running in a JVM. | |
Exit Code | An Exit Code is returned by a terminating Process. This includes that shell Jobs return Exit Codes, JVM Jobs do not return Exit Codes as their Tasks can be re-used. Instead, JVM Jobs complete with a Return Code. | |
Workflow | 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 that run independently from 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 to execute a single Job. Frequently used synonyms include the terms Job Net, Job Stream. | |
Instruction | Instructions implement Workflow Patterns such as Fork/Join, a Sequence etc. Instructions rule job dependencies, see JS7 - Workflow Instructions. | |
Node | The position of an Instruction, for example to execute a Job, in a Workflow. Nodes are assigned labels that allow to recognize steps in a Workflow. | |
Workflow Pattern | A number of Nodes that are implemented by Instructions in a Workflow. Instructions include for example to execute a Job or to fork processing according to a Workflow Pattern. For details see JS7 - Workflow Patterns. | |
Sequence | A Workflow Pattern that implements sequential execution of Instructions in a Workflow. | |
Order | Orders represent triggers for the execution of Workflows.
| |
Timed Order | Such Orders are automatically created by a Schedule that determines when to run the Order and what parameterization to apply. | |
Ad hoc Order | Such Orders are added by users or from external applications on-the-fly. | |
File Order | An Order that is represented by an incoming file, see JS7 - File Watching. | |
State | Orders are stateful objects that pass a number of State Transitions during lifetime. States include for example to be scheduled for later execution, to wait for resources, to be running, to be failed etc. | |
State Transition | Orders are subject to State Transitions when moving from one State to the next. The 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. | |
Event | Events signal State Transitions of Orders. They are used for example to automatically update information in the JOC Cockpit GUI about Orders being running, waiting, failed etc. | |
File Order Source | The scheduling object that defines a source for File Orders, for example the directory that should be watched for incoming files, for details see JS7 - File Watching. | |
Resource Lock | Resource Locks implement mutual exclusion and can be used to limit parallelism of Jobs, for details see JS7 - Resource Locks. | |
Job Resources | Job Resources are used to propagate variables and to inject environment variables to shell Jobs. They are a flexible means to parameterize Workflows and Jobs, for details see JS7 - Job Resources. | |
Notice Boards | Notice Boards implement job dependencies, for example to make a Job wait for some other Job in a different Workflow, for details see JS7 - Notice Boards. | |
Script Includes | Script Includes are re-usable pieces of shell code that can be added to Job scripts, for details see JS7 - Script Includes. | |
Calendar | Calendars determine the days that are 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 Monday, to the 1st Tuesday in month, to For details see JS7 - Calendars | |
Schedule | Schedules make use of Calendars that specify possible days for Workflow execution. A Schedule can create Orders for any days of the assigned Calendar and it can further restrict for which days to create Orders.:
For details see JS7 - Schedules. | |
Order Template | The configuration object of an Order that includes default parameters and run-time settings.
| |
Status | The status of an object, e.g. of a Job, Task, that do not know of transitions. In JS7 Jobs and Tasks do not represent objects with a status. | |
Terminology Mapping with JS1
Wording JS1 | Wording | Meaning | Comments | Wording JobScheduler1 |
---|---|---|---|---|
Job | Job | The configuration object of what should be executed. Jobs are stateless objects, the instance of a Job is called a Task. | Meaning changed. | |
Job Chain | Workflow | |||
Order | Schedule | The instance of an Order Template that is scheduled for execution.
| ||
Exit Code | An exit code is returned by a process, this includes that shell jobs will return exit codes, API jobs do not return exit codes (as the task can be re-used). Instead, API jobs and job steps complete with a Return Code. | Exit Code | ||
File Group | A number of File Orders that are expected to be available. Processing continues if all expected File Orders are present, otherwise missing File Orders are waited for. | n/a | ||
File Order | An Order that is represented by a file. | Meaning unchanged. | File Order | |
Instruction | Instructions implement Workflow Patterns such as e.g. fork/join. They represent configuration elements that rule job dependencies. | |||
Job Net | Synonym for the term Workflow. | n/a | ||
Node | The position of a Job in a Workflow. Synonym to the term Step. Nodes are assigned labels that include free text to allow recognizability of a step in a Workflow. | Node | ||
Order | The instance of an Order Template that is scheduled for execution.
| Ad Hoc Order | ||
Order Template | The configuration object of an Order that includes default parameters and run-time settings.
| Permanent Order | ||
Return Code | A summary term for the Exit Code of a process and the Return Code provided by API Jobs. | Meaning unchanged. | Return Code | |
State | A state is not used in JS7. Instead the term Node is used and the content of a state in JobScheduler1 is moved to a Node Label in JS7. | State | ||
Sequence | A Workflow Pattern that implements sequential execution of job nodes. | Meaning changed. | Job Chain | |
Status | The status of an object, e.g. of a Job, Task, that do not know of transitions. In JS7 Jobs and Tasks do not represent objects with a status. | Meaning changed | Status | |
State | The state of an object that is subject to transitions, e.g. an Order. In JS7 the Order is the only object that knows a state. | Meaning changed | State | |
Task | The instance of a Job that is executed. | Meaning unchanged. | Task | |
Transition | A Transition follows a Node in a Workflow Pattern. It causes an Order to be moved to the next Node. Transitions are signaled by Events. | n/a | ||
Workflow Pattern | A number of Jobs that are organized by Instructions in Nodes. Instructions include e.g. to fork processing within a Workflow Pattern. | JobScheduler1 knows but job chains as a workflow pattern. | n/a | |
Workflow | The instance of a Workflow Pattern that is used for an Order. A Workflow is started by an individual Order or by a number of Orders. Workflows for parallel Orders are instantiated independently from one another. | n/a | ||