This service is named ‘Request Management’ and has no associated service application, management is done solely thru PowerShell. This service will be provisioned on any server running the SharePoint Foundation Web Application Service. Request Management is scoped and configured per Web Application, for each Web Application there is a matching Request Manager which runs under the SPRequestModule .
Reviews the performance of each server to prioritize which server can be used in load balancing, then implements rules of the following types.
A Routing Target is a machine running SharePoint Foundation Web Application Service. By default all servers in the farm running this service are placed in the Routing Targets of the Request Manager. Routing Target is interchangeable with the name Routing Machine.
Each Routing Target has a Static Weighting which is constant and will be evaluated. The Static Weight is assignable, In addition the availability of a Routing Target can be toggled and other advanced properties related to the polling of the machine can be set.
Each Routing Target also has a Health Weighting which is dynamic and will be evaluated. The Health Weighting cannot be assigned and is derived from the Health Score (0 to 10) which is updated by Health Analysis.
Routing Targets must be associated with a Machine Pool.
Machine Pool is a collection of Routing Targets which are contained within its MachineTargets property.
Machine pools are the target of one or more Routing Rules.
A Routing Rule is the definition of the criteria to evaluate before routing requests which match the criteria. Each Routing Rule is associated with a Machine Pool and an Execution Group. Routing Rules can have an expiry time set.
A Throttling Rule is the definition of the criteria to evaluate before refusing requests which match the criteria. Throttling Rules are NOT associated with a Machine Pool or an Execution Group. Throttling Rules can have an expiry time set.
A Execution Group is a collection of Routing Rules which allows the precedence of rule evaluation to be controlled and Routing Rules to be managed in batches. There are three execution groups (0, 1 & 2) which are evaluated in order. If no Execution Group for a Routing Rule is specified it is associated with Execution Group 0.
Managing Request management using PowerShell
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.