Introduction

...

• JOC Cockpit can be operated in the following modes:
  • single instance,
  • active-passive clustered instances with one active instance and any number of standby instances.
• Cluster Service
  • manages a number of Background Services:
    • JS7 - Monitor Service: checks execution history for events that users receive JS7 - Notification for.
    • JS7 - Cleanup Service: purges the JS7 - Database to limit for example the size of the history.
    • JS7 - History Service: receives execution results and logs from a Controller instance.
    • JS7 - Daily Plan Service: creates and submits orders to Controllers on a daily basis.
  • guarantees service execution:
    • checks the cluster health status of any connected JOC Cockpit instances,
    • performs a fail-over operation in case the active JOC Cockpit instance fails.
• Event Bus Service
  • 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 a timeout,
    • events are considered informational for the user interface that is updated in near real-time.
• Proxy Service
  • On start-up the Proxy will retrieve a snapshot of the Controller's journal and will subsequently receive any events fired by a Controller.
  • The Proxy implements an event queue that can be is subscribed to by a number of consumers, for example by Background Services and by the GUI.

...