Spstc2011 share point for dotcom sites


Published on

Presentation by me at SharePoint Saturday The Conference in Washington DC on August 12th, 2011.

A review of the major points about how to use SharePoint in a DotCom project.

Published in: Technology
1 Like
  • Be the first to comment

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

No notes for slide
  • HardwareVirtual servers versus physicalProperly scaled memory and CPU Look at scaling the box versus adding more serversPay attention to what servers are slowing down (WFE, App, DB) and scale those firstTuningDatabase – critical to SP successPre-grow if possible, never auto-shrinkTempDB – very important for search and viewsWhen to split Content from Search/ConfigCacheSP Pub Cache (Pub pages only)BLOB Cache (BLOBs only)Other typesASP.Net – programattic cache that is unique to each serverWeb Part Cache – prgrammatic cache that is shared by all SP servers (all users or by user)Partial/Doughnut Cache – mix of various cache methods for specific circumstances
  • Server Sizing MS Recommends8GB RAM for WFEs and App Servers16GB for SQL Server4 cores for WFEsDisk ~80GBConsiderations for upgradesWFE Memory should be fineProcs should be fine Disk (if large index files)App Memory – push to 12GBProcs – 8 cores (Dual quad cores) Disk – (if large index files)SQL Server Memory = 32+GBProcs – 16 cores (4x4way) or more Disk – Depends on usage and content requriementsBut, for DotCom sites…we likely don’t have lots of content
  • Spstc2011 share point for dotcom sites

    1. 1. SharePoint for DotCom SitesFri-S5A-105<br />David C. Broussard<br />Catapult Systems<br />Welcome to SharePoint Saturday—The Conference<br />
    2. 2. Welcome to SharePoint Saturday—The Conference<br />Thank you for being a part of the first SharePoint Saturday conference<br />Please turn off all electronic devices or set them to vibrate.<br />If you must take a phone call, please do so in the hall so as not to disturb others.<br />Open wireless access is available at SSID: SPSTC2011<br />Feel free to “tweet and blog” during the session<br />Thanks to our Diamond and Platinum Sponsors:<br />
    3. 3. Where do we come from?<br />Content Management<br />Server 2002<br />Office SharePoint <br />Server 2007<br />SharePoint Portal<br />Server 2003<br />
    4. 4. Where do we come from?<br />Content Management<br />Server 2002<br />Office SharePoint <br />Server 2007<br />SharePoint Portal<br />Server 2003<br />SharePoint 2010<br />
    5. 5. SharePoint 2010 is the new…<br />Sites<br />Communities<br />Composites<br />Content<br />Insights<br />Search<br />Everything<br />
    6. 6. Web Content Management<br /><ul><li>Authoring
    7. 7. Approving
    8. 8. Scheduling
    9. 9. Deploying
    10. 10. Managing</li></ul>Content<br />
    11. 11. The Transitive Effect of SharePoint<br />
    12. 12. SharePoint = DotCom<br />Sort of…<br />We need to think outside of the box<br />
    13. 13. Intranet versus Internet<br />
    14. 14. DotCom Sites are a different Beast<br />
    15. 15. DotCom Considerations<br />Business Needs<br />End User Experience<br />Performance<br />Hardware<br />Software<br />Authentication/Personalization<br />Branding<br />Authoring Experience<br />
    16. 16. Business Needs<br />Who is my site for?<br />Demographics of users (age, gender, skills, language)<br />Current or new<br />What is my website going to do?<br />Selling a product<br />Informing people<br />Where will it be viewed?<br />Desktop/Mobile/Tablet<br />Home/Work<br />When will it be used?<br />Peak Periods of use (8-5, lunch, etc.)<br />Why are we doing this?<br />How do I measure success<br />
    17. 17. End User Experience<br />Make the user the focus of every design decision<br />Remember that the content Authors are users too<br />Iterate, Iterate, & Iterate<br />
    18. 18. Performance<br />Let’s define performance <br />Page Load vs Transaction<br />Determine Average User Load<br />Total users * % Concurrent Users / Time Per request<br />Test till it breaks<br />Primary Mode vs Fail Over tests<br />Make sure you compare Apples to Apples<br />
    19. 19. Performance<br />Increase Hardware<br />Server Size and/or # Servers<br />Tune the systems<br />Database tuning<br />Modify Cache settings<br />SharePoint Publishing Cache (pub pages only)<br />BLOB Cache<br />Server Side Cache settings (ASP.Net Cache, Web Part Cache, Partial Cache)<br />http://blogs.catapultsystems.com/tlingenfelder/archive/2011/03/24/sharepoint-caching-techniques.aspx<br />
    20. 20. Hardware<br />Farm Sizing<br />Usage requirements<br />Availability Requirements<br />Fail-over Requirements<br />How many farms?<br />Prod, Test, Development, DR<br />Server Sizing<br />Memory, CPU, Disk<br />
    21. 21. Hardware<br />Highly Available SharePoint farm<br />Medium SharePoint farm<br />Small SharePoint farm<br />
    22. 22. Hardware<br />High Availability<br />Do we need it?<br />Do we need App Server redundancy?<br />Virtualization<br />What can we virtualize?<br />What should we not?<br />Disaster Recovery Failover<br />Hot stand-by<br />Virtual stand-by<br />Cloud<br />
    23. 23. Hardware - Security<br />
    24. 24. Software<br />SharePoint Server 2010 for Internet Sites<br />Enterprise or Standard<br />No CALs for external users (still need them for internal users, except authors)<br />Must be on all SharePoint servers in farm<br />Works for both Authenticated and Anonymous<br />Pre-Prod and DR licenses<br />Pre-Prod can be MSDN (10/subscription)<br />DR (active) are considered Production and must be licensed<br />Cloud implementations can “rent” licenses<br />
    25. 25. Authentication/Personalization<br />Authentication Options<br />Anonymous users<br />Windows Authentication<br />Claims/Forms Based Authentication<br />Personalization<br />User Profiles<br />Web Part Personalization<br />Page Personalization<br />
    26. 26. Branding<br />
    27. 27. Branding<br />Pixel perfect rendering is required<br />Cross Browser compatibility<br />IE (6,7,8,9), Firefox, Chrome, Safari (Mac), Mobile browsers<br />Active Content (Javascript, JQuery, Silverlight, Flash) – Graceful Degradation<br />Do we style just publishing pages, or all pages? What will the user see?<br />
    28. 28. Branding<br />Designers need a Design Environment just like Developers need a Developer Environment<br />Lock down Production Designer folders (_catalogs/masterpage, /StyleLibrary, etc.)<br />Sandbox solutions can reduce deployment headaches, but can cause governance headaches<br />
    29. 29. Authoring Experience<br />Content Organization<br />How often will it change?<br />Content changes<br />Navigation changes<br />Approval process<br />Staging of content<br />Content Author Skills<br />Approval and Control of content<br />
    30. 30. Summary<br />SharePoint does WCM<br />DotCom sites are very different from Intranets<br />Focus on the User Experience<br />Remember the goals of the Website (What get’s measured, get’s done)<br />Test, Test, Test…and then test some more<br />
    31. 31. Questions<br />http://blogs.catapultsystems.com/dbroussard<br />
    32. 32. Thanks to Our Other Sponsors!<br />Thanks to our Sponsors<br />
    33. 33. Session Evaluation<br />Please complete and turn in your Session Evaluation Form so we can improve future events. Survey can be filled out at:<br />http://app.fluidsurveys.com/surveys/spstc2011-<br />and add the Session number to the URL<br />Presenter: David C. Broussard<br />Session Name: SharePoint for DotCom Sites<br />Session No.: Fri-S5A-105<br />