SharePoint Saturday Belgium SharePoint Farm Architecture bringing it all together

389 views
227 views

Published on

Published in: Technology, Design
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
389
On SlideShare
0
From Embeds
0
Number of Embeds
3
Actions
Shares
0
Downloads
3
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

SharePoint Saturday Belgium SharePoint Farm Architecture bringing it all together

  1. 1. SharePoint Farm Architecture Bringing it all together #SPSBE09 Thomas Vochten April 26th, 2014
  2. 2. Thanks to our sponsors! Gold Silver
  3. 3. About Me @thomasvochten http://thomasvochten.com Thomas Vochten SharePoint Server MVP Platform Architect Involuntary DBA Trainer
  4. 4. In the Wild
  5. 5. But,… we’re doing DevOps!
  6. 6. Are you serious?
  7. 7. The G-Word
  8. 8. What we need
  9. 9. Product Line Architecture
  10. 10. Basic Building Blocks SharePoint Farm Web Application Site Collections Service Applications Servers IIS Web Sites Bindings Application Pools Identity
  11. 11. SharePoint doesn’t care about IIS Certificates Host Headers Advanced Bindings IP Addresses
  12. 12. Host Headers to the rescue? Multiple web applications using the same bindings require the use of host headers
  13. 13. The problem with Host Headers
  14. 14. Web Applications vs Web Sites Web Application • SharePoint • Logical Concept Web Sites • IIS • Physical Concept
  15. 15. Support Limits
  16. 16. Web Sites
  17. 17. Application Pools Application Pool • Worker Process (w3wp.exe) • CPU/Memory • Identity Web Sites
  18. 18. Support Limits
  19. 19. Application Pools Application Discovery and Load Balancer Service Application
  20. 20. Application Pools How many of these do you create?
  21. 21. Accounts    • • • •
  22. 22. Good Practice: Cleaning Up
  23. 23. Design Principles
  24. 24. Application Pool Content Application Pool Central Administration Content Apps Application Pool Application Pool App Disc & LB Svc Services Application Pool Service ApplicationsSecurity Token Svc
  25. 25. Content Web Application
  26. 26. Apps Web Application
  27. 27. http://bleh Consolidating Application Pools
  28. 28. Consolidating Web Applications
  29. 29. “Host-named site collections are the preferred method to deploy sites in SharePoint 2013” From: TechNet
  30. 30. Confusion Incompatible
  31. 31. Path Based Site Collections https://intranet.contoso.com https://intranet.contoso.com https://intranet.contoso.com/sites/teamA https://intranet.contoso.com/dep/departmentA
  32. 32. Path Based Site Collections
  33. 33. Host Named Site Collections https://intranet.contoso.com https://mysites.contoso.com https://community.contoso.com https://intranet.contoso.com/sites/benefits https://teams.contoso.com/sites/it
  34. 34. Marchitecture
  35. 35. Why Host Named Site Collections?
  36. 36. Create Host Named Site Collections -HostHeaderWebApplication
  37. 37. Living without host headers
  38. 38. The good, the bad, the ugly Path Based Host Named Site Creation Central Admin or PowerShell PowerShell Out of the box self service site creation Custom self service site creation needed URLs & Structure Inherits Web Application URL Unique URL per site collection Multiple URLs with AAM Multiple URLs without AAM Managed Paths at web application level Managed Paths at farm level Database Mgmt Managed out of the box at the web application level Custom site creation provider recommended
  39. 39. Multiple URLs Path Based Site Collections Host Named Site Collections
  40. 40. PowerShell Support for Multiple URLs $site = Get-SPSite https://intranet.contoso.com Set-SPSiteURL -Identity $site -Url https://extranet.contoso.com -Zone Default
  41. 41. Zones Multiple URLs work even without multiple web application zones!
  42. 42. Managed Paths https://intranet.contoso.com/projects/projectA https://teams.contoso.com/projects/projectB
  43. 43. Certificates If you need multiple TLD support, you need a SAN certificate!
  44. 44. Mixing Path & Host
  45. 45. Migrating to Host Named Site Collections $webApp = Get-SPWebapplication 'https://portal.contoso.com' foreach($spSite in $webApp.Sites) { if ($spSite.HostHeaderIsSiteName) { Write-Host $spSite.Url 'is host-named' } else { Write-Host $spSite.Url 'is path based' } }
  46. 46. Migrating to Host Named Site Collections Backup-SPSite -Identity 'https://portalOld.contoso.com' -Path 'c:BackupportalContoso.bak' Restore-SPSite -Identity 'https://portal.contoso.com' -Path 'c:BackupportalContoso.bak' -DatabaseName 'portal_content' -HostHeaderWebApplication 'https://content.contoso.com'
  47. 47. Good Practices
  48. 48. Considerations
  49. 49. SSL Offloading Requirement: Support for custom HTTP Header “Front-End-Https:On”
  50. 50. SSL Offloading
  51. 51. Using multiple webapps with HNSC
  52. 52. Summary
  53. 53. Thank you! @thomasvochten #SPSBE09

×