Transcript Slide 1

Ryan Charnock
MCT @ New Horizons MI
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)
 Database Server (db)
 Application Server (app)
 Query Server (qu)

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
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
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
Single Server
 Small farm (farmet, Toy-farm)
 Large farm / scaled out

Single Server
WFE
Application
Srv
Database Srv
Small Farm
WFE
App
DB
Large Farm
WF
E
Fail Over
Cluster
APP
DB
WF
E
DB
WF
E
Logical Players
Application Pool
 Web Application
 Site Collection

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
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
Application Pool
Web Application:
http://mycompanyintran.local
Ntml – Window Authentication
Database - WSS_Content
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
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
Application Pool
Web Application:
http://MyCompanyIntranet.local
Site Collection
Root of web Application
http://MycompanyIntranet.local
Scenario 1 Break Down
= Sub
Site
Root Site of Intranet
Departmental Sites
Dept. teams
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
Pros
1. Easy Administration
2. Auto Share Custom
Element
3. Security Inheritance
4. Auto Contruction of
Navigation
5. One Content
Database
Cons
1. One Content
Database = small
size. < 50 gb
2. No Space quotas
3. Auto Share Custom
Elements
Scenario 2 – Many Site Collections
1:1:Many
Web Application:
http://MyCompanyIntranet.local
Intranet Home
Sales
Operations
IT
Scenario 2 Break Down
Intranet Home
Sales
Operations
Dept. Sites
Teams
IT
Scenario 2 Urls
Root Intranet url:
Http://MyCompanyIntranet.local
Department Urls:
 http://MyCompanyIntranet.local/Dept/Op
ps
 http://MyCompanyIntranet.local/Dept/Sal
es
 http://MyCompanyIntranet.local/Dept/IT
Scenario 2 Pros / Cons
Pros
1. Quota Limits
2. Separation of
content
3. Can be in different
DB’s
4. Scalable
Cons
1. Manual Site
Navigation
2. Customizations
need to be
activated to each
SC.
3. Defaults to 1 db
Multiple Content Databases

Tools:
 Central Admin (Gui)
 Stsadm –o CreateSiteInNewDB
 Ben Curry - Creating and Managing
SharePoint Content Databases
Demo
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
Questions
Closing
http://NhGreatLakes.com
 http://CharnockConsulting.wordpress.com
 http://SharePointPodcast.com
