Sps Boston   The Share Point Beast
Upcoming SlideShare
Loading in...5

Sps Boston The Share Point Beast



What every developer and architect need to understand before diving head first into SharePoint.

What every developer and architect need to understand before diving head first into SharePoint.



Total Views
Slideshare-icon Views on SlideShare
Embed Views



0 Embeds 0

No embeds



Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
Post Comment
Edit your comment

    Sps Boston   The Share Point Beast Sps Boston The Share Point Beast Presentation Transcript

    • Wrapping your head around
      The sharepoint beast
      Mark Rackley - SharePoint Architect/Developer
      Email: mrackley@gmail.com
      Blog: http://www.sharepointhillbilly.com
      Twitter: http://www.twitter.com/mrackley
    • Presentation Outline
      Why SharePoint?
      SharePoint Overview
      Logical Architecture & Taxonomy
      Path to development
      End User
      The Importance of Community
      Avoiding Beginner Hurdles
    • 4
      100 M+Licenses, 17k+ Customers,
      $1 Billion Revenue
      Fastest growing server product in Microsoft history
      81 of Fortune 100 Companies
      #1 Portal Vendor
      Forrester April 2005
      Leader in Gartner Portal MQ*
      Top Fortune 500 websites: Viacom, Starbucks, etc.
      Leader in Gartner ECM 2008 & 2009 
      Visionary Gartner ECM MQ*, Challenger in Search MQ*
      325k Portals, Sites and Sub-Sites
      on MS IntraExtranet 15TB DB!
      2250+ SharePoint ISV Partners
      *The Gartner Magic Quadrant is a proprietary research tool developed by Gartner Inc., a US based research and advisory firm. It is designed to provide an unbiased qualitative analysis of a “markets’ direction, maturity, and participants.”
      So… Why SharePoint?
    • What can SharePoint Do For Me?
      Source: http://www.sharepointcowboy.com
    • 5 Stages of Learning SP Dev
      • Denial – “They aren’t really going to make me learn this.  They’ll forget all about it in the next few months and move onto something new.”
      • Anger – “This is SO stupid! I can’t believe they are making me learn this! It’s impossible!”
      • Bargaining – “Okay.. How about this, I’ll do support 24/7 for the rest of my life, just don’t make me learn this!”
      • Depression – “It’s hopeless.  I’ll never learn this.  I wonder how much it would cost to rent Eric Shupps by the hour?”
      • Acceptance – “Well, it looks like I have no choice… maybe it won’t be that bad?  Hey! At least it will look good on my resume?”
    • 7
      SharePoint is a PLATFORM
      “A ‘platform’ is a system that can be programmed and therefore customized by outside developers — users — and in that way, adapted to countless needs and niches that the platform’s original developers could not have possibly contemplated, much less had time to accommodate.”
      - Marc Andreessen, Netscape
      What IS SharePoint?
    • 8
      SHAREPOINT overview
    • 9
      SHAREPOINT overview
    • 10
      SHAREPOINT overview
      Source: http://www.gilham.org
      Which SharePoint technology is right for you?
    • Terminology (Remember when a Web Application was an actual application?)
      Web Application
      A virtual server that resides on an HTTP server but appears to the user as a separate HTTP server. Several Web applications can reside on one computer, each capable of running its own programs and each having individualized access to input and peripheral devices. Each Web application can have its own domain name and IP address.
      Site Collection
      A set of Web sites on a Web application that has the same owner and share administration settings. Each site collection contains a top-level Web site and can contain one or more sites (or subsites). There can be multiple site collections on each Web application. A site collection can use only a single content database. Everything is now a site collection: a portal is a site collection where Home is the top-level Web site and the areas are sites (or subsites), a channel hierarchy is a site collection where the root channel is the top-level Web site and sub-channels are sites (or subsites).
      A complete Web site stored in a named leaf of the top-level Web site.
      A named subdirectory of the top-level Web site that is a complete Web site. Each subsite can have independent administration, authoring, and browsing permissions from the top-level Web sites and other subsites.
      Top-Level Web Site
      The top, root default site in a site collection. Every site collection has, at its root a top-level Web site. Access to the top-level web site is provided supplying the URL of the site collection (like http://ServerURL or http://ServerURL/sites/SiteCollectionName) without specifying a page name or subsite.
    • 12
      SHAREPOINT overview
    • Logical Architecture & Taxonomy
      Logical architecture model: Corporate deployment
    • Logical Architecture Diagram
    • 15
    • Taxonomy Diagrams
    • Plan Your Logical Architecture & Taxonomy!!
      Where do you want to be in 2 years?
      How many farms? sites?
      Ensure you have the ability to expand
      Take into account licensing costs
      How are users going to connect?
      ISA? F5? SSL? FBA?
      Plan… Plan… Plan…
    • Avoid Analysis Paralysis!
    • Governance
      What is this thing everyone talks about?
      Get executive buy-in
      Set up committee
      As few IT people as possible, but led by IT
      Make sure decision makers from important departments play key role
      Document policies
      Determine correct level of control
      Too much will frustrate users
      Too little will render sites unusable
      Enforce Policies
    • Taxonomy & Governance
      Community/Microsoft Recommended Core Corporate Intranet Taxonomy
    • Path To SharePoint Developer
      End User -> Admin -> Developer
    • Path To SharePoint Developer
      End Users
      Create sites
      Work with lists & Document Libraries
      Use basic web parts
      Manage content
      Add users
      Manage simple workflows
    • Path To SharePoint Developer
      Be End User
      Configure SharePoint farm
      Use Central Admin
      Use STSADM
      Deploy Features
      Add Workflows to Lists
      Configure Search
      Be familiar with all out of the box web parts
      Know 12 Hive structure and what’s in there
    • Path To SharePoint Developer
      Be Admin
      Know how & WHEN to use SharePoint Designer
      Be .NET developer
      Know XSLT, CAML, XML, JavaScript, jQuery, and other acronyms
      Be familiar with SharePoint Object Model
      Be familiar with SharePoint Web Services
      Be able to debug
      Be able to Package
    • What About Architects?
      Be able to use all the acronyms appropriately
      Fake everything else (I’m kidding of course)
    • SPD – A Beautiful Disaster
      SharePoint Designer (SPD)
      The Good
      Don’t have to develop on the server
      SPD Workflows
      Developing Branding
      Data View Web Parts
      The Bad
      SPD Workflows
      The Ugly
      Possible to break a site collection
      Be careful modifying default aspx files
      Migration & Restores
      Don’t tell your boss what you have to do
      CONCLUSION - Don’t give End Users Access! Don’t connect to Production Server unless you fully understand the ramifications.
    • Dev… Rubber Meets The Road
      Dev on VM
      Free VHD from Microsoft (time bombed)
      Build your own if possible
      Windows Server 2003
      SQL Server 2005
      MOSS 2007 (Don’t do basic install!)
      Office 2007 Professional
      SharePoint Designer
      Visual Studio 2008 & Source Safe
      SDK’s etc..
    • Custom Development
      Web Part Development
      Learn File Structure and XML files purpose
    • Development Tools… (There’s an App For that)
      Web Part Development cont.
      STSDev from http://codeplex.com
      Creates structure and XML files for you – avoids typos in XML
      Great build options:
    • More Development Goodness
      Dev/QA Farm
      Have One or Both!
      Should be as identical to production as possible
      80/20 Rule
      If it doesn’t make sense to do in SharePoint DON’T DO IT in SharePoint
      Packages? We don’t need no stinking Packages! Oh wait.. Yes we do…
      Create Deployable Solutions wherever possible
      If 50% of deployment is packages you are ahead of 90% of the companies out there
    • Debugging
      Event Logs
      Admin Tools->Computer Management-> Event Viewer
    • Debugging
      SharePoint Logs
      C:Program FilesCommon FilesMicrosoft ShareWeb Server Extensions12LOGS
      Can write to logs when writing custom code
    • Debugging – Visual Studio
    • DEMO
      The obligatory “Hello World”
    • 35
    • Deployment
      Create deployable solutions when possible
      Site Definitions
      Content Types
      Web Parts
      Data Connection Files
      Create detailed deployment scripts for admins
      Test scripts in QA environment
    • Free Tools Rock
      Internet Information Services (IIS) 6.0 Resource Kit Tools
      Metabase Explorer to fix port conflicts
      Fiddler – Web Debugging Proxy
      Performance Tuning, inspect session data, etc
      Application Pool Manager
      IIS Reset usually not necessary, recycle app pools is much quicker
      SQL to CAML Converter
    • A Word (or two) About Community Don’t leave home without it!
    • Tips when asking for help
      What Version of SharePoint Do You Have?
      WSS 3.0? Standard? Enterprise?
      What Development Limitations Do You Have?
      Custom Code? 3rd Party Web Parts? SPD?
      What is your skill level?
      Get Your Terminology Down!
      For General “How To” Questions Be Detailed
      For Help Fixing Issues
      What are the steps to reproduce the problem?
      Provide Screen Shots
      Did you check the logs?
      Be Patient!
    • OH COME ON!!
    • A Little Knowledge is a Dangerous Thing
      Site Collections
      Make sure you want it to be a top level site; non-trivial to move to sub-site
      All content for site-collection & sub-sites in same content database
      All list data for every site in content database is in same table
      Site features must be activated on parent site to be available to sub-sites
      Document Libraries
      Avoid Sub-Folders unless structure is well defined
      Use Metadata when possible
      Be aware of Versioning!
    • Trying to make your life easier
      Don’t host non-SharePoint Sites on Farm
      SSL (Secure Sockets Layer)
      Create Site Collection as SSL with self signed certificate if don’t have certificate yet
      Consider use wildcard cert – use of SAN (Subject Alternate Name) certificate will mean buying whole new certificate if you add servers
      Service Accounts
      Basic install uses logged in user as service account
      Should not be obvious
      Locked out account will bring down farm
      Site Templates
      Master Pages and Themes must exist on target site
      10mb Size Limit???
      stsadm.exe -o setproperty -pn max-template-document-size -pv 500000
    • How the heck do I…
      Create a blog/wiki/etc. sub-site under a Publishing Site??
      GLOBAL#0 = Global template STS#0 = Team Site STS#1 = Blank Site STS#2 = Document Workspace MPS#0 = Basic Meeting Workspace MPS#1 = Blank Meeting Workspace MPS#2 = Decision Meeting Workspace MPS#3 = Social Meeting Workspace MPS#4 = Multipage Meeting Workspace CENTRALADMIN#0 = Central Admin Site WIKI#0 = Wiki Site BLOG#0 = Blog BDR#0 = Document Center OFFILE#0 = Records Center OFFILE#1 = Records Center OSRV#0 = Shared Services Administration Site SPS#0 = SharePoint Portal Server Site SPSPERS#0 = SharePoint Portal Server Personal Space SPSMSITE#0 = Personalization Site SPSTOC#0 = Contents area Template SPSTOPIC#0 = Topic area template SPSNEWS#0 = News Site CMSPUBLISHING#0 = Publishing Site BLANKINTERNET#0 = Publishing Site BLANKINTERNET#1 = Press Releases Site BLANKINTERNET#2 = Publishing Site with Workflow SPSNHOME#0 = News Site SPSSITES#0 = Site Directory SPSCOMMU#0 = Community area template SPSREPORTCENTER#0 = Report Center SPSPORTAL#0 = Collaboration Portal SRCHCEN#0 = Search Center with Tabs PROFILES#0 = Profiles BLANKINTERNETCONTAINER#0 = Publishing Portal SPSMSITEHOST#0 = My Site Host SRCHCENTERLITE#0 = Search Center SRCHCENTERLITE#1 = Search Center SPSBWEB#0 = SharePoint Portal Server BucketWeb Template  
      stsadm.exe -o createweb -url http://path-to-publishing-site/subsite-name -sitetemplate <template name> -title <title of site>
    • Why Did They Do That?
      I don’t think it means what you think it
    • Really???
      SQL Forms Based Authentication (FBA) Limitations
      Roles in Audiences
    • Isn’t That Just Peachy!
      SQL Forms Based Authentication (FBA) Limitations cont.
      Crawling content secured by FBA (extend for Windows authentication and crawl that)
      Office 2007 integration
      Resolving names
      PROFILE SYNCING!!!!!!!
      Limitations if using ISA
    • To Avoid SharePoint Fail…
      Image Source: http://theroosterstrikes.files.wordpress.com
    • You Gotta Drink the Kool-Aid!
      Read Books
      Setup a VHD
      Read the blogs
      Join the Community
      Start a blog
      Attend events
      Image Source: http://www.irvinehousingblog.com
    • 49
      Mark Rackley
      • Email: mrackley@gmail.com
      • Blog: http://www.sharepointhillbilly.com
      • Twitter: http://www.twitter.com/mrackley