Product Knowledge Base

Space shortcuts

Page tree

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 25 Next »

Overview

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 REST Web Service provide the necessary information for the JOC Cockpit as well as handling the communication with JobScheduler Masters.

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

 

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

Additional features of this new architecture are:

  • 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 GUI 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 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.

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 applications.

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.

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

Communication between the REST Web Services and the JobScheduler database takes place using Hibernate.

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.

 

  • No labels