SharePoint Architecture

Agenda
SharePoint Foundation 2010 Architecture
ASP.NET 3.5 integration
SharePoint Sites, List, Document Libraries
Site Columns & Content Types
SharePoint Site Page Customization
User requests
Load balances web
front end servers
Application
servers
2 Clustered SQL server
Index Query Query Calc +
10 Server Farm (Large)
User requests
Web front ends
+ application(s)
Application(s)
Clustered SQL server
5 Server Farm (Medium)
3 Server Farm (Small)
User requests
Each load-balanced server
includes:
Web front end
Applications
Dedicated SQL server
Single Server
Web front end
Application
Database
One Server which contains:
User Requests
Picking Your Topology
Availability
P
e
r
f
o
r
m
a
n
c
e

SharePoint Environment
SharePoint data and content stored in SQL Server
Provides foundation for scaling to Web farm environment
Configuration data stored in WSS configuration database
Site content and customizations stored in content databases
SharePoint Terminology
Farm
SPFarm
Web Applications
SPWebApplication
Site Collections
Site collection
SPSite


Site
SPWeb
Root Site
Sub sites
Field 1 Field 2 Field 3
Item 1
Item 2
Item 3
Item 4
Item -
SPListItem
List - SPList
Field 1 Field 2 Field 3
File 1
File 2
File 3
File 4
File SPFile
Folder - SPFolder

Document Library - SPDocumentLibrary
Lists
Important WSS v3 Concepts
Farm
The highest-level scope for a SharePoint deployment
An installation of one of more Web servers and back-end servers
Each WSS farm has one and only one configuration DB
Web Application (a.k.a. Virtual Server)
An IIS Web site extended with WSS
Entry point capable of hosting 10,000s of site collections
Site Collection (a.k.a. Site)
Unit of scale and ownership containing top-level site
Stored in one specific content DB
Site (a.k.a. Web)
Many per site collection
Uses same content DB as parent site
MOSS 2007
Windows SharePoint Services (WSS v3)
Site and Workspace Provisioning Engine
Out-of-the-box Collaboration Services
Microsoft Office SharePoint Server (MOSS)
User Profiles, Search, Workflows, WCM
BDC, Excel Services, Forms Services, ECM

Windows SharePoint Services 3.0 (WSS v3)
Browser Clients
MS Word Clients
MS Outlook Clients
Microsoft Office SharePoint Server 2007 (MOSS)
Windows Server 2003 or 2008 (32-bit or x64)
Internet Information Services 6.0 or 7.0
.NET Framework 3.0
SharePoint Server 2010
An evolved version of MOSS and WSS v3
Microsoft SharePoint Server 2010
Microsoft SharePoint Foundation 2010
Development can now be done on client OS
Significant enhancement for many development teams


Microsoft SharePoint Foundation 2010
Browser Clients
MS Word Clients
MS Outlook Clients
Microsoft SharePoint Server 2010

Windows Server 2008 (x64 only) for Production Environments
Windows 7 or Vista (x64 only) for Development Environments only

Internet Information Services 7.0
.NET Framework and ASP.NET 3.5 SP1
New Databases
F
a
r
m

Config
Admin_Content
Application Registry
Service
Secure_Store_Service
StateService
ManagedMetadata
Web Analytics Web
Service
WSS_Usage
Reporting_DB
Staging DB
S
e
r
v
i
c
e
s

Search
Search_Service_Application
Crawlstore
SearchDB
PropertyStore
WSS_Search
People
SocialDB
ProfileDB
SyncDB
Service
Sync
BDC_Service_DB
Word Conversion
Service Application
Performance_Point
C
o
n
t
e
n
t

WSS_Content_GUID
WSS_Content_GUID1
WSS_Content_GUID2
SharePoint 2010 Team Site
Pages Everywhere
Every team site has a pages
library
Create a new page with a
single click
Just enter a name
Ready to go
[[Wiki Linking]] to
Pages
Lists
Items
Documents

Edit Like in Word
Single click editing experience
Transition to edit is quick and seamless
Type into page and format text like in Word
Full set of rich text controls for formatting and layout
Streamlined insert experience for images, links
Asset library
Edit Pick Content Insert
Safe and Simple
Auto-save every
minute, no data-loss
Only save if user made
changes
Edit\Stop Editing no
prompts
Whoops Protection
Rich Text Editor has
undo stack
Versioning turning on,
in case you want to
revert

Central Admin UI
Contextual
Ribbon

Server 2008
Style UI

Easier to find.
Site Settings
Site Settings
Site Settings
Title, Description & Appearance





SharePoint as a Solution Platform
Microsoft SharePoint Foundation 2010 supplies core
workspace services
Particularly suited for building scalable Web-enabled applications
Microsoft SharePoint Foundation 2010 provides out-of-box
collaboration solutions
Operating System Services
Database Search Workflow
ASP.NET (Web Parts, Personalization, Master Pages, Provider Model for navigation, security, etc.)




SharePoint Foundation 2010 Core Workspace Services
Storage
Repository
Metadata
Versioning
Backup
Security
Rights/Roles
Pluggable Auth
Per Item
Rights Trimming
Mgmt
Admin UX
Delegation
Provisioning
Monitoring
Topology
Config Mgmt
Farm Services
Feature Policy
Extranet
Site Model
Rendering
Templates
Navigation
Visual Blueprint
APIs
Fields/Forms
OM and SOAP
Events
Deployment
Sites Communities Portal Content Search Insights Composit
SharePoint Server 2010 Solutions Built On SharePoint Foundation 2010
Microsoft
SharePoint
Foundation
2010
ASP.NET Integration
ASP.NET 3.5
SharePoint Foundation 2010
ASP.NET 2.0
Windows SharePoint Services 3.0
Windows
SharePoint
Services
Version 3
SharePoint Foundation 2010
SharePoint Foundation 2010 is built on ASP.NET 3.5
WSS integration in line with best practice ASP.NET extensibility
ASP.NET 3.5 provides parser for .aspx pages from database
ASP.NET 3.5 provides new Web Part infrastructure
ASP.NET 3.5 offers Master Pages feature for page templates
ASP.NET 3.5 offers rich navigation infrastructure
SharePoint Application
Landscape
SharePoint Core

.NET | ASP.NET
Customized
SharePoint Server
2010 Workloads
Portal for LOB
Application Data
Single Web Part
Solutions
Business
Collaboration
Applications
Sites
A SharePoint site is a storage container for content
Site can contain lists which store list items
Site can contain document libraries which store documents
Site can contain child sites help to partition and organize content

A SharePoint site provides a browser-based UI
Site provides customizable home page via Web Part
Site provides Form pages for each list and document library
Site provides access to shared application pages

A SharePoint site provides a built-in security model
Site access configured in terms of users and groups
Permissions applied at site collection, site, list and item level
Lists
List types designed to store content in form of items
Each list type defines schema including set of columns
List type includes Form pages (e.g. AllItems.aspx)
List type can have multiple views

Creating a list instance from a list type
Create list instance using WSS built-in list types (e.g. Contacts)
Create list instance from custom list and define columns
Users can add/remove/modify columns on list instance

List template used to create list type from instance
List instance can be template-ized from list settings page
List templates create new list types scope at site collection
Document Libraries
SharePoint Document Library is a hybrid list type
Provides support for uploading/storing documents
Provides support for document check-in/check-out
Provides support for document versioning
Document images store in SQL Server content DB

Document Library has a document template
Document template used when user clicks New command

Document Library can contain custom columns
Provide easy way to add metadata to documents

Data Storage Scenarios
Consider the concept of the "list"
atomic unit of storage from prehistoric times
grown up significantly since the days of flat-file databases
Lists have been the foundation of each versions of WSS

The "list" in the Enterprise
Huge document libraries, record repositories, knowledge bases,
web content, etc.

Key Requirements
Scalable storage
Accessible and discoverable
More server-side control over content
Highly customizable behaviors
Managing Content Issues
Problems with managing content in large companies
Many document types identified in an organization, but there is
no clear way to enforce standards
There's a need to create different types of documents and store
them all in one central location
Content management application should make list of actions
available to users depend on the type of content or document

WSS provides new features to solve these problems
Site Columns
Content Types
Site Columns
Site column is a reusable column definitions
Site column can be reused across multiple lists
Site column scoped to site and stored in Site Column Gallery
Site column visible within site collection to all child sites
Using a Site Column in a List
Site Columns can be used in List Definitions
Site column represents a reusable, named column definition
Site column used in lists, document library or content types
Updates to a site column can optionally be pushed out to lists,
document libraries and content types where it has been used
Content Types
Foundation for content management in SharePoint
Reusable definition for list schema
Defines constraints and requirements for an item type
Created by users and developers
Reused and extended by users
Examples for Content Types
Proposals for software projects
Requires author
Requires data for scheduling and budgeting
Requires reviews by technical and finance departments
Customer presentation
Requires author
Requires reviews by legal and art departments
Customer report for consulting work
Requires consultant name
Requires hourly billing information
Content Types
A content type definition can include
Columns to represent metadata or properties
A document template on which to base documents of this type
Custom forms for New, Edit, and Display use with content type
Event handlers
Workflows
Supporting Multiple Content Types
Lists can support multiple content types
Makes it possible to support heterogeneous content
New button becomes a dropdown list
Input and display forms change depending on content type
Inheriting Content Types
Allows base definition reuse across multiple types
Core properties can be defined in base content type
Base content type inherited by more specific content types
Base Document
Litware
Document
Litware
Presentation
Litware
Customer Report
Litware
Proposal
Web Pages in SharePoint Sites
SharePoint Sites have two kinds of pages (.aspx
files)
Site pages that can be customized on a per site basis
Application pages that cannot be customized on a per site basis
Site pages are initially uncustomized
Uncustomized version stored once on front-end Web server
Uncustomized page also known as "ghosted" page
Upon editing, customized site page stored in content DB
Application pages only live on front-end Web server
Single copy of application page used for all WSS sites
Served out of the _layout virtual directory
The _layouts directory
_layouts directory provides common point for sites
Configured as virtual directory for all WSS Web applications
C:\Program Files\Common Files\Microsoft Shared\
web server extensions\14\TEMPLATE\LAYOUTS
Provides standard relative URL for all sites in Web Application
/_layouts/SiteSettings.aspx
Used for WSS system application pages
Can also be used for custom application pages

Images directory configured in _layouts directory
Used by Microsoft to deploy standard WSS images
/_layouts/images/ALLUSR.GIF
Can also be used to deploy custom images/graphics

Child Sites
WSS site can contain one or more child sites
Site hierarchy can be designed to partition and manage content
Security can be configure differently for each site in hierarchy