More Best Practices With Share Point Solutions


Published on

Published in: Technology
  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • Best practice installation: your security environment (Office SharePoint Server) Review the secure topology design checklists (Office SharePoint Server) Plan security hardening for server roles within a server farm (Office SharePoint Server) Plan for administrative and service accounts (Office SharePoint Server)
  • More Best Practices With Share Point Solutions

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