Job Server

The Job Server is a TM server which facilitates a wide variety of tasks. It supports on demand and recurring tasks of different types, including integration, information retrieval and manipulation, and system maintenance tasks.

The Job Server schedules instances of jobs and handles the processing of job instances. For each job instance, the job type indicates what processing the Job Server will perform. Examples of the type of jobs which the Job Server can handle include:

Integration jobs to integrate with Blue Yonder partners like TransVoyant and INTTRA
Data maintenance jobs like rerating and scheduling loads, trips, and bookings
API based jobs to automatically handle events and common tasks

Many Job Server job types are based on Entity Selection Criteria. Entity Selection Criteria view use SQL or findEntities API calls to identify specific data or a set of data which the job type will process. Defining Entity Selection Criteria (ESC) is done using the Transportation Smartbench. For jobs which require ESC, more information about what data or entities is expected and how that job type utilizes the ESC can be found in the documentation for that job type.

The Alert Framework and the Event Notification Framework have been integrated with the Job Server, allowing both alerts and events to initiate instances of defined jobs for immediate processing. This allows actions to be configured in the system in response to alerts and events.

The Job Server queries the queue of scheduled job instances at regular intervals and processes job instances based on their scheduled date and time. Recurring schedules allow for the definition of the following schedule types:

Fixed Interval: Fixed interval schedules define a recurrence based on a frequency in minutes. For example, a fixed interval of 60 would result in the Job Server processing an instance of the job definition once every hour.
Daily: Daily schedules define a recurrence for activities that should occur once per day. A daily schedule can define the time of day that the job instance should start. Daily schedules support the definition of which days of the week should be included. For example, a schedule could define that the job instance should only be scheduled Monday through Thursday. Daily schedules can also define an interval, allowing for job instances that occur every other day, every third day, or every Nth day.
Monthly: Monthly schedules define a recurrence for activities that should occur once per month. A monthly schedule can define the day of the month that the job instance should be scheduled on, and the time of day that the job instance should start on that day. Monthly schedules can also define an interval, allowing for job instances that occur every other month, every third month, or every Nth month.

After processing an instance of a recurring job, the Job Server will calculate the next occurrence of that job instance and add a queue entry for the job instance with the calculated scheduled date and time. The job queue can be viewed and maintained in the Transportation Smartbench. Additionally, historic data from the job queue can be purged from the Purge Supplementary Data page. See Supplementary Purge (Employee).

The Job Server can alert users after jobs are complete. General information about the processing of job instances is maintained in the job queue and detailed information about the processing of job instances is maintained in the Job History table. Information about the Jobs Queue view and History of a Job Instance is accessible using the Transportation Smartbench.