Scope

• JOC is turning towards its end of life and shall be replaced by a new component.
• The scope of the new JOC Cockpit is currently in discussion.

Cockpit

Functional Requirements

• Basically the existing functionality shall be provided.
• Visualisation of more details, e.g. for history.
• Support for multiple JobScheduler instances
  • Cluster Instances
  • Supervisor and Workload Instances
  • Master and Slave Instances
• Authentication via Apache Shiro
• Authorisation via Apache Shiro
  • Management of permissions, e.g. for folders and GUI operations.
  • Grouping of permissions to roles.
  • Associating roles to users.
• Workload visualisation
• Calendar preview

Non-Functional Requirements

• Reduced impact of JOC operations on the JobScheduler main process.
• Consistent logging.

Usability Requirements

• Improved navigation.
• Improved graphical presentation.
• Better responsiveness of the GUI.
• Responsive Design for use with devices as e.g. tables.

Architecture

• JOC will be completely re-written.
• A new framework will be introduced that currently is being decided on. 
• Introduction of an interface between JOC and JobScheduler
  • Presumably the Jetty Web Server will operate that interface.