Page History
...
Generic Term | Specific Term | Meaning |
|---|---|---|
| Controller | Standalone Controller | A Controller knows what which Workflows and Jobs to execute, when to execute and with which Agents are to executebe used for execution. A Controller receives receives the job-related inventory from the 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 which orchestrates Agents. |
| Controller Cluster | A Controller is clustered for high availability by with two instances, one being active and one being in standby mode. A manual switch-over and an automated fail-over between instances can occur. For details see see JS7 - Controller Cluster. | |
| Agent | Standalone Agent | Agents execute Jobs that call executable files and commands on the Agent's server. Agents receive the information what from a Controller about which Jobs to start and when to start from a Controller and them. Agents report back execution results and log output to the Controller. Agents can act autonomously without a Controller being connected at the point in time of job execution. Standalone Agents act independently from of each other. |
| Agent Cluster, Subagent | Agent instances that are clustered for high availability and for performance are called Subagents. If a Subagent fails in an active-passive Cluster then automated fail-over takes place. In an active-active Cluster a number of Subagents run Tasks for the same applications in parallel and can replace each other. A Cluster is is a logical layer that allows to select selection of any number of of Subagents for Task execution. Selection can be in fixed-priority mode or in round-robin mode. Subagents can participate in any number of Clusters. For details see JS7 - Agent Cluster. | |
| Director Agent | Agent Clusters work autonomously, they include primary and secondary Director Agent instances that act as a passive Cluster and that implement automated fail-over. Director Agents communicate with a Controller and orchestrate Subagents in the Cluster. | |
| JOC Cockpit | Standalone JOC Cockpit | JOC Cockpit is the user interface to manage for managing the job-related inventory and to monitor & control Workflow execution with Controllers and Agents. A Standalone JOC Cockpit is a single instance that can be used to manage one or more Controllers. |
| JOC Cockpit Cluster | A number of JOC Cockpit instances act instances act in a passive cluster for providing high availability that allows and allowing manual switch-over and automated fail-over between instances. For details see see JS7 - JOC Cockpit Cluster. |
...
Generic Term | Specific Term | Meaning |
|---|---|---|
| Deployment | Deploy | Deployment includes forwarding objects to Controllers and Agents that store deployed objects with their respective journal. This applies to objects such as Workflows, Job Resources, Resource Locks etc. For details see JS7 - Deployment of Scheduling Objects. |
| Revoke | Users can Revoke a Deployment which forces deletion of the respective scheduling object from Controllers and Agents. | |
| Submission | Submit | Submission includes adding Orders to Controllers and Agents. Submitted Orders can be cancelled or suspended.. For details see JS7 - Daily Plan. |
| Releasing | Release | Release of objects includes making JS7 - Calendars and JS7 - Schedules available for processing by the Daily Plan. |
| Rollout | Rollout | Scheduling objects are rolled out to separate environments, for example for a sequence of dev -> test -> prod environments. For details see JS7 - Rollout of Scheduling Objects. |
...
Overview
Content Tools