Chapter 5: Jobs The Integration Toolkit supports the following job functions. l Job creation methods: pickup, pickupdropoff, dropoff, and job request. l The modification of jobs on the segment level (goal and priority changes). l The cancellation of entire jobs. l The cancellation (deletion) of single segments of multi-segment jobs. l If a job request is created without a namekey or jobId, the Integration Toolkit will auto- matically generate unique values for these data items. NOTE: Creating a dropoff job overrides the Fleet Manager's AMR selection logic. For this reason, use this job type selectively. NOTE: A job request has the same functionality as the queueMulti ARCL command.
This job type will queue the AMR for multiple pickups and dropoffs at multiple goals. Job Creation Steps Job creation is a two-step process: 1. A job request is made and a confirmation reply is sent after the Integration Toolkit accepts the request. NOTE: A confirmation reply is sent with REST only. 2. After the Integration Toolkit accepts the job request, a call is made to the Fleet Manager to initiate the job. When the job is initiated, job and job segment entries become avail- able in the Integration Toolkit, allowing the job to be tracked in real time. 5.1 Common Job Creation Use Cases Common use cases when working with job creation are provided below.
Create a Single Job This use case involves the creation of a job by specifying only the goal(s). If the system does not need to track the job or verify status, using any one of the communication channels can create a job with a single call (or SQL row insertion). Create a Job and Verify it was Accepted by the Fleet Manager After a job request is created, the status of it can be obtained by checking the SQL entry or by running a GET call on the same path's /ByKey URI using the namekey originally returned with the call. 20964-000 Rev. C Fleet Operation Workspace Core Integration Toolkit 33 User's Manual