Scope
- The JobScheduler REST Web Services replace the retired XML Interface.
- The REST Web Services are used by the JOC Cockpit and by external applications for interaction with a JobScheduler Master:
- The REST Web Services offer access to objects such as jobs, job chains and orders and their respective operations, e.g. to add an order to a job chain.
- Access to REST Web Services is restricted by permissions, see Authentication and Authorization - Permissions for the JobScheduler REST Web Services
Architecture
Usage
- The REST Web Services are called by using an HTTP client.
- The following REST web service requests are supported:
- URL
joc/api/security/login
- The first operation of a client should be call to this URL in order to authenticate and to retrieve an access token.
- A valid account and password have to be provided by the client for HTTP authentication The account and permissions for the command(s) to be executed are configured with the
shiro.ini
configuration file. See the Authentication and Authorization - Configuration article and the exampleapi_user
configuration for further information. - Use the
joc/api/security/joc_cockpit_permissions
URL to retrieve the permissions for the current user.
- URL
joc/api/jobscheduler/command
- Subsequent XML Commands can be sent by use of this URL.
- The XML command is added to the body of the web service request.
- The JobScheduler REST Web Services will return the respective XML Response.
- URL
joc/api/security/logout
- The last operation of a client should be a call to this URL in order to logout from the web service.
- URL
- Requirements
- All REST web service requests should use an HTTP POST operation.
- Should an idle timeout of 15 minutes between two web service requests be exceeded then the current session is invalidated and a login has to be performed.
Change Management References
References
- Authentication and Authorization
- JobScheduler Reference Documentation:
- JobScheduler REST Web Services