Job Manager API
Number of APIs: 10
Offers execution mechanisms for running models stored in Model Management module. A schedule is created based on a model identifier and a cron expression so the model will run one or multiple times. Each time a model runs a new job is generated. When the schedule is created it will start according to the cron expression. If a user wants to stop the executions it can update the status of the schedule and the executions will stop. Also the user has the possibility to update again the status and trigger again the schedule. If a user does not want to run a model multiple times or based on a schedule expression it can start immediately a new job.
-
schedules - Retrieves a list with all schedules stored within the same tenant GET {{baseUrl}}/schedules?pageNumber=<integer>&pageSize=<integer>&filter=<string>
-
schedules - Schedules a job for execution specified by its model id and a cron string POST {{baseUrl}}/schedules
-
jobs-{id} - Retrieves the details regarding a job execution GET {{baseUrl}}/jobs/:id
-
jobs-{id} - Stops a job execution POST {{baseUrl}}/jobs/:id/stop
-
jobs - Retrieves all the jobs executions GET {{baseUrl}}/jobs?pageNumber=<integer>&pageSize=<integer>&filter=<string>
-
jobs - Creates a new job execution POST {{baseUrl}}/jobs
-
schedules-{id} - Retrieves information about a schedule GET {{baseUrl}}/schedules/:id
-
schedules-{id} - Removes a schedule DELETE {{baseUrl}}/schedules/:id
-
schedules-{id} - Updates the status of the schedule to started POST {{baseUrl}}/schedules/:id/start
-
schedules-{id} - Updates the status of the schedule to stopped POST {{baseUrl}}/schedules/:id/stop