Refresher: Templates


Windows SharePoint Services uses number of templates to create site or site pages and can be applied to any site, page, web part page, lists, areas and quotas. By default, templates are stored in the Program Files\Common Files\Microsoft Shared\Web Server Extensions\60\templates directory on the local file system of the front-end Web server. The use of templates saves database space and increases performance in Windows SharePoint Services.

 

Saving Database Space

Windows SharePoint services does not store all the data about sites and pages in database but infect saves a row representing a site with the template of the site. When users changes the site the changes are stored in database. When user request the page again SharePoint services loads the page from template but load the changes from the database and shows to the user. This way Windows SharePoint Services saves database space

 

Increasing Performance

ASP.Net pages normally converted to DLL in web server. Templates have only one DLL associated with them but not for each site they represent which result if performance increase.

 

The Effects of Customization

Once a template page is changed. Windows SharePoint Services does not load the template from the table instead it saves the whole copy of the page to the page table.

 

 

 

 


 

Refresher: IIS Services Used by SharePoint Services


Windows SharePoint relies on specific software installed on the windows server 2003. Front-end web servers required IIS and ASP.Net and backend server required SQL Server 2000 or MSDE. SharePoint services uses the following services of IIS;

  • Virtual Servers
  • Application Pools
  • Authentication
  • ASP.Net

 

Virtual Servers

IIS uses virtual servers to give websites administrative, security, and resource boundaries. The default virtual server installed by IIS is named Default Web Site and is located at the c:\inetpub\wwwroot folder. Windows SharePoint Services uses virtual

servers provided by IIS to host its websites. We can many virtual server as per our requirements but we much keep in mind that each virtual server is assigned a specific set of memory so it can affect the server. Virtual server can be used to create site collection for organization with multiple departments.

 

Application Pools

Introduced as part of IIS 6. Each application pool is an isolated set of worker processes in which Web applications are run. This means that different application pools use separate processor and memory resources. An application pool is also a security boundary because each application pool requires its own set of credentials on the server. Windows SharePoint Services uses IIS application pools for handling resource allocation in its websites. Different virtual pools can share Application pools and we can create 9 application pools on server.

 

Authentication

IIS performs authentication to validate user accounts that try to access its Web services. Authentication works on a per-virtual-server basis in IIS and in Windows SharePoint Services. Windows SharePoint Services lets IIS handle authentication on

the front-end Web server—so much so that changes to authentication must occur in IIS administrative tools as well as in Windows SharePoint Services administrative tools. Authentication can be

  • Windows Integrated Authentication
  • Forms Authentication
  • Basic Authentication
  • SSL Authentication

ASP.NET

When IIS installs, it has only a minimum configuration and does not install many of the features that it includes. This is for security reasons. Because many Windows SharePoint Services components are built on ASP.NET, the Application Server component

for ASP.NET must also be installed in IIS before beginning an installation of Windows SharePoint Services.

Refresher: Installing and Configuring Windows SharePoint Services


Here a quick refresher about installation and configuration of Windows SharePoint services. To install windows SharePoint services the preparation of server required

  • Windows Server 2003 Standard or Enterprise Edition
  • IIS with ASP.Net and without Front page server extensions
  • SQL Server 2000 with Service pack 3 or later

Prepare the server by installing the software listed above and then follows these steps

Install Windows SharePoint Services

Install Windows SharePoint services without MSDE by selecting Server Farm during setup.

Create the administration virtual server and configuration database

You need to create the configuration database when you configure the first front-end Web server. For subsequent front-end servers, simply connect to the database

Create and extend a virtual server

You need to create virtual server to contain them in IIS. You can create multiple virtual servers with different IP addresses or host all your sites using the same IP address and virtual server.

Create sites

Finally create sites where you can also enable Self-Service Site Creation so that users can create their own sites.

Refresher: Installing SharePoint Services Version 2.0


Installing SharePoint Services is not a very simple decision. It involves planning. If you decide to deploy services you can install SharePoint services in one of the following scenarios.

  • Single Server Deployment

One servers with SharePoint Services 2003 and SQL Server 2003

  • Small Server Farm

Two servers with SharePoint Services or Front-End Web Server installed on one machine and SQL Server 2000 on 2nd machine

  • Medium Server Farm

Two or more server with SharePoint services or Front-End Web servers and two machines with SQL Server 2000 for content and Configuration databases