There are
hardware/ software load balancer used to route the request at a network level
to web servers.
But such
configuration not fully solved the problem.
Now SP 2013
comes with this to route requests from application level. By this SharePoint
can refuse or redirect HTTP requests individually within the farm to dedicated
or different servers in the farm for specific workloads.
It can now
recognize the origin of incoming requests like browsers, applications, IP to
reduce the priority.
Request Management Rules:
These rules
are applied per web applications which are disabled by default.
These rules
are either throttling or routing rules.
Throttling
rules evaluated before routing rules $ if request matches the criteria, the
request is refused.
Throttling
and routing rules use the following HTTP request header properties:
·
CustomHeader
·
Host
·
HttpMethod
·
IP
·
SoapAction
·
Url
·
UrlReferrer
·
UserAgent,
such as a Microsoft Office OneNote client application
·
EndsWith
·
Equals
·
Regex
·
StartsWith
Creating & Managing Request Management:
No
administrative user interface for Request Management. Only using powershell.
Create
routing rules using powershell -
·
$webapp =
Get-SPWebApplication “Web application URL”;
·
$rmsettings
= Get-SPRequestManagementSettings $webapp;
·
$MachTargets
= @("SP1");
·
$machpool_1
= Add-SPRoutingMachinePool -RequestManagementSettings $rmsettings ' -Name
"Machine Pool 1" -MachineTargets $MachTargets;
·
$RMrulecriteria
= New-SPRequestManagementRuleCriteria -Property Url '-MatchType Regex -Value
".*\.docx"
·
$DocRule =
Add-SPRoutingRule -RequestManagementSettings $rmsettings -Name
"DocRule" '-ExecutionGroup 0 -MachinePool $Machpool_1 -Criteria
$RMruleCriteria
View routing
rules -
·
Get-SPWebApplication
“Web application URL” | Get-SPRequestManagementSettings
No comments:
Post a Comment