Components
- JOC Cockpit: manages the workflow and job inventory, monitors and controls workflow execution
- Controller: orchestrates Agents, manages workflow execution
- Agents: start 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.
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 established between each component
Platforms
- JOC Cockpit: Container, Linux, Windows
- Controller: Container, Linux, Windows
- Agent: Container, Linux, Windows, any platform that provides a Java Virtual Machine
Setup Scenarios
- Cloud
  - JOC Cockpit and Controller High Availability
  - Agent High Availability
  - Hybrid Use of Agents
- On Premises
  - Standalone Server
  - Controller High Availability
  - Controller and JOC Cockpit High Availability
  - Multi-Client Capability
  - Agent High Availability

Space shortcuts

Page tree