SharePoint Products and

Technologies
Deployment Issues
 Single Server
Deployments
 All WSS components
on a single box
 Best for work group or
business unit
 Two types:
 Use SQL Server 2000
(a.k.a. “Single Server”)
 MSDE

(a.k.a. “Stand-alone”)
 Application Pools
 Three application pools will be created by
default:
1. DefaultWebSiteSPApp
2. CentralAdminAppPool
3. MSSharePointPortalAppPool
 Application pools are used for process
isolation and are associated to the virtual
servers hosting WSS/SPS
 Administrators have full control over how to
allocate and configure application pools
 Portal Performance
Factors
 Web page throughput
 Search throughput
 Index throughput
 Pages per user
 The Performance ‘Wild-Card’
Custom Web Parts
 Custom-built Web Parts may
dramatically increase the use of Web
server or SQL Server resources
 Recommendation: Test all custom Web
Parts carefully by using code profiling,
database profiling, and load simulation
before deploying to production servers.
 Single Server
Deployment
 Hardware
Capacity Example
 At least 1 GB of RAM

 At least 100 GB of available hard disk space

 A 2 GHz (minimum) Pentium 4 processor

 Above configuration will:

 Process 20 Web pages per second

 Process two search queries per second

 Index five documents per second

 Store more than 100,000 documents

 Include more than 1 million documents in indexes

 Host more than 10,000 team and personal sites

 WSS/SPS Infrastructure
Considerations
 Servers must be members of same domain (except for
single server installs which support local accounts)
 All servers in farm must be the same language version
of OS and SQL Server
 Should not install with SharePoint’s version of MSDE
on DC’s
 WSS/SPS supports multiple languages
 Each server in your server farm must include the

regional language options to support the languages

of all portal sites on that server
 All portal sites on the server farm must use the

same language. However, other sites, such as

SharePoint sites, can use different languages
 Scalable Service
Components of SharePoint
 There are a total of five major service
components SharePoint relies on:
 WSS Service Components

 Web server
 Database server
 SPS Service Components
 Search server
 Index server
 Job server
 Any of these services may be distributed
across many servers to achieve scalability
 Scale-out Decision
Points
 Throughput and availability are the 2 competing decision points
 Small to medium org ( < 10,000 users)
 Single Server or Small Farm deployments are sufficient
 Throughput generally not an issue
 Large org (10s of thousands of users)
 Throughput will require Small Farm or Medium Farm (3-5
servers)
 Largest orgs (100s of thousands of users)
 Throughput will require large farm (10-20 servers) or multiple
farms
 Share Services may also be appropriate
 Business structure may require shared services for SharePoint Portal
Server
 Custom web parts can significantly change CPU/memory
requirements
 Capacity, Throughput and
Availability Planning
 Increase capacity and throughput by
adding:
 Processors, RAM, and storage capacity to
existing servers (increases capacity only)
 Increase capacity and availability
 Web servers
 Computers running SQL Server
 Search servers
 Index servers