...
- 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 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 operational information in a database - this information can be called up from the JOC Cockpit via the Web Services.
...
The Web Services use XML commands and responses to communicate with the JobScheduler Master(s). [Protokol??] In addition events are communicated [Protokol??] between the Web Services and the JobSchedulersJobScheduler 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 XML [Genauer??] Hibernate.
Authentication and authorization is carried out by an Apache Shiro framework integrated into the Cockpit:
- authentication is carried out against an LDAP directory (not shown in the technical diagram above but in the) and
- authorization is carried out against a role-based group permissions file.
...