Article last updated on the 16th of November, 2023.
Contents
1. Introduction
2. Requirements
3.1. Web Job Priorities
3.1.1. Integration
3.1.2. Site Provisioning
3.1.3. Critical
3.1.4. High
3.1.5. Medium
3.1.6. Low
3.2. Web Jobs in queue
1. Introduction
The Job Queue Manager in WorkPoint 365 is a critical feature designed to efficiently manage and control the execution of jobs within a SharePoint tenant. It serves to optimize system performance and prevent SharePoint throttling by limiting the number of concurrent jobs that can run at different times of the day and week. Administrators have the flexibility to fine-tune job execution based on specific time periods, such as daytime, nighttime, and weekends.
The Job Queue Manager allows for the management of various job types, including integration and site provisioning, as well as categorized jobs in groups like "Critical," "High," "Medium," and "Low."
This robust tool helps ensure that critical tasks are prioritized and run smoothly while maintaining SharePoint's overall system performance and stability.
An example of use could be on a large solution on which many entities with sites are created every day. Normally, a solution like this would utilize the Buffer Sites feature, but in order to limit the number of site creations, and by extension throttling, on the solution, an administrator may limit Site Provisioning jobs so that they can only run during nighttime and/or weekends. This may result in a better experience for the end user.
2. Requirements
There are no requirements associated with the use of the Job Queue Manager.
3. Configuration
Note that the option to set a max number for concurrent jobs of the Integration- and the Site Provisioning job types are only available in WorkPoint 365 version 4.
The Job Queue Manager allows administrators to define how many concurrent jobs of specific types can run. For some types of jobs, it is possible to finely tune how many concurrent jobs can run during specific time intervals (daytime, nighttime, and weekends).
The following page shows an example of the Job Queue Manager settings page:
The Job Queue Manager settings page is split into two sections; the Web Job Priorities section and the Web Jobs in queue section.
3.1. Web Job Priorities
In the Web Job Priorities section, you can define how many concurrent jobs of specific types can run.
Note that you can click "Click here to view the jobs in each priority" text to expand the page and view which jobs are in which categories.
3.1.1. Integration
This queue is used for integration through the WorkPoint API. To reduce the effects of throttling during integration / migration, you can define the number of concurrent running jobs that can be run during daytime hours and evening hours. The time settings are currently based on the time zone of the WorkPoint root site collection.
For this type, you can specify how many concurrent jobs can run during daytime (06:00 - 18:00), nighttime (18:00 - 06:00), and weekends (Saturday at 00:00 until Monday at 00:00).
The number you put into each field defines how many integration jobs can run concurrently during the specific time intervals.
3.1.2. Site Provisioning
This queue is used for site provisioning through the WorkPoint Integration API or through Dynamic Site Creator when it runs in parallel mode.
For this type, you can specify how many concurrent jobs can run during daytime (06:00 - 18:00), nighttime (18:00 - 06:00), and weekends (Saturday at 00:00 until Monday at 00:00).
The number you put into each field defines how many Site Provisioning jobs can run concurrently during the specific time intervals.
3.1.3. Critical
This priority can by used when you need a critical job to run immediately. No jobs get this priority assigned by default.
For this type, you can specify how many concurrent jobs can run during daytime (06:00 - 18:00), nighttime (18:00 - 06:00), and weekends (Saturday at 00:00 until Monday at 00:00).
The number you put into the number field defines how many Critical categorized jobs can run concurrently during the specific time intervals.
3.1.4. High
This Priority is used for the most business critical jobs and is the highest priority that is assigned to jobs by default. The type of jobs in this category involves tasks like Security Replication, Site Creation and Action execution.
For this type, you can specify how many concurrent jobs can run during daytime (06:00 - 18:00), nighttime (18:00 - 06:00), and weekends (Saturday at 00:00 until Monday at 00:00).
The number you put into each field defines how many High categorized jobs can run concurrently during the specific time intervals.
3.1.5. Medium
The jobs in this category can be either short or long running. The end users typical do not have to wait for these jobs to finish. Examples of jobs in this category is Provisioning of Site Collections, Updating of Inheritance/Aggregation for single entity and Master site synchronization.
For this type, you can specify how many concurrent jobs can run during daytime (06:00 - 18:00), nighttime (18:00 - 06:00), and weekends (Saturday at 00:00 until Monday at 00:00).
The number you put into each field defines how many Medium categorized jobs can run concurrently during the specific time intervals.
3.1.6. Low
This Priority is primarily used for long running jobs. This can be either maintenance or jobs requested by an administrator. Example of jobs in this category is Dynamic Site Creation, Site Maintenance and Solution update.
For this type, you can specify how many concurrent jobs can run during daytime (06:00 - 18:00), nighttime (18:00 - 06:00), and weekends (Saturday at 00:00 until Monday at 00:00).
The number you put into each field defines how many Low categorized jobs can run concurrently during the specific time intervals.
Note that you can click "Click here to view the jobs in each priority" text to expand the page and view which jobs are in which categories.
3.2. Web Jobs in queue
The Web Jobs in queue section contains a list of all current web jobs being processed or jobs which have recently completed or failed.
The following image shows an example of the list containing a couple of jobs:
Note that jobs which are in the "Pending" status can have their priorities changed. This effectively moves them from their predefined prioritization category into the selected on. A pending job in the "Low" category and e.g., be changed to the "Critical" category, and therefore have it's priority changed.
An example is shown in the following image:
In the image above, we have selected a few jobs and opened the "For selected jobs" menu. Here we can select a new category for the selected jobs in the queue.
To move the selected jobs to the selected category, we select it and click the "Change priority" button.
To cancel one or more selected jobs, click the "Cancel" button(s).
Comments
0 comments
Please sign in to leave a comment.