Product Knowledge Base

Space shortcuts

Page tree

Versions Compared

Old Version 13

changes.mady.by.user Alan Amos

Saved on

compared with

New Version 14

changes.mady.by.user Alan Amos

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Intermediate save

Table of Contents

Overview

Excerpt

The introduction of the JobScheduler Operating Center (JOC) Cockpit with the release of Version 1.11 brings a significant change in the JobScheduler architecture

.

:

  • The JOC Cockpit has a client - server 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 provide the necessary information for the Cockpit GUI as well as handling the communication with
one or more
  • JobScheduler Masters.

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

 

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

...

  • 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 GUIs: The JobScheduler Web Services can be accessed by more than one 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 in the same network.
  • Job Status and History: JobScheduler Masters record status and other operational information in a database - this information can be called up from the JOC Cockpit via the Web Services.

...

  • The JOC Cockpit can display workplan and job history information and therefore functionally replaces JID - the JobScheduler Information Dashboard, which will no longer 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.

...