4. #SPC271 IT-Pro, Level 300 Demo Heavy Session (Hopefully!)

5. What is Request Management?

6. 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

7. 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

8. Usage Scenarios

9. 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

10. 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

11. 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

12. 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

13. Architectural Overview

14. Available in all SKUs Zero footprint before configuration Critical to IA and deployment planning

15. SharePoint Web Server SharePoint Foundation Web Application Service 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 Request Management Service Incoming Requests Configuration

16. 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

17. 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

18. 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

19. 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

20. SharePoint Farm Web Servers

21. Request Management Farm Web Servers SharePoint Farm

22. CharacteristicIntegrated Mode Dedicated Mode Independent scalingNoYes Independent resource usageNoYes Large scale hosting scenariosNoYes Common on premises deploymentYesNo Edition independenceNoYes Content Farm IIS Binding dependenceYesNo

23. Components, Rules and Evaluation

24. Static Weighting – configurable Health Weighting – the SharePoint health score A collection of Routing Targets The target of Routing Rules

25. Definition of criteria to evaluate before routing requests Associated with a Machine Pool Definition of criteria to evaluate before refusing requests NOT associated with a Machine Pool

26. A collection of Routing Rules Allows for evaluation precedence Three Execution Groups (0,1,2) Criteria to evaluate Based upon HTTP properties

27. Url UrlReferrer UserAgent Host StartsWith EndsWith Equals RegEx (use with caution!) IP HttpMethod SoapAction CustomHeade r

28. 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

30. 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

31. Configuration and Management

33. Core configuration parent, scoped to the web application. Piped into other cmdlets

34. Configure Machine Pools and their Routing Targets

35. Configure Routing Targets Also necessary when configuring Dedicated Mode

36. Define criteria for Throttling or Routing Rules

37. Configure Throttling Rules

38. Configure Routing Rules and their Execution Group

39. Category: Request Management Regular HTTP logs SPPING Mechanism SharePoint Foundation: Request Management

40. Example Scenario

41. Request Management in Integrated Mode SP1, SP2, SP3 load balanced using BIG-IP Local Traffic Manager www.contoso.com www.fabrikam.com www.adventureworks.co m

46. Wrap Up and Recommendations

47. Reliability, Performance, Capacity and Scalability Application aware throttling and routing Just because you can, doesn’t mean you should!

48. A single bad rule could hose the entire farm Significant performance penalty Web Application with NO host headers, Host Named Site Collections

49. You need to be able to easily manage the RM configuration Interaction and operational service decisions

50. Three part series: http://bit.ly/PArRBC http://bit.ly/TeMNz0 http://bit.ly/VMQkbV http://bit.ly/PPa9cB http://bitly.com/RQEhI x

51. MySPC