How To Use Host-Named Site Collections
Download as PPTX, PDF0 likes148 views
The document discusses host-named site collections in SharePoint, highlighting their scalability and multi-tenancy benefits since their introduction in SharePoint 2003, while addressing limitations resolved in SharePoint 2013. It outlines the process for creating such collections through PowerShell, emphasizing requirements like creating a web application and configuring IIS bindings. Key advantages include high scalability with a limit of 250,000 site collections per farm, while drawbacks include shared application pool settings and the need for PowerShell for configuration.
How To Use Host-Named Site Collections
- 1. Host-Named Site Collections ANDRÉ VALA SharePoint Solutions Architect
- 2. When? How?What? Host-Named Site Collections
- 3. When? How?What? Web SiteSite CollectionWeb Application www.portal.com /sites/companyA /teamA /teamB /sites/companyB /teamC Path-based site collections managed path
- 4. When? How?What? Web SiteSite CollectionWeb Application www.portal.com www.companyA.com /teamA /teamB www.companyB.com /teamC Host-named site collections host name
- 5. Exist since SharePoint 2003 (by the name of scalable hosting mode) with several limitations In SharePoint 2013 most limitations have been resolved Designed for scalability in multi-tenancy scenarios Used by Microsoft in Office 365 environments When? How?What?
- 6. When? How?What? Especially useful for multi-tenant scenarios High scalability requirements SharePoint has a supported limit of 20 web applicationsper farm SharePoint can handle up to 250.000 site collections per farm, using shared content databases Even if you use a separatecontentdatabase per site collection, you can still scale up to 500 site collections per farm
- 7. When? How?What? Recommended over path-based site collections on most scenarios, except when: You want to use multiple application pools You want to have multiple service application proxy groups You want to use different authentication methods for each site collection You need to use the Self Service Site Creation feature (not supported for host-named site collections) SSL termination is required but your SSL termination device cannot be configured to produce a specific custom HTTP header
- 8. When? How?What? Host-named site collections cannot be created in Central Administration. You must use PowerShell cmdlets. Process overview: 1. Create a web application 2. Configure IIS binding 3. Create root site collection (required for crawling purposes) 4. Create host-named site collection(s) 5. Set alternate URLs for host-named site collection (if applicable)
- 9. When? How?What? $ownerAlias = ‘domainuser’ $ap = New-SPAuthenticationProvider -UseWindowsIntegratedAuthentication New-SPWebApplication -Name ‘Portal WebApp’ -hostHeader ‘webapp.portal.com’ -port 80 -ApplicationPool ‘SharePoint – Portal’ -ApplicationPoolAccount $ownerAlias -DatabaseName ‘WSS_Content_Portal’ -AllowAnonymousAccess -AuthenticationProvider $ap Create a web application
- 10. When? How?What? New-WebBinding -Name ‘Portal WebApp’ -HostHeader ‘*’ -IPAddress ‘*’ -Port 80 -Protocol http Configure IIS binding
- 11. When? How?What? New-SPSite ‘http://webapp.portal.com’ -HostHeaderWebApplication ‘http://webapp.portal.com’ -Name ‘Root Site’ -Description ‘Root Site’ -OwnerAlias $ownerAlias -Language 1033 -Template ‘STS#0’ Create root site collection
- 12. When? How?What? New-SPSite ‘http://www.companya.com’ -HostHeaderWebApplication ‘http://webapp.portal.com’ -Name ‘Company A’ -Description ‘Company A’ -OwnerAlias $ownerAlias -Language 1033 -Template ‘STS#0’ Create host-named site collection
- 13. When? How?What? $site = Get-SPSite ‘http://www.companya.com’ Set-SPSiteUrl $site -Url ‘https://secure.companya.com’ -Zone Internet Set alternate URL
- 14. DEMO Creating host-named site collections
- 15. ConsPros Scalability Heavily tested architecture Support for alternate access mappings Can be mixed with path-based site collections (but more complex to configure)
- 16. ConsPros Single application pool All site collections must share same web application settings (e.g. authentication methods and zones) Requires PowerShell scripting and configuration can be complex
- 17. Thank you!