Product Knowledge Base

Space shortcuts

Page tree

Versions Compared

Old Version 30

changes.mady.by.user Andreas Püschel

Saved on

compared with

New Version Current

changes.mady.by.user Alan Amos

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: 'cluster' added

...

Excerpt

The introduction of the JobScheduler Operating Center (JOC) Cockpit brings the following architecture:

  • The JOC Cockpit is accessible with any standard browser from a number of end user devices including tablets.
  • The JOC Cockpit makes use of a web service architecture and is installed separately from a JobScheduler Master.
  • The JobScheduler Web Service provides the necessary information for the JOC Cockpit as well as handling the communication with JobScheduler Masters.

The Web Service can be addressed by any number of JOC Cockpit instances and by external programs such as ERP applications.

Multiple instances of the JobScheduler Web Services can be linked up to form a cluster for high availability. (Feature introduced with Release 1.12.1.)

 

The diagram below provides a schematic view of a typical JobScheduler environment using the JOC Cockpit.

...

HTTP/HTTPS is used for communication between the RESTful Web Services Service and the JOC Cockpit - or other applications.

The web service Web Service uses JSON and XML based commands and responses to communicate with the JobScheduler Master(s). In addition events Masters. Events about object status changes are communicated between the JobScheduler Masters and the Web Service and the JobScheduler Masters.

Communication between the JobScheduler Masters and Agents takes place using HTTP/HTTPS RESTful web service .

...

Authentication and authorization is carried out by an Apache Shiro framework integrated into the JOC CockpitWeb Service:

  • authentication is carried out against a local configuration or an LDAP directory
  • authorization is carried out against role-based group permissions.

...