Introduction to SharePoint 2010

Editor's Notes

• #2 Welcome to this introductory session of SharePoint 2010. Let me walk you through the different aspects of SharePoint that we would be discussing today.
• #4 Think of SharePoint 2010 Sites as a “one-stop shop” for all your business Web sites. It provides a full set of tools that your people can use to create any kind of site, plus a single infrastructure that simplifies site management. From a team site for colleagues, to an extranet site for partners, to an Internet site for customers, people can share and publish information using one familiar system.
• #6 Before SharePoint arrived, there was a product called Site Server (and Site Server Commerce Edition) that contained features including: web content management and replication, site analytics, personalisation, indexing/search, document management and ecommerce.In 1998 Microsoft announced that the next version of Exchange, codename Platinum, would include a new information store - the Web Store - designed for handling documents and web content, as well as email. A new product, codename Tahoe, would enhance Platinum by introducing document management through a technology called WebDAV - Document Authoring and Versioning - and an improved indexing/search engine. In April 1999, a toolkit originally called the Digital Dashboard Starter Kit was released as a free download and introduced Microsoft's first portal framework. The UI of digital dashboard contained 'nuggets' displaying information from different content sources. Nuggets would later be renamed as web parts.In 2000, Microsoft finally released Windows Server 2000 (upgrade from NT 4.0, introducing Active Directory) and SQL Server 2000 (upgrade to SQL Server 6.5). Exchange Server 2000 was completed and also released. By mid-2000, the portal market was taking centre stage and,In October 2003, Microsoft released a new version of Office - Office 2003 - and included the new upgraded SharePoint range within the Office brand. STS was renamed Windows SharePoint Services (WSS), and became part of Windows Server 2003. It provided a collaboration store and a web part user interface built using ASP.NET. SPS v2 was built on top of WSS and named Microsoft Office SharePoint Portal Server 2003 (SPS 2003). SPS contained indexing/search, personalisation and enhanced management/taxonomy.CMS and SPS finally joined together as the two product groups were merged in 2004. Web parts built using ASP.NET were beginning to take on a life of their own and were moved fully into the developer playground. ASP.NET v2, launched at the end of 2005 includes native web parts. Workflow was back on the agenda, and now there is a common engine to build around - Windows Workflow Foundation (WinWF). Just like Windows SharePoint Services (WSS), WinWF will be a native add-on to Windows Server, providing a workflow service that all other applications can build upon.
• #7 SharePoint development can, indeed,mean a number of things. if you want to simply customize SharePoint, you may onlyhave to interact with page layouts or master pages (that is, the way in which you structure contentin SharePoint). This needs a basic understanding of HTML editing, CSS,how ASP.NET master pages work. However, if you want to do deeperlevelsolution development, you use SharePoint object model, and leverage.NET and Web services to do this using managed-code(that is, C# and Visual Basic, or VB.NET) solutions that are built and deployed to SharePoint — acomplex type of coding experience for the developer.The fact is that actual development can range fromHTML/XHTML, AJAX, and XSLT to .NET and service-based development SharePoint being a broad platform but also asymptom of the different standards, applications, and interoperability that SharePoint must supportas a good citizen of the Web.Thus, if you break down the useof SharePoint across the three levels shown in Figure, you’llfind the largest population ofSharePoint consumers interactwith the Applications level.These are the end users, and theyrepresent your core audience whenbuilding and deploying your customapplications to SharePoint.Next, you may also operate at theCustomization level, where power users possess a high degree of SharePoint knowledge. In somecases, you may work with these people, and in others you will work independently of one another.Lastly, there is you: the developer. You are, in many cases, the person who is developing those customapplications for SharePoint. You are the one who is developing that next killer app in the ISVecosystem. SharePoint 2010 is about developer productivity, the availability of rich platform services,and the capability to manage and deploy your applications with maximum flexibility.With regard to developer productivity, this means that you can use either Visual Studio 2010 orSharePoint Designer (SPD) 2010 as your core set of developer tools. As a professional developer,you’ll likely use Visual Studio 2010 as your core toolset — especially if you’re a .NET programmerlooking to get into the SharePoint space. As for SPD, you’re more than likely going to use it toedit master pages and page layouts, as well as to build declarative or rules-based workflows using avisual rules approach (for example, using Visio 2010 and SPD 2010). And as a complement to thesetools, you may also use Expression Blend — either as a way to build more advanced and interactiveUIs (through Expression Blend) or through Expression Web for baseline Web sites.
• #9 For the end user, SharePoint enhances productivity by providing a core set of connectedapplications that essentially act as the Web-based application platform. The applicationsenable people to connect using wiki sites, workspaces, lists, document libraries, and integration withMicrosoft Office applications, such as Outlook, Excel, and Word 2010.From an organizational point of view, sharepoint provides a central point of collaboration — be it through an organizational portal, a team site, ora personal My Site. It also enables to integrate LOB systems, such as SAP, Siebel,PeopleSoft, and Microsoft Dynamics, into end user experience through SharePoint.Activities for example routing documents through managedprocesses, providing BI dashboards, or supplying audit tracking for documents in the RecordCenter. In essence, SharePoint 2010 represents a platform that offers the organization a lot of functionalityto do many different things, with collaboration lying at the heart of them.
• #12 SharePoint Server 2010 for Internet SitesBoth editions can be run on-premise or by a SharePoint Hosting Provider like Fpweb.net.Standard Edition:  For SMBs looking to create Internet (www) or Extranet (partner) sites using the standard features of SharePoint Server 2010.Enterprise Edition:  Similar to Standard Edition, but with more scalability and management functions. SharePoint Online for Internet SitesThe second cloud version of SharePoint hosting from Microsoft.  This offering will allow customers to host their extranet or public-facing site outside their network.  
• #13 Microsoft now provides handful different options for us to setup a SharePoint 2010 environment. They are:Base machine installation (AKA On-the-metal installation)Bootable VHDVirtualizationIn this option you will be installing everything in your base machine and we require following hardware configurations:Hardware/ Software:Intel Core 2 Duo Processor with 64-bit supportMinimum 4 GB RAMMinimum 80 GB Hard Disk spaceBootable VHDThis is a new feature provided only by Widows Server 2008 R2 and Windows 7 operating systems. With this feature you can have any of the above operating system as your primary operating system and any no of bootable .VHDs running from above mentioned operating systems based on your disk space available.Virtualization can be achieved by using either VMware or Hyper-V. Hyper-V comes free as an add-on to Windows Server 2008 R2 and for VMware you need to pay additionally for licensing. Hyper-V comes only with the Windows Server and will not be available with any of the client operating systems. But VMware can be installed to any of the operating systems.
• #19 Farm can be single server or multi server Exactly one configuration database Farm requires Web server(s) and database server Single Server Farm Medium Server Farm Large Server Farm A sharepoint farm is simply a collection of servers that have sharepoint installed on them and are all connected to the same configuration database.
• #20 Service ApplicationsReplacement of Shared Service Providers (SSPs)facilitates sharing resources across sites running in different web applications and different farmsCan run on Web Front End Server (WFE) or Application ServeriWeb applications can be assoicated with different service offerings 
• #21 Every SharePoint Web application runs as one large ASP.NET application. A sharepoint farm typically runs two or more web applications. Each web application has one or more content database. Web application security configured independently. The introduction of claims-based security support into SharePoint 2010 provides developers with new possibilities for configuring a Web application. One such possibility is the ability to outsource identity management to an identity service publicly available on the Internet, such as Windows Live ID. This approach gives developers the ability to track users for the purposes of security, auditing, and personalization but without the hassles of setting up a user database, storing credentials, and dealing with all the associated password management headaches.