You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 11
Next »
Introduction
JobScheduler can be implemented for different architectures:
- Single Server Operation
- Cluster Operation
- Failover is provided by either an active or passive cluster:
- Passive Cluster with Primary JobScheduler and Backup JobScheduler in stand-by mode
- Active Cluster with multiple JobScheduler instances in balanced mode
- Depending on the type of cluster, load balancing is also possible
- Jobs & orders are executed on remote servers via SSH
- Master / Agent Cluster
- Operating Master JobScheduler and Agent JobScheduler on different platforms for cross-platform scheduling
- Jobs & orders are executed on remote servers by Agents and via SSH (Agentless Scheduling)
- Supervisor
- Operating a Supervisor JobScheduler for central configuration
Architecture Decision Template
Error rendering macro 'viewpdf'
com.atlassian.confluence.macro.MacroExecutionException: com.atlassian.confluence.macro.MacroExecutionException: The viewfile macro is unable to locate the attachment "JobScheduler_Architecture_Decision_Template.pdf" on this page
Resources
Architecture in Detail
-
Page:
-
Page:
-
Page:
-
Page:
-
Page:
-
Page:
-
Page:
-
Page:
How To ... Instructions
-
Page:
-
Page:
-
Page:
-
Page:
-
Page:
Frequently Asked Questions
Examples in detail