Sharepoint Architecture Basics

1. Ryan Charnock MCT @ New Horizons MI Sharepoint Architecture Basics

2. OverView • Physical Architecture • Server Types and Farms • Logical Architecture • Pros Cons of different Logical Archs. • Content Database • Demo • Conclusions and Questions

3. Physical Players • Web Front End server(WFE) • Database Server (db) • Application Server (app) • Query Server (qu)

4. Web front End Server What: Send and Receive Http requests for pages Why: Server to field user requests for access Think of: A bank teller

5. Database Server What: Holds configuration and content data in SQL Server databases. Why: Structured storage within a known storage system Think Of: Bank vault. Keeper of the cash.

6. Application Server What: Run Share Services for farm Why: Scaled out delegation of centralized server Think of: Federal Government – provide centralized services to the 50 states

7. Farms • Single Server • Small farm (farmet, Toy-farm) • Large farm / scaled out

8. Single Server WFE Application Srv Database Srv

9. Small Farm WFE App DB

10. Large Farm WFE Fail Over Cluster APP DB • WFE DB • WFE

11. Logical Players • Application Pool • Web Application • Site Collection

12. Application Pool What: Memory container with an AD account to represent Web Applications in it to other resources Why: One app crash only that app Think of: Chained together convicts.

13. Web Application What: IIS Virtual Server. Determines the URL:Port, Authentication method, Content Database Name Why: Creates a website for hosting SharePoint content. Think of: A convention center / Cobo.

14. App. Pool / Web app. relationship Application Pool Web Application: http://mycompanyintran.local Ntml – Window Authentication Database - WSS_Content

15. Site Collection What: A grouping of sites in an hierarcky. Why: To isolate and share common features, and customizations. Think of: Condo association. Each condo is separate, but have common stuff.

16. Web App. / Site Col relations Application Pool Web Application: http://MyCompanyIntranet.local Site Collection Root of web Application http://MycompanyIntranet.local

17. Scenario 1 – Stick to the basics 1:1:1 Application Pool Web Application: http://MyCompanyIntranet.local Site Collection Root of web Application http://MycompanyIntranet.local

18. Scenario 1 Break Down = Sub Site Root Site of Intranet Departmental Sites Dept. teams

19. Scenario 1 Urls Root Intranet url: Http://MyCompanyIntranet.local Department Urls: • http://MyCompanyIntranet.local/Opps • http://MyCompanyIntranet.local/Sales • http://MyCompanyIntranet.local/IT

20. Scenario 1 Pros / Cons Pros • Easy Administration • Auto Share Custom Element • Security Inheritance • Auto Contruction of Navigation • One Content Database Cons • One Content Database = small size. < 50 gb • No Space quotas • Auto Share Custom Elements

21. Scenario 2 – Many Site Collections 1:1:Many Web Application: http://MyCompanyIntranet.local Intranet Home Sales Operations IT

22. Scenario 2 Break Down Intranet Home Sales Operations IT Dept. Sites Teams

23. Scenario 2 Urls Root Intranet url: Http://MyCompanyIntranet.local Department Urls: • http://MyCompanyIntranet.local/Dept/Opps • http://MyCompanyIntranet.local/Dept/Sales • http://MyCompanyIntranet.local/Dept/IT

24. Scenario 2 Pros / Cons Pros • Quota Limits • Separation of content • Can be in different DB’s • Scalable Cons • Manual Site Navigation • Customizations need to be activated to each SC. • Defaults to 1 db

25. Multiple Content Databases • Tools: • Central Admin (Gui) • Stsadm –o CreateSiteInNewDB • Ben Curry - Creating and Managing SharePoint Content Databases

26. Demo

27. Conclusions • Physical Architecture: • Start with small farm so you can scale out. • Grow when you feel pain • Logical Architecture: • Small use with limited growth = One Site collection and Db • Large use and lots of growth = Multi Site collections and Dbs

28. Questions

29. Closing • http://NhGreatLakes.com • http://CharnockConsulting.wordpress.com • http://SharePointPodcast.com