Mirjam van Olst. Best Practices & Considerations for Designing Your SharePoint Logical Architecture

Transcription

1 Mirjam van Olst Best Practices & Considerations for Designing Your SharePoint Logical Architecture

2 About me

3 Agenda Introduction Logical Architecture Design Web Applications Service Applications Site Collections & Content Databases Sites Wrap Up

4 Introduction

5 Logical Architecture Configuration of your SharePoint environment Continuous monitoring needed

6 Logical Architecture Design Get the most from out-of-thebox SharePoint Be able to scale your environment Avoid common health and performance challenges

7 Logical Architecture Design Functional Drivers Shared security Content rollup Shared settings Technical Drivers Boundaries

8 Logical Architecture Design Safest bet: use your crystal ball Second best: Good insight into the environment and the organization Thorough understanding of SharePoint internals

9 SharePoint Hierarchy Farm Servers Web Applications Content Databases Site Collections Sites Libraries and Lists Items

10 Logical Architecture Design

11 Logical Architecture Design Web Applications Service Applications Content Databases & Site Collections Sites

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 Collections Best practice for new deployments Created using PowerShell (no User Interface) Hosted in a single web application without a host header

14 Host header-less web applications SharePoint Apps Multi-Tenancy Request Management expect more in the future New capabilities in SharePoint have been designed for, and expect a web application with no host header

15 When to use Path Based Sites Self Service Site Creation Unique wild card inclusion Managed Paths Security isolation with separate app pools

16 Host Named vs. Host Header Host Named Site Collections: 1 web application Host Header Web applications: Portal Team Sites / Project Sites My Sites

17 Custom Solutions Custom solutions can be deployed to: All Web Applications A specific Web Application The Farm

18 SharePoint Apps App Catalog per Web Application by default Web Applications in a farm can share a Catalog App settings for users per Web Application

19 SharePoint Apps

20 Software Boundaries Web Applications Limit Maximum Value Limit Type Web Applications 20 per farm Supported Zone 5 per web application Boundary Managed Path 20 per web application Supported Application Pools 10 per web server Supported

21 Reasons for multiple web apps Usage Service Applications SharePoint Apps and Custom Solutions

22 Logical Architecture Design Web Applications Service Applications Content Databases & Site Collections Sites

23 Service Application model Service Applications can easily be scaled out Web applications can pick and choose service applications Some 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 When you create a web app you can: select the default proxy group create a custom proxy group and select proxies A custom proxy group can only be used by one web application when using the user interface

26 Proxy Groups Excel User Profile App Management Machine Translation Excel Business Data Connectivity Managed Metadata Search Secure Store Visio Graphics

27 Service Application Considerations Isolation Scalability What 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 it s own SQL Server instance or SQL Server server

29 Logical Architecture Design Web Applications Service Applications Content Databases & Site Collections Sites

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 Influencers People Content Site 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 collections Complex security Separate backup and restore schedules and demands Site Collection quotas Decentralized administration

34 Sites and Site Collections Architectural reasons for multiple site collections More than 2000 sub sites per site view More than 250,000 sub sites More than GB of content Complex authorization structures per site

35 Software Boundaries Site Collections Limit Maximum Value Limit Type Site collections per farm 250,000 for non-personal site collections Supported Site collections per farm 750,000 Supported Site collections per content database Site collections per content database Users in a site collection 2,500 for non-personal site collections Supported 5,000 Recommended 2 million (after more than 1,000 the user interface will no longer scale and PowerShell should be used) Supported

36 Logical Architecture Design Web Applications Service Applications Content Databases & Site Collections Sites

37 Software Boundaries Security Limit Maximum Value Limit Type Security Scopes per list 5,000 Recommended Number of SharePoint groups a user can belong to 5,000 Supported Users in a SharePoint group 5,000 Supported Security principal per Access Control List (ACL) 5,000 Supported

38 Security Don t use item level security if you can avoid it Sharing an item or document means using item level security!

39 Security Don t use item level security if you can avoid it Sharing an item or document means using item level security!

40 Wrap up

41 Wrap Up Consider Functional and Technical drivers Thorough investigation and planning needed Design for growth Custom solutions add complexity and risk

42 Questions?

43 THANK YOU