...

• JOC Cockpit and Controller can each implement a passive cluster with an active node and a standby node.
• Agents can be operated standalone or as instances of a JS7 - Agent Cluster which implement active-passive or active-active scheduling.
  
  

Image Modified

Components

The components interact as described in the slide below:

...

• Any connections are unilateral.
• Connections can be secured by TLS/SSL certificates.
  
  

Image Modified

Setup Scenarios

Consider attached slides JS7_JobScheduler_System_Architecture.pdf for further setup scenarios.

Cloud Setup

A high availability setup includes to cluster JOC Cockpit, Controller and Agents. Components are deployed to separate availability zones like this:

Image Added

A hybrid approach suggests to use a cluster of JOC Cockpit instances and Controller instances from the Cloud. Agents can be integrated from the Cloud and from environments on premises:

Image Added

On Premises Setup

A cluster of JOC Cockpit instances and Controller instances can be used like this:

Image Added

Standalone Agents can be used and clustered Agents can be used for high availability like this:

Image Added

Summary

• 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
    Consider attached slides JS7_JobScheduler_System_Architecture.pdf for detailed scenarios.