Page History

Table of Contents

Overview

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

Image AddedImage Removed

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.
• 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.
• The Web Services use the LDAP Directory not only for authentication but also for authorization. This means that user access to particular resources can be restricted.
• External Applications 3^rd 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 in the same network.
• JobScheduler Universal Agents or Universal Agent Clusters cannot be directly controlled via the Web Services - this must take place via a JobScheduler Master.
• JobScheduler Masters record status and other 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.
• Security: The architecture restricts direct user access to the JOC Cockpit. Only the Web Service has access to the JobScheduler Masters themselves.
  Image Added

Technical Details

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

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

The Web Services use XML commands and responses Service uses JSON and XML based commands to communicate with the JobScheduler Master(s). [Protokol??] In addition events are communicated [Protokol??] between the Web Services and the JobSchedulersMasters. Events about object status changes are communicated between the JobScheduler Masters and the Web Service.

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

Communication between the REST Web Services Service and the JobScheduler database takes place using ?? [Genauer??] Hibernate.

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

• Authentication authentication is carried out against a local configuration or an LDAP directory (not shown in the diagram)
• authorization Authorization is carried out against a role-based group permissions file

...

• .

...

1. Dashboard
2. Liste der Job-Ketten
3. Darstellung einer Split/Sync Job-Kette mit graphischer Ansicht
4. Daily Plan: klären für welches Datum
5. Historie: Log soll sichtbar sein
6. PowerPoint
   1. Folie Nr. 6 überarbeiten (aus Anhang)
   2. Info
      1. Nur zur Info: Knowledge Base Adresse: https://kb.sos-berlin.com/x/EgAv
      2. 2-3 Seiten in SOS Web Site
      3. Top Features

                                                              i.      Dashboard

• Screenshot 1.a)

                                                            ii.      Authentication and Authorization

                                                            iii.      Multi-client Capability

                                                           iv.      Navigation, Usability

• Screenshots aus 1.b)  1.e)

1. Architektur, Technologie

...