JS24 - System Architecture

Scope

The system architecture explains
- system boundaries
- components
- platforms
- setup scenarios

Download: JobScheduler_System_Architecture.pdf
Download: JobScheduler_System_Architecture.pptx
Download from above links should display of the below document not work for your browser:

Error rendering macro 'viewppt'
com.atlassian.confluence.macro.MacroExecutionException: com.atlassian.confluence.macro.MacroExecutionException: The viewfile macro is unable to locate the attachment "JobScheduler_System_Architecture.pptx" on this page

Components
- JOC Cockpit: manage configuration, monitor and control job execution
- Master: orchestrate Agents, manage job executions and state transitions
- Agents: execute jobs and return job execution history and log output
Operations
- JOC Cockpit can be operated in the following modes:
  - as a single instance,
  - as an active-passive clustered instance with a primary instance and a backup instance,
  - as an active passive clustered instance with a primary instance and any number of backup instances.
- The Master can be operated
  - as a single instance,
  - as an active-passive clustered instance with a primary instance and a backup instance,
- Agents can be operated
  - as a single instance,
  - as an active-passive clustered instance with a primary instance and a backup instance,
  - as an active-active clustered instance with any number of Agent instances.
Network Connections
- JOC Cockpit
  - connects to a Master
  - connects to a database
- Masters connect to Agents
- Networks connections are firewall friendly, a single connection is initiated between components
Platforms
- JOC Cockpit: Windows, Linux
- Master: Windows, Linux
- Agent: any platform that provides a Java Virtual Machine
Setup Scenarios
- Standalone Server
- Master High Availability
- Master and JOC Cockpit High Availability
- Multi-Client Capability