Scope
- The implementation architecture explains
- components used,
- embedding of components and
- component communication.
Implementation Architecture
- Download: JS7_JobScheduler_Implementation_Architecture.pptx
- Download: JS7_JobScheduler_Implementation_Architecture.pdf
- Download the slides from above links should display of the below document not work for your browser:
JOC Cockpit Implementation Architecture
- 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 Controller.
- 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.
- manages a number of backend services:
- JOC Event Bus
- An event bus manages communication between JOC Cockpit services:
- events are published in a producer/consumer (publish/subscribe) model,
- events are asynchronous, i.e. a service does not rely on immediate responses,
- events are not persistent, i.e. they are removed after being consumed or after some timeout,
- events are considered informational for the user interface that displays current data,
- events are not intended for historical retrieval.
- An event bus manages communication between JOC Cockpit services:
- Controller Proxy
- The Controller Proxy on start-up will retrieve a snapshot of the Controller's journal and will subsequently receive any events fired by a Controller.
- The Controller Proxy implements an event queue that can be subscribed to by a number of consumers.
Controller/Agent Implementation Architecture
TODO
Overview
Content Tools