Your SlideShare is downloading. ×
Spstc2011   share point for dotcom sites
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Spstc2011 share point for dotcom sites

348
views

Published on

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

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

0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
348
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
0
Comments
0
Likes
1
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
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
  • Transcript

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

    ×