• manage job configuration, optionally with a repository service
• manage release procedure for job configuration to Master
• accept job events and job history from Master
• report job events to event queue
• report job history to reporting database
• run authentication and authorization service
• run web server and web services
• run JobScheduler Controller Web GUI
• bundle a number of Masters and delegate commands to Master

Master

• implement a fault-tolerant peer-to-peer network of Agents
• accept daily plan from Master
• available for active-passive and active-active clustering:
  • fixed priority scheduling
  • round-robin scheduling

• execute job chains independently from Master availability
• resolve more complex dependencies with Master, e.g. for checks of the job history or of external events from other machines
• report job history and log information back to Master
• run distributed recovery files for recovery purposes
• allow access by a number of Master instances
• provide resilience features for reconciliation after Master connection loss