Page History

JobScheduler can be implemented for different architectures:

• JOC Cockpit user interface
• JobScheduler Web Service
• JobScheduler Master and Agents
  • Single Server Operation
  • Cluster Operation
  • for high-availability
    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
    • • active load-sharing mode
    • Master / Agent Cluster
      • Operating JobScheduler Master and JobScheduler
      and
      • Agent
      JobScheduler
      • on different platforms for
      cross
      • Cross-
      platform scheduling
      • Platform Scheduling
      • Jobs
      & orders
      • are executed on remote servers by Agents (JobScheduler Universal Agent) and via SSH (Agentless Scheduling)
    • Agent Cluster
      
      • Operating a number of Agents for failover with fixed priority and round-robin scheduling.
    • Supervisor
      • Operating a JobScheduler Supervisor
      JobScheduler for central configuration

• • • for Central Configuration