Deploying And Installing Sharepoint Portal 2003
This document was uploaded by user and they confirmed that they have the permission to share it. If you are author or own the copyright of this book, please report to us by using this DMCA report form. Report DMCA
Overview
Download & View Deploying And Installing Sharepoint Portal 2003 as PDF for free.
More details
- Words: 1,183
- Pages: 23
Deploying and Installing SharePoint Portal 2003
Section Topics
Server Requirements Client Requirements Single Server Deployment Portal Components, Virtual Servers and Application Pools URL Namespaces Active Directory Integration
SPS/WSS Minimum Requirements
Microsoft Windows Server 2003, Any Edition Intel Pentium III–compatible processor 512 megabytes (MB) of random access memory (RAM) 550 MB free hard disk space NTFS
WSS/SPS Additional Service Requirements
Microsoft ASP.NET Enabled network COM+ access Microsoft Internet Information Services (IIS) with the following components:
Common Files Internet Information Services Manager World Wide Web Service
SQL Servers
SQL Server 2000 – Purpose:
Stores all user data – docs, lists, Webs, permissions, etc. Stores all config data and Web structure
SQL Recommendations:
Web Server
SP3 current minimums NT Authentication strongly recommended 4-10 content DBs / server: eases management Pre-allocate database size in SQL Server for performance Use SQL failover options for highest availability
SQL DB
WSS/SPS Infrastructure Considerations
Servers must be members of the same domain (except for single server installs which support local accounts) All servers in the farm must be the same language version of OS and SQL Server Should not install with SharePoint’s version of MSDE on DCs 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
Client Requirements
Hardware Requirements: Intel Pentium III–compatible 500 MHz processor 64 MB of RAM 50 MB hard disk space on Microsoft Windows 98 and Microsoft Windows NT 4.0; 30 MB disk space on Windows 2000 and Windows XP
Supported Operating Systems: Windows 98 and up Unix, Linux, and Mac OS X
Supported Browsers: Microsoft Internet Explorer 5.01, plus the latest service pack Internet Explorer 5.5, plus the latest service pack Internet Explorer 6.0, plus the latest service pack Netscape Navigator 6.2 or later (for Windows, Mac or Unix) Internet Explorer 5.2 for Mac OS X, plus the latest service pack
The disk can be formatted as NTFS, FAT, or FAT32.
Service Components of SharePoint
There are a total of five major service components on which SharePoint relies:
WSS Service Components:
Web server Database server
SPS Service Components:
Search server Index server Job server
Scaling Decision Factors
Throughput and availability are the two competing decision points Small to medium organization (< 10,000 users):
Single Server or Small Farm deployments Throughput generally not an issue
Custom Web parts can significantly change CPU/memory requirements
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”)
Physical Server Virtual Servers:
Used to host admin, portal, and team sites
Site Collections:
Portal Components
Many per vserver For example, http://svr/sites/mysite
Sites (a.k.a. sub webs):
Many per site collection For example, http://svr/sites/mysite/web
Virtual Servers
IIS’ virtual server is the same as SharePoint’s virtual server Granular control for sites Allows process isolation via application pools Top hosting element for site hierarchy
IIS Admin VServer End-User VServer Site Collection
Site
Portal Site
Site
IIS Configuration WSS Configuration
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
URL Namespaces
Domain named sites:
Folder named sites:
One per virtual server Corresponds to IP:PORT mapping Many per virtual server Corresponds to URL path Starts at a domain named site
Domain can be hosted by different servers Two URLs in the same domain cannot point to same site:
Can provide redirection Can host separate virtual server to resolve site
Managed Paths
Main functions:
Define which URL namespaces are managed by WSS (e.g. http://server/sites) Define paths used during self-service site creation (e.g. Restrict creation to http://server/usersites)
Excluded paths – WSS leaves alone (code cannot reference WSS) Included paths – WSS manages:
Explicit inclusion: only include the specific path set
Wildcard inclusion: e.g. http://server/usersites/* indicates that all sites below usersites are managed by WSS
Mapping URLs to Content http://machine/sites/mysite/lists/events/allitems.aspx
Web Server
Config DB
Server: ITG_STS_1 Database: STS_01
Lookup by server-relative site URL:
http://localhost and http://157.55.234.184 can work Two different virtual servers can serve same content
Content Database Lookup http://machine/sites/team56/lists/events/allitems.aspx
Virtual Server
Web Server
Config DB
List Content
Server: ITG_STS_1 Database: STS_01
Lookup by Server-Relative Site URL
http://localhost and http://157.55.234.184 work Two different virtual servers can serve same content
Lookup cached on Web server Everything is stored in SQL databases
Service Accounts Used by WSS/SPS
Install-time defined accounts:
Configuration database administration account Application pool account for virtual servers Portal site application pool identity Default content access account
Post-Install defined accounts:
Override account for crawling User profile import account Single sign-on service account Audience calculation job account
Portal Configuration Process
Configure indexing service account information and application pool identity Configure SQL connection settings Configure indexing service connection information including email account and proxy settings Configure portal components:
Web – provides http rendering services Index server – acts as indexing server to update content indices and crawl for new content Search – acts a server receiving and effectuating search requests using the indices built by the Index server Job – handles all scheduled jobs and administrative change requests to the portal
Create the Portal site:
Creates the top level portal site which will be used as the jumping point from which to access all content in the organization More portals can be created as required
Active Directory
Servers in a farm are in the same AD:
Exception (SQL server in SQL authentication mode can be standalone)
Users must be in trusted domain Portal profiles are based on users:
Can be imported from AD
Optional Services
HTML Transformation
Provides an engine for converting Office documents to HTML
“Compatible” library services
Provides a host service for Portal 2001 compatible libraries
Shared Services
Allows portals to share:
MySite definitions Indexing Audiences Alerts
Lab Key Points Configure Server Farm Account Specify Configuration Database Settings Configure server topology Create portal site Install an IFilter for Adobe PDF documents Configure user profile importing from Active directory Configure shared services
Section Topics
Server Requirements Client Requirements Single Server Deployment Portal Components, Virtual Servers and Application Pools URL Namespaces Active Directory Integration
SPS/WSS Minimum Requirements
Microsoft Windows Server 2003, Any Edition Intel Pentium III–compatible processor 512 megabytes (MB) of random access memory (RAM) 550 MB free hard disk space NTFS
WSS/SPS Additional Service Requirements
Microsoft ASP.NET Enabled network COM+ access Microsoft Internet Information Services (IIS) with the following components:
Common Files Internet Information Services Manager World Wide Web Service
SQL Servers
SQL Server 2000 – Purpose:
Stores all user data – docs, lists, Webs, permissions, etc. Stores all config data and Web structure
SQL Recommendations:
Web Server
SP3 current minimums NT Authentication strongly recommended 4-10 content DBs / server: eases management Pre-allocate database size in SQL Server for performance Use SQL failover options for highest availability
SQL DB
WSS/SPS Infrastructure Considerations
Servers must be members of the same domain (except for single server installs which support local accounts) All servers in the farm must be the same language version of OS and SQL Server Should not install with SharePoint’s version of MSDE on DCs 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
Client Requirements
Hardware Requirements: Intel Pentium III–compatible 500 MHz processor 64 MB of RAM 50 MB hard disk space on Microsoft Windows 98 and Microsoft Windows NT 4.0; 30 MB disk space on Windows 2000 and Windows XP
Supported Operating Systems: Windows 98 and up Unix, Linux, and Mac OS X
Supported Browsers: Microsoft Internet Explorer 5.01, plus the latest service pack Internet Explorer 5.5, plus the latest service pack Internet Explorer 6.0, plus the latest service pack Netscape Navigator 6.2 or later (for Windows, Mac or Unix) Internet Explorer 5.2 for Mac OS X, plus the latest service pack
The disk can be formatted as NTFS, FAT, or FAT32.
Service Components of SharePoint
There are a total of five major service components on which SharePoint relies:
WSS Service Components:
Web server Database server
SPS Service Components:
Search server Index server Job server
Scaling Decision Factors
Throughput and availability are the two competing decision points Small to medium organization (< 10,000 users):
Single Server or Small Farm deployments Throughput generally not an issue
Custom Web parts can significantly change CPU/memory requirements
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”)
Physical Server Virtual Servers:
Used to host admin, portal, and team sites
Site Collections:
Portal Components
Many per vserver For example, http://svr/sites/mysite
Sites (a.k.a. sub webs):
Many per site collection For example, http://svr/sites/mysite/web
Virtual Servers
IIS’ virtual server is the same as SharePoint’s virtual server Granular control for sites Allows process isolation via application pools Top hosting element for site hierarchy
IIS Admin VServer End-User VServer Site Collection
Site
Portal Site
Site
IIS Configuration WSS Configuration
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
URL Namespaces
Domain named sites:
Folder named sites:
One per virtual server Corresponds to IP:PORT mapping Many per virtual server Corresponds to URL path Starts at a domain named site
Domain can be hosted by different servers Two URLs in the same domain cannot point to same site:
Can provide redirection Can host separate virtual server to resolve site
Managed Paths
Main functions:
Define which URL namespaces are managed by WSS (e.g. http://server/sites) Define paths used during self-service site creation (e.g. Restrict creation to http://server/usersites)
Excluded paths – WSS leaves alone (code cannot reference WSS) Included paths – WSS manages:
Explicit inclusion: only include the specific path set
Wildcard inclusion: e.g. http://server/usersites/* indicates that all sites below usersites are managed by WSS
Mapping URLs to Content http://machine/sites/mysite/lists/events/allitems.aspx
Web Server
Config DB
Server: ITG_STS_1 Database: STS_01
Lookup by server-relative site URL:
http://localhost and http://157.55.234.184 can work Two different virtual servers can serve same content
Content Database Lookup http://machine/sites/team56/lists/events/allitems.aspx
Virtual Server
Web Server
Config DB
List Content
Server: ITG_STS_1 Database: STS_01
Lookup by Server-Relative Site URL
http://localhost and http://157.55.234.184 work Two different virtual servers can serve same content
Lookup cached on Web server Everything is stored in SQL databases
Service Accounts Used by WSS/SPS
Install-time defined accounts:
Configuration database administration account Application pool account for virtual servers Portal site application pool identity Default content access account
Post-Install defined accounts:
Override account for crawling User profile import account Single sign-on service account Audience calculation job account
Portal Configuration Process
Configure indexing service account information and application pool identity Configure SQL connection settings Configure indexing service connection information including email account and proxy settings Configure portal components:
Web – provides http rendering services Index server – acts as indexing server to update content indices and crawl for new content Search – acts a server receiving and effectuating search requests using the indices built by the Index server Job – handles all scheduled jobs and administrative change requests to the portal
Create the Portal site:
Creates the top level portal site which will be used as the jumping point from which to access all content in the organization More portals can be created as required
Active Directory
Servers in a farm are in the same AD:
Exception (SQL server in SQL authentication mode can be standalone)
Users must be in trusted domain Portal profiles are based on users:
Can be imported from AD
Optional Services
HTML Transformation
Provides an engine for converting Office documents to HTML
“Compatible” library services
Provides a host service for Portal 2001 compatible libraries
Shared Services
Allows portals to share:
MySite definitions Indexing Audiences Alerts
Lab Key Points Configure Server Farm Account Specify Configuration Database Settings Configure server topology Create portal site Install an IFilter for Adobe PDF documents Configure user profile importing from Active directory Configure shared services
Related Documents
Deploying And Installing Sharepoint Portal 2003
November 2019 9
Deploying Sharepoint Portal Server Across An Extranet
October 2019 9
Sharepoint Portal - Wss(tr)
November 2019 24
