Page History
...
- The JOC Cockpit, which is used to manage the inventory JS7 - Inventory of scheduling objects, to monitor and control workflow execution and to access the JS7 - History.
- The Controller, which is used to orchestrate Agents, to pass orders for workflow execution to Agents and to deploy workflows and the JS7 - Daily Plan to Agents.
- Agents, which are dedicated to a Controller and are used to execute workflows and jobs. Agents act autonomously for workflows that execute all included jobs with the same Agent.
...
- Any connections are unilateral to simplify network access.
- Connections can be secured by TLS/SSL certificates.
...
- Components
- JOC Cockpit: manages workflow configuration, monitors and controls workflow execution
- Controller: orchestrates Agents, manages workflow execution
- Agents: execute workflows and return the execution history and log output
- Operation
- JOC Cockpit can be operated in the following modes:
- as a standalone instance,
- as a cluster with one active instance and any number of standby instances.
- The Controller can be operated:
- as a standalone instance,
- as a cluster with one active instance and one standby instance.
- Agents can be operated:
- as a single instance,
- as a passive cluster with one active instance and any number of standby instances,
- as an active cluster with any number of active instances.
- JOC Cockpit can be operated in the following modes:
- Network Connections
- JOC Cockpit connects to Controller instances and connects to a database
- Controllers connect to Agents
- Network connections are firewall friendly, a single connection is initiated established between each component
- Platforms
- JOC Cockpit: Windows, Linux
- Controller: Windows, Linux
- Agent: any platform that provides a Java Virtual Machine
- Setup Scenarios
- Standalone Server
- High Availability Controller
- High Availability Controller and JOC Cockpit
- Multi-Client Capability
- High Availability Agents
...
Overview
Content Tools