Sharepoint 1

Tuesday, November 12, 2013

Sharepoint is a platform that sits on top of ASP.NET

Provides business services

Supports extensibility

Enables integration with external sites/services

Sharepoint Rocks!!!

What's in this article:

  1. Site Provisioning
  2. Information Collaboration, working with lists and libraries
  3. Architecture, integrating with IIS and ASP.NET, working with pages
  4. Developer Tools and API's, developer environment and visual studio tools, server and client object model, REST Api
  5. Features and solutions, extensions on top of SharePoint
  6. Sharepoint Apps, extensions outside of Sharepoint

Microsoft Sharepoint Foundation 2013

  • Free add on to supported operating systems
    • 64 Bit Windows Server 2008 R2 or 2012
  • The core or foundation of Sharepoint
    • Scalable data driven architecture
  • Designed to be highly customizable by end users
    • Many customizations can be done through the browser
  • Designed to be extended by developers
    • Built on top of ASP.NET and .NET Framework 4.5
    • Extensible framework through solutions and features
    • Visual Studio 2012 includes tooling to assist in development

Microsoft Sharepoint Server 2013

  • Retail product built on top of Sharepoint Foundation
  • Comes in standard and enterprise edition
  • Additional features for enterprise scale
    • Access Services
    • Business Intelligence
    • SharePoint Apps
    • Excel Services
    • BCS
    • PerformancePoint
    • SharePoint 2013 Workflow
    • Enterprise Search
    • Managed Metadata
    • Social
    • Records Management
    • Web Content Management
    • And much more...

Office 365/SharePoint Online

  • Variety of plans to meet business needs and budget
  • End user
    • All plans include most of the features from foundation
    • Small business plans get some server features
    • Midsize and enterprise plans add more server features
    • None of the plans match what is available on premise
  • Developer
    • Custom development is limited to sandboxed solutions and apps

SharePoint Apps

  • New development, deployment, hosting model for extensions to SharePoint
    • Adds to the Solution Model, does not replace it
  • Conceptually similar to apps for phones/tablets
    • Find, try, buy concept
    • Public and private app stores(catalogs)
  • Apps for sharepoint are self-contained pieces of functionality that extend the capabilities of a sharepoint web site. Apps integrate the best of the web and sharepoint; they are targeted and easy to use and do a great job at solving a user need.

Administrators view sharepoint architecture

  • Sharepoint deployment is known as a farm
    • One or more servers
    • SQL server database to store configuration data
  • Simple farm may consist of single server and sql server express database
  • Files used by the farm are stored in the sharepoint system folders
    • Also known as the hive
  • Web application
    • Sharepoint web applications are extended IIS sites
    • Virtual directories point to the share point system folders
    • Multiple web applications used when multiple authentication modes required
    • Intranet: Windows authentication
    • Extranet: Forms based authentication
    • Internet: Anonymous
  • Site collection
    • Sites form a tree structure
    • One site is the root or top level site
  • Boundary for administrative privilege
  • Boundary for visibility of data
  • Info associated with site collection/sites stored in content database

End users view sharepoint architecture

Sharepoint as a provisioning engine

  • Quickly create sites, pages, lists, libraries without
    • Writing code
    • Configuring databases
    • Fiddling with IIS
    • Pushing files around
    • Changing security settings on files or in IIS

Sharepoint security

  • By default sharepoint sites require authentication
    • Possible to grant anonymous access if desired
    • Sharepoint 2013 uses claims based authentication
      • Providers: windows, forms based, third party(saml)
      • Classic mode authentication has been deprecated
  • Sharepoint manages authorization itself
  • Main permission groups are:
    • Owners: administrative privilege within the context
    • Members: can contribute to and manage lists and libraries
    • Visitors: read only access to content
  • Main levels of security are site collection, site, list and list item
    • By default security is inherited from parent
    • Security can be customized at any of these levels

Open sharepoint 2010 central administration

I installed sharepoint foundation 2010 locally since 2013 doesn't run on a client installation

Click on link create site collections

Fill in this data and select team site

Provide username for administrator and click ok

Database entries for the site collection and site at the root of sitecollection created

Click on link to newly created site collection and the new training site is opened

Create new site collection named trainingdemo, template blank site in central administration

Click on the url

View the sharepoint 2010 site that has been created

Click on tab site actions, select more options

Click on Contacts List template and name it contacts

Click create, the provisioning engine creates new entries in content database, there is a new list that uses the contact schema

Click add new item, a dialog box pops open, add some entries and save

View the list of items, in the ribbon possible to view, edit and delete. checkboxes to select individual or multiple items

Navigate to the root site click on site actions and select new site

Select teamsite, name and url online and click create

Here is the online training site, the provisioning engine creates entries in the database and then redirects to this new site

Navigate to root site notice on top link bar a link to childsite has been added

Click on site actions, select site settings

In category Look and Feel click on site theme

Select mission theme and click apply

View the newly applied mission theme

Go into site actions and click on site permissions, by the way switched the theme to bittersweet

There are 3 groups

Click on owners and see that I am a member of that group

In ribbon click on grant permissions

type testuser and ctrl+k to check the name, grant permission to members group

Click ok, go into members group and see the new member, now testuser has access to training site as a contributor, permissioms are inherited so access to all child sites as well

Logged in as testuser, click on site actions only viewing content enabled and not creating lists, pages, libraries and sites since only contributor permission

Open custom site and see that inherits permissions from parent

Click on stop inherit permissions

Now the web site has unique permissions

Click on inherit permissions to reverse

Back to its initial state of inherited permissions from site collection trainingdemo

Provisioning engine

  • Makes it easy for end users to create content
  • Reduces the need for IT intervention
Default Success Warning Important Info Inverse
B S W I ? O