spca2013 - best practices & considerations for designing your sharepoint logical architecture

of 45/45

Post on 09-May-2015

546 views

Category:

Technology

0 download

Embed Size (px)

DESCRIPTION

Best Practices & Considerations for Designing Your SharePoint Logical Architecture

TRANSCRIPT

  • 1.Mirjam van OlstBest Practices & Considerations for Designing Your SharePoint Logical Architecture

2. About me http://sharepointchick.com @mirjamvanolst [email protected] 3. Agenda IntroductionLogical Architecture Design Web Applications Service Applications Site Collections & Content Databases SitesWrap Up 4. Introduction 5. Logical ArchitectureConfiguration of your SharePoint environmentContinuous monitoring needed 6. Logical Architecture DesignGet the most from out-of-thebox SharePointBe able to scale your environmentAvoid common health and performance challenges 7. Logical Architecture DesignFunctional Drivers Shared security Content rollup Shared settingsTechnical Drivers Boundaries 8. Logical Architecture Design Safest bet: use your crystal ball Second best: Good insight into the environment and the organizationThorough understanding of SharePoint internals 9. SharePoint Hierarchy Farm Servers Web Applications Content DatabasesSite Collections Sites Libraries and Lists Items 10. Logical Architecture Design 11. Logical Architecture Design1 Web Applications234Service ApplicationsContent Databases & Site CollectionsSites 12. Web Application Considerations Potential Influences: Intended Use Scalability SharePoint App policies Host Header Web Applications vs. Host Named Site Collections 13. Host Named Site CollectionsBest practice for new deploymentsCreated using PowerShell (no User Interface)Hosted in a single web application without a host header 14. Host header-less web applicationsSharePoint AppsMulti-TenancyRequest Managementexpect more in the futureNew capabilities in SharePoint have been designed for, and expect a web application with no host header 15. When to use Path Based SitesSelf Service Site CreationUnique wild card inclusion Managed PathsSecurity isolation with separate app pools 16. Host Named vs. Host HeaderHost Named Site Collections:Host Header Web applications: 1 web applicationPortal Team Sites / Project Sites My Sites 17. Custom Solutions Custom solutions can be deployed to: All Web ApplicationsA specific Web ApplicationThe Farm 18. SharePoint AppsApp Catalog per Web ApplicationApp settings for users per Web Application 19. SharePoint Apps 20. Software Boundaries Web ApplicationsLimit Web Applications Zone Managed Path Application PoolsMaximum Value 20 per farm 5 per web application 20 per web application 10 per web serverLimit Type Supported Boundary Supported Supported 21. Reasons for multiple web appsUsageService ApplicationsSharePoint Apps and Custom Solutions 22. Logical Architecture Design1 Web Applications234Service ApplicationsContent Databases & Site CollectionsSites 23. Service Application modelService Applications can easily be scaled outWeb applications can pick and choose service applicationsSome Service Applications can be shared across farms 24. Service Applications 25. Proxy Groups A proxy group is a group of Service Application Proxies (connections) that are selected for one or more web applications By default, all Service Application Proxies are included in the default proxy group A web application can: Use the default proxy group Use a custom proxy group and select service application proxies A custom proxy group is specific to a web application when using the user interface 26. Proxy GroupsUser ProfileBusiness Data Connectivityhttp://myApp ManagementMachine TranslationExcelManaged MetadataExcelSearchSecure StoreVisio Graphicshttp://teams http://projectshttp://intranethttp://communities 27. Service Application ConsiderationsIsolationScalabilityWhat functionality and where? 28. Scaling of Services First role to move to a dedicated server is crawl Calculations in Excel Services could use a lot of CPU User Profile synchronization single point of failure Only one User Profile Service Application and one Search Service Application per server Access Services needs its own SQL Server instance or SQL Server server 29. Logical Architecture Design1 Web Applications234Service ApplicationsContent Databases & Site CollectionsSites 30. Content Databases A content database should be within 100 to 200 GB A site collection is always stored in a single content database Limiting the size of a content database could be a reason to use multiple site collections 31. Sites and Site Collections InfluencersPeopleContentSite Types 32. Sites and Site Collections Within a site collection the following things can shared: Navigation Content types Site Columns SharePoint Apps Master pages SharePoint Security groups Lookup fields for lists Search scopes Feature set 33. Sites and Site Collections Functional reasons for multiple site collectionsComplex securitySeparate backup and restore schedules and demandsSite Collection quotasDecentralized administration 34. Sites and Site Collections Architectural reasons for multiple site collectionsMore than 2000 sub sites per site viewMore than 250,000 sub sitesMore than 100-200GB of contentComplex authorization structures per site 35. Software Boundaries Site Collections LimitMaximum ValueLimit TypeSite collections per farm250,000 for non-personal site collectionsSupportedSite collections per farm750,000SupportedSite collections per content database2,500 for non-personal site collectionsSupportedSite collections per content database5,000RecommendedUsers in a site collection2 million (after more than 1,000 the user interface will no longer scale and PowerShell should be used)Supported 36. Logical Architecture Design1 Web Applications234Service ApplicationsContent Databases & Site CollectionsSites 37. Software Boundaries SecurityLimitMaximum ValueLimit TypeSecurity Scopes per list5,000RecommendedNumber of SharePoint groups a user can belong to5,000SupportedUsers in a SharePoint group5,000SupportedSecurity principal per Access Control List (ACL)5,000Supported 38. Security Dont use item level security if you can avoid it Sharing an item or document means using item level security! 39. Security Dont use item level security if you can avoid it Sharing an item or document means using item level security! 40. Wrap up 41. Wrap UpConsider Functional and Technical driversThorough investigation and planning neededDesign for growthCustom solutions add complexity and risk 42. THANK YOU