More Best Practices With Share Point Solutions
2 likes468 views
This document provides best practices for SharePoint solutions. It discusses installation best practices such as avoiding basic or standalone installations and separating database and front-end servers. It also covers farm architecture such as example small, medium, and large farm configurations with separate web front-end, application, and database servers. Additional topics include the SharePoint 12 folder structure, organizing information through web applications and site collections, caching techniques, and maintaining a DTAP environment.
More Best Practices With Share Point Solutions
- 1. Alexander Meijers & Roel Hans BethlehemMore best practices with SharePoint solutions
- 2. IntroductionAlexander MeijersArchitect at SparkedSubject matter Expert for SharePoint and Searchhttp://www.bloggix.com/blogs/microsofthttp://www.dutchsug.nlRoel Hans BethlehemArchitect at SparkedSubject matter Expert for SharePoint
- 4. InstallationDo NOT select basic installationNo controlSQL ExpressINSTALLATION
- 5. InstallationDo NOT select Stand-alone installationNo FarmSQL ExpressSingle machineINSTALLATION
- 6. InstallationNever click the option “Basic” and “Standalone-alone” installationProduction: Never install everything on one server Separate database and front-endUse application server for indexingThink about securityStandard securityLeast privilege rightsINSTALLATION
- 7. Choose your farm wiselyType of farm (5-farm or other)WSS and MOSS cannot be installed on the same serverWSSFree with Windows ServerLicensesMOSS Standard or Enterprise?LicensesStandard can be upgraded (entering a code)Enterprise cannot be downgraded (only reinstall)FARM
- 8. Small Farm (Example)PhysicalLogicalServer 1 & 2:Content SitesSSPSSP admin siteShared servicesShared web servicesCentral admin (only svr 1)Load balanced servers: Web front end
- 9. ApplicationsServer 3All databasesDedicated SQL serverFARM
- 10. Medium Farm (Example)PhysicalLogicalServers 1 & 2:Content SitesSSPSSP admin siteShared servicesShared web services Load balanced servers: Web front end
- 11. ApplicationsApplication server (Index)Server 3SSPShared service (Index)Shared web servicesCentral AdminApplicationsClustered SQL serverServer 4 & 5All databasesFARM
- 12. Large Farm (Example)PhysicalLogicalWFEs: servers 1 - 4:Content SitesSSPSSP admin site Web front end App servers: servers 5 - 10:SSPSvr5 - 6: Shared service (Index)Svr7 - 8: Shared service (Search)Shared web services (Search)Svr 9 – 10: Shared service (Excel)Shared web services (Excel)Central Admin (server # 5)Application servers: Index
- 13. Search
- 14. Excel calculationClustered SQL serverServer 11 and 12All databasesFARM
- 15. Farm PerformanceKeep your content databases small (around 30-50 GB)Keep your farm scalable Multiple front-endsUse Application Servers for IndexingDo not use virtualization for your database clusterFARM
- 16. Sharepoint 12 folder / HiveImportant foldersControlTemplatesLayoutsImagesFeaturesSiteTemplatesShared with all SharePoint web applications on the same server farmDo not change or replace any of the Microsoft filesService packs will cause problemsMicrosoft does not support these changesCreate your own folders and put files in thereARCHITECTUre
- 17. How to organize information?Web applicationsInternet, Intranet, ExtranetMy SitesShared Service ProvidersSite collectionsUnique security permissions and ownershipLowest level of granularity of quota is the site collectionSite usage tracked at the site collection levelContent databases; site quota templatesSub-SitesAllow for security inheritanceCan re-use security groups created for the site collectionPagesPublishing functionalityDifferent views of the same dataARCHITECTURE
- 18. Architectural decisionsWhy more than 1 Farm?Application/Customization SLAs, Licensing (Internet vs. Intranet CAL), Isolation (No Scale)Why more than 1 SSP?Isolation and Service NeedsWhy more than 1 App Pool?Security Isolation, Memory and CPU isolation, Auth requirementsWhy more than 1 Site Collection?Separation/delegation of ownership, quotas, ability to split across databasesWhy one site collection?Global Navigation, Inheritance of style/Master page, Security inheritance, Query web parts, Site Collection policy and content types enforcementsARCHITECTURE
- 19. FeaturesAny unit of functionality for SharePointDescribed by:Feature.xmlPossibly some element.xml filesDelivers functionality like:Adding menu items on several placesAdding templates, files, Web PartsCan contain list definitionsARCHITECTURE
- 21. Caching don'tsSetting memory based caching can waste valuable memory (ASP.NET may flush cache to make room!)Never cache search results – disable search results layout page cacheNever cache personalized web partsCACHING
- 22. DTAP modelKeep your environment up-to-dateMOSS 2007 / WSS service packsInfrastructure updateCumulative update august 2008 (every two months from now)Keep DTAP in syncAcceptance must be an exact hardware copy of productionUse WSP packages for deploymentCheck with SharePoint Best Practice AnalyzerRightsDevelopers can only access development and testCustomer uses acceptance for functional acceptanceDTAP
- 23. ResourcesBest practices resource center for SharePoint 2007http://technet.microsoft.com/en-us/office/sharepointserver/bb736746.aspxPatterns and practices SharePoint guidancehttp://www.codeplex.com/spgBest practices for SharePoint guidance http://msdn.microsoft.com/en-us/library/dd203468.aspxSharePoint Deployment Planning Serviceshttps://iwsolve.partners.extranet.microsoft.com/SDPS/Downloadable book: Design and build sites for Office SharePoint Server 2007http://go.microsoft.com/fwlink/?LinkId=110087Other resources such as http://www.codeplex.com / http://www.dutchsug.nl / www.microsoft.com/sharepoint
- 24. Questions?
Editor's Notes
- #7: Best practice installation:http://www.xs4all.nl/~ykuijs/HOWTO%20-%20Install%20MOSS2007%20v2.0.pdfChoose your security environment (Office SharePoint Server)http://technet.microsoft.com/en-us/library/cc262843.aspx Review the secure topology design checklists (Office SharePoint Server) http://technet.microsoft.com/en-us/library/cc263306.aspx Plan security hardening for server roles within a server farm (Office SharePoint Server)http://technet.microsoft.com/en-us/library/cc262849.aspx Plan for administrative and service accounts (Office SharePoint Server)http://technet.microsoft.com/en-us/library/cc263445.aspx
- #12: http://www.bloggix.com/blogs/microsoft/archive/2008/05/29/automatically-creating-content-databases.aspx
- #17: http://tomblog.insomniacminds.com/2008/07/30/sharepoint-internals-clearing-configuration-cache-caveat/