Scope

The implementation architecture explains
- components used,
- embedding of components and
- component communication.

Implementation Architecture

Download: JobScheduler_Implementation_Architecture.pptx
Download: JobScheduler_Implementation_Architecture.pdf
Download from above links should display of the 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_Implementation_Architecture.pptx" on this page

JOC Cockpit can be operated in the following modes:
- single instance,
- active-passive clustered instance with a primary instance and backup instance,
- active passive clustered instance with a primary instance and any number of backup instances.
The JOC Cluster Service
- manages a number of backend services:
  - Job Streams Service: manage job starts, monitor tasks and calculate events for dependency management.
  - History Service: retrieve the job execution and log output of jobs executed with Agents.
  - Daily Plan Service: submit orders for the daily plan to JobScheduler Master.
  - Monitor Service: check execution history for events that users should be notified about.
- operates backend services for active or passive mode:
  - in active mode any of the services will perform active tasks, e.g. the Job Streams Service will start tasks,
  - in passive mode any of the services will report status information about the result of active tasks.
- guarantees service execution
  - for the Active JOC Cockpit instance in service active mode,
  - for any Passive JOC Cockpit instance in service passive mode.
- forwards service execution requests originating from a Passive JOC Cockpit instance to the Active JOC Cockpit instance.