Product Knowledge Base

Space shortcuts

Page tree

Versions Compared

Old Version 24

changes.mady.by.user Alan Amos

Saved on

compared with

New Version 25

changes.mady.by.user Andreas Püschel

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Excerpt

The introduction of the JobScheduler Operating Center (JOC) Cockpit brings a significant change in the JobScheduler following architecture:

  • The JOC Cockpit is accessible with any standard browser from a number of end user devices including tablets.
  • The JOC Cockpit has a client - server makes use of a web service architecture and is installed separately from a JobScheduler Master.
  • The Cockpit client runs in a standard Internet browser and the server provides the JobScheduler Web Services.The JobScheduler Web Services JobScheduler REST Web Service provide the necessary information for the JOC Cockpit GUI as well as handling the communication with JobScheduler Masters.

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

 

...

  • Authentication and Authorization: The Web Services use an LDAP Directory for authentication, authorization is carried out against role-based group permissions data held on the WebServices server. This means that user access to particular resources can be restricted and that resources .
  • Multiple GUIsGUI instances: The JobScheduler Web Services can be accessed by more than one JOC Cockpit, so that, for example, an operator situated in a remote site can carry routine tasks at the same time as an administrator in the server room is configuring maintenance procedures.
  • 3rd Party Applications: External applications such as ERP systems can also access the Web Services and, for example, start jobs when they provide the correct authentication and authorization.
  • Multi-Client Capability: Any number of JobScheduler Masters can be controlled in a network via the Web Services as long as they are located in the same network.
  • Job Status and History: JobScheduler Masters record operational information in a database - this information can be called up from the JOC Cockpit via the Web Services.

Note also the following:

  • The JOC Cockpit can display workplan and job history information and functionally replaces JID, the JobScheduler Information Dashboard, which will not be delivered with the JobScheduler from version 1.11 onwards.
  • JobScheduler Universal Agents or Universal Agent Clusters cannot be directly controlled via the Web Services - this must take place via a JobScheduler Master.

Technical Details

The diagram below shows the JobScheduler JOC Cockpit Architecture at a more technical level. 

...

HTTP is used for communication between the RESTful Web Services and the JOC Cockpit - or other application - clientsapplications.

The Web Services use XML commands and responses to communicate with the JobScheduler Master(s). In addition events are communicated between the Web Services and the JobScheduler Masters.

...

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

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

...