Ryan charnock mct @ new horizons mi
Download
1 / 29

Sharepoint Architecture Basics - PowerPoint PPT Presentation


  • 64 Views
  • Uploaded on

Ryan Charnock MCT @ New Horizons MI. Sharepoint Architecture Basics. OverView. Physical Architecture Server Types and Farms Logical Architecture Pros Cons of different Logical Archs . Content Database Demo Conclusions and Questions. Physical Players. Web Front End server(WFE)

loader
I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
capcha
Download Presentation

PowerPoint Slideshow about ' Sharepoint Architecture Basics' - lucas-william


An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript
Ryan charnock mct @ new horizons mi

Ryan Charnock

MCT @ New Horizons MI

Sharepoint Architecture Basics


Overview
OverView

  • Physical Architecture

  • Server Types and Farms

  • Logical Architecture

  • Pros Cons of different Logical Archs.

  • Content Database

  • Demo

  • Conclusions and Questions


Physical players
Physical Players

  • Web Front End server(WFE)

  • Database Server (db)

  • Application Server (app)

  • Query Server (qu)


Web front end server
Web front End Server

What: Send and Receive Http requests for pages

Why: Server to field user requests for access

Think of: A bank teller


Database server
Database Server

What: Holds configuration and content data in SQL Server databases.

Why: Structured storage within a known storage system

Think Of: Bank vault. Keeper of the cash.


Application server
Application Server

What: Run Share Services for farm

Why: Scaled out delegation of centralized server

Think of: Federal Government – provide centralized services to the 50 states


Farms
Farms

  • Single Server

  • Small farm (farmet, Toy-farm)

  • Large farm / scaled out


Single server
Single Server

WFE

Application Srv

Database Srv


Small farm
Small Farm

WFE

App

DB


Large farm
Large Farm

WFE

Fail Over Cluster

APP

DB

  • WFE

DB

  • WFE


Logical players
Logical Players

  • Application Pool

  • Web Application

  • Site Collection


Application pool
Application Pool

What: Memory container with an AD account to represent Web Applications in it to other resources

Why: One app crash only that app

Think of: Chained together convicts.


Web application
Web Application

What: IIS Virtual Server. Determines the URL:Port, Authentication method, Content Database Name

Why: Creates a website for hosting SharePoint content.

Think of: A convention center / Cobo.


App pool web app relationship
App. Pool / Web app. relationship

Application Pool

Web Application:

http://mycompanyintran.local

Ntml – Window Authentication

Database - WSS_Content


Site collection
Site Collection

What: A grouping of sites in an hierarcky.

Why: To isolate and share common features, and customizations.

Think of: Condo association. Each condo is separate, but have common stuff.


Web app site col relations
Web App. / Site Col relations

Application Pool

Web Application:

http://MyCompanyIntranet.local

Site Collection

Root of web Application

http://MycompanyIntranet.local


Scenario 1 stick to the basics 1 1 1
Scenario 1 – Stick to the basics 1:1:1

Application Pool

Web Application:

http://MyCompanyIntranet.local

Site Collection

Root of web Application

http://MycompanyIntranet.local


Scenario 1 break down
Scenario 1 Break Down

= Sub Site

Root Site of Intranet

Departmental Sites

Dept. teams


Scenario 1 urls
Scenario 1 Urls

Root Intranet url:

Http://MyCompanyIntranet.local

Department Urls:

  • http://MyCompanyIntranet.local/Opps

  • http://MyCompanyIntranet.local/Sales

  • http://MyCompanyIntranet.local/IT


Scenario 1 pros cons
Scenario 1 Pros / Cons

Pros

  • Easy Administration

  • Auto Share Custom Element

  • Security Inheritance

  • Auto Contruction of Navigation

  • One Content Database

Cons

  • One Content Database = small size. < 50 gb

  • No Space quotas

  • Auto Share Custom Elements


Scenario 2 many site collections 1 1 many
Scenario 2 – Many Site Collections 1:1:Many

Web Application:

http://MyCompanyIntranet.local

Intranet Home

Sales

Operations

IT


Scenario 2 break down
Scenario 2 Break Down

Intranet Home

Sales

Operations

IT

Dept. Sites

Teams


Scenario 2 urls
Scenario 2 Urls

Root Intranet url:

Http://MyCompanyIntranet.local

Department Urls:

  • http://MyCompanyIntranet.local/Dept/Opps

  • http://MyCompanyIntranet.local/Dept/Sales

  • http://MyCompanyIntranet.local/Dept/IT


Scenario 2 pros cons
Scenario 2 Pros / Cons

Pros

  • Quota Limits

  • Separation of content

  • Can be in different DB’s

  • Scalable

Cons

  • Manual Site Navigation

  • Customizations need to be activated to each SC.

  • Defaults to 1 db


Multiple content databases
Multiple Content Databases

  • Tools:

    • Central Admin (Gui)

    • Stsadm –o CreateSiteInNewDB

    • Ben Curry - Creating and Managing SharePoint Content Databases



Conclusions
Conclusions

  • Physical Architecture:

    • Start with small farm so you can scale out.

    • Grow when you feel pain

  • Logical Architecture:

    • Small use with limited growth = One Site collection and Db

    • Large use and lots of growth = Multi Site collections and Dbs



Closing
Closing

  • http://NhGreatLakes.com

  • http://CharnockConsulting.wordpress.com

  • http://SharePointPodcast.com


ad