Queue Engine GUI
While most customers prefer the Job Control Panel’s view of all Queue Engine servers, Argent also provides a Queue Engine GUI for connecting directly to a single Queue Engine to manage the Queue Engine directly.
You can manage many of the same Queue Engine properties either through the Job Scheduler Control Panel or the Queue Engine GUI.
The Queue Engine GUI provides the ability to control any Queue Engine regardless of the availability of the Argent Scheduler Job Control Panel.
Managing Queues
The Queue Engine GUI provides the same ability to create, delete or rename queues and adjust queue properties that the Argent Scheduler Job Control Panel provides.
Queue Properties
Queue properties of such as ‘Start’, ‘Stop’, ‘Open’, and ‘Close’ can be edited using the Queue Engine GUI.
Think of each queue as grain hopper with a top that accepts new jobs and a bottom that releases processed jobs. The Open/Closed status controls the whether the queue can accept new jobs. The Start/Stopped status controls whether the queue can process new jobs.
Queue ‘Start’ Property
If a Queue is ‘Started’, then it is able to execute any jobs that have been submitted to it.
Queue ‘Stop’ Property
If a Queue is ‘Stopped’, then the queue is still able to accept submitted jobs to be executed at a later time, however no jobs will execute during the time that the Queue is in a ‘Stopped’ state.
Queue ‘Open’ Property
If a Queue is ‘Open’, then the Queue is able to accept submitted jobs to be run either at the current or future time.
Queue ‘Closed’ Property
If a Queue is ‘Closed’, then it may continue to run existing jobs that have previously been submitted to it, but it will no longer accept any new jobs that are submitted to it while in the ‘Closed’ state.
CPU Affinity
By restricting a queue’s CPU affinity to low priority tasks, the power of multi-processing systems is appropriately allocated to higher priority queues.
Queue Permissions
Having multiple queues within a Queue Engine allows for dividing resource usage and corporate users the granular control they need.
For example, the accounting department of an investment firm needed to ensure their compliance jobs run at a higher priority than all other job types. By creating a separate queue for these jobs, and managing permissions to the queue, the accounting department was able parallelize jobs while maintaining security and performance.
These permissions restrict the use of the COMPLIANCE queue to members of the COMP_Admins group.
Managing Jobs
The Queue Engine GUI can manage jobs that have already been submitted by the Job Scheduling Service, using the right-click options for ‘Resubmit’, ‘Requeue’, ‘Delete’ etc.
Submitting Jobs
A new adhoc job instance can be submitted directly to a queue using the Queue Engine GUI. These job instances do NOT appear within the Argent Scheduler Job Control Panel GUI.
The same options for controlling how the job will run are available here, with the obvious exception of a schedule.
