Best practices for SharePoint solutions architecture, caching and DTAP
1. Alexander Meijers & Roel Hans Bethlehem More best practices with SharePoint solutions
2. Introduction Alexander Meijers Architect at Sparked Subject matter Expert for SharePoint and Search http://www.bloggix.com/blogs/microsoft http://www.dutchsug.nl Roel Hans Bethlehem Architect at Sparked Subject matter Expert for SharePoint
4. Installation Do NOT select basic installation No control SQL Express INSTALLATION
5. Installation Do NOT select Stand-alone installation No Farm SQL Express Single machine INSTALLATION
6. Installation Never click the option “Basic” and “Standalone-alone” installation Production: Never install everything on one server Separate database and front-end Use application server for indexing Think about security Standard security Least privilege rights INSTALLATION
7. Choose your farm wisely Type of farm (5-farm or other) WSS and MOSS cannot be installed on the same server WSS Free with Windows Server Licenses MOSS Standard or Enterprise? Licenses Standard can be upgraded (entering a code) Enterprise cannot be downgraded (only reinstall) FARM
15. Farm Performance Keep your content databases small (around 30-50 GB) Keep your farm scalable Multiple front-ends Use Application Servers for Indexing Do not use virtualization for your database cluster FARM
16. Sharepoint 12 folder / Hive Important folders ControlTemplates Layouts Images Features SiteTemplates Shared with all SharePoint web applications on the same server farm Do not change or replace any of the Microsoft files Service packs will cause problems Microsoft does not support these changes Create your own folders and put files in there ARCHITECTUre
17. How to organize information? Web applications Internet, Intranet, Extranet My Sites Shared Service Providers Site collections Unique security permissions and ownership Lowest level of granularity of quota is the site collection Site usage tracked at the site collection level Content databases; site quota templates Sub-Sites Allow for security inheritance Can re-use security groups created for the site collection Pages Publishing functionality Different views of the same data ARCHITECTURE
18. Architectural decisions Why more than 1 Farm? Application/Customization SLAs, Licensing (Internet vs. Intranet CAL), Isolation (No Scale) Why more than 1 SSP? Isolation and Service Needs Why more than 1 App Pool? Security Isolation, Memory and CPU isolation, Auth requirements Why more than 1 Site Collection? Separation/delegation of ownership, quotas, ability to split across databases Why one site collection? Global Navigation, Inheritance of style/Master page, Security inheritance, Query web parts, Site Collection policy and content types enforcements ARCHITECTURE
19. Features Any unit of functionality for SharePoint Described by: Feature.xml Possibly some element.xml files Delivers functionality like: Adding menu items on several places Adding templates, files, Web Parts Can contain list definitions ARCHITECTURE
21. Caching don'ts Setting memory based caching can waste valuable memory (ASP.NET may flush cache to make room!) Never cache search results – disable search results layout page cache Never cache personalized web parts CACHING
22. DTAP model Keep your environment up-to-date MOSS 2007 / WSS service packs Infrastructure update Cumulative update august 2008 (every two months from now) Keep DTAP in sync Acceptance must be an exact hardware copy of production Use WSP packages for deployment Check with SharePoint Best Practice Analyzer Rights Developers can only access development and test Customer uses acceptance for functional acceptance DTAP
23. Resources Best practices resource center for SharePoint 2007http://technet.microsoft.com/en-us/office/sharepointserver/bb736746.aspx Patterns and practices SharePoint guidancehttp://www.codeplex.com/spg Best practices for SharePoint guidance http://msdn.microsoft.com/en-us/library/dd203468.aspx SharePoint 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=110087 Other resources such as http://www.codeplex.com / http://www.dutchsug.nl / www.microsoft.com/sharepoint
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