Transcript Request Management in SharePoint 2013

#SPC271 IT-Pro, Level 300
Demo Heavy Session (Hopefully!)
What is Request
Management?
Allows SharePoint to
understand more about,
and control the
handling of, incoming
HTTP requests
Having knowledge of
the nature of incoming
requests allows
SharePoint to customize
the response to each
request
Decide if a farm should accept
a request
And if so, which web server
should handle the request
Deny potentially harmful requests
Route good requests
Optimize Performance
Usage Scenarios
Request Management can route
to web servers that have better
performance, keeping low
performance web servers
available
Prioritize requests by throttling
requests from bots to instead serve
requests from end users
Request Management can send
multiple or single requests to
web servers that are designated
to handle them
Request Management can send
requests to logical groups of
servers based upon request
characteristics
Request Management can
perform application routing so
that a load balancer can
concentrate on balancing load
at the network level
Request Management can route
requests to independent content
farms
Request Management can send
all requests of a specific type
(e.g. Search, User Profiles, Office
Web Apps) to specific servers
Request Management can help
locate and isolate the problem,
whilst troubleshooting
Architectural Overview
Available in all SKUs
Zero footprint before
configuration
Critical to IA and
deployment planning
SharePoint Web Server
SharePoint Foundation Web Application Service
Incoming Requests
Filter out requests which should be throttled or prioritized
Select which web servers the request may be sent to
Select a single web server to route to, based upon weighting schemes
Configuration
Request Management Service
Request Manager is
implemented in
SPRequestModule
SharePoint
Foundation Web
Application Service
(a.k.a. WFE)
Starting the Request
Management Service
Instance elsewhere
serves no purpose
Impacts traditional
deployments that use
IIS host headers
Where Request
Management is
configured
Processes all requests
Request Management
may route requests to
another Web
Application
Change to traditional
deployments that use
IIS host headers
www.contoso.com
www.fabrikam.com
www.tailspin.com
For supportability
Even if no end user
accesses that entry
point
Request Management Service runs
on the web servers in a farm
Common On-Premises
environments
A dedicated SharePoint farm which
manages requests exclusively, and
routes request to other farms
Large scale hosting environments
SharePoint Farm
Web Servers
Request Management Farm
Web Servers
SharePoint Farm
SharePoint Farm
Characteristic
Integrated Dedicated
Mode
Mode
Independent scaling
No
Yes
Independent resource usage
No
Yes
Large scale hosting scenarios
No
Yes
Common on premises deployment
Yes
No
Edition independence
No
Yes
Content Farm IIS Binding dependence
Yes
No
Components,
Rules and Evaluation
Static Weighting – configurable
A collection of Routing Targets
Health Weighting – the
SharePoint health score
The target of Routing Rules
Definition of criteria to evaluate
before routing requests
Definition of criteria to evaluate
before refusing requests
Associated with a Machine Pool
NOT associated with a Machine Pool
A collection of Routing Rules
Criteria to evaluate
Allows for evaluation precedence
Based upon HTTP properties
Three Execution Groups (0,1,2)
Url
UrlReferrer
UserAgent
Host
IP
HttpMethod
SoapAction
CustomHeader
StartsWith
EndsWith
Equals
RegEx (use with caution!)
If matched, the request is refused
If NOT matched, Routing Rules in Execution Group 0 are evaluated
If matched, the request is routed to the correct Routing Target
If NOT matched, Routing Rules in Execution Group 1 are evaluated
If matched, the request is routed to the correct Routing Target
If NOT matched, Routing Rules in Execution Group 2 are evaluated
If matched, the request is routed to the correct Routing Target
If NOT matched, the request is routed to ANY available Routing Target
Create the most important rules
in Execution Group 0
If you wish to route everything to a
subset of machines, create a rule
with no criteria and associate with
the subset of machines
Configuration and
Management
Core configuration parent, scoped to the
web application.
Piped into other cmdlets
Configure Machine Pools and their Routing Targets
Configure Routing Targets
Also necessary when configuring Dedicated Mode
Define criteria for Throttling or Routing Rules
Configure Throttling Rules
Configure Routing Rules and their Execution Group
Category: Request
Management
Regular HTTP logs
SPPING Mechanism
SharePoint Foundation:
Request Management
Example Scenario
Request
Management in
Integrated Mode
SP1, SP2, SP3
load balanced using
BIG-IP Local Traffic
Manager
www.contoso.com
www.fabrikam.com
www.adventureworks.com
Wrap Up and
Recommendations
Reliability,
Performance,
Capacity and
Scalability
Application aware
throttling and routing
Just because you can,
doesn’t mean you
should!
A single bad rule
could hose the entire
farm
Significant
performance penalty
Web Application with
NO host headers,
Host Named Site
Collections
You need to be able
to easily manage the
RM configuration
Interaction and
operational service
decisions
Three part series:
http://bit.ly/PArRBC
http://bit.ly/TeMNz0
http://bit.ly/VMQkbV
http://bit.ly/PPa9cB
http://bitly.com/RQEhIx
MySPC
http://myspc.sharepointconference.com