...
The introduction of the JobScheduler Operating Center Cockpit with the release of Version 1.11 brings a significant change in the JobScheduler architecture. As can bee seen in the diagram below, the JOC Cockpit can be installed separately from a JobScheduler Master and all communication between the Cockpit and Master JobScheduler(s) takes place as an authenticated web service.
Additional features of this new architecture are:
- 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.
- 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 such as ERP systems can access the Web Services and, for example, start jobs when they provide the correct authentication and authorization.
- Any number of JobScheduler Masters can be controlled via the Web Services as long as they are in the same network.
- JobScheduler Universal Agents cannot be directly controlled via the Web Services - this must take place via a JobScheduler Master.
- JobScheduler Masters record status and other information in a database - this information can be called up from the JOC Cockpit via the Web Services.
...