Windows SharePoint Services 3.0 Web application (Health model)
Applies To: Windows SharePoint Services 3.0
Topic Last Modified: 2008-04-27
A Web application is comprised of an Internet Information Services (IIS) site that has a unique application pool. When you create a new Web application, you also create a new database and define the authentication method used to connect to the database.
The following is a list of all aspects that are part of this managed entity:
Windows SharePoint Services 3.0 uses the authentication providers that are provided by Microsoft Windows Server 2008, such as Forms authentication or Web Single Sign-On authentication, to authenticate users. When using Kerberos v5 authentication, the service account used by the Internet Information Services (IIS) application pool for your Web application must be registered in Active Directory as a Service Principal Name (SPN) on the domain on which the front-end Web server is a member.
Windows SharePoint Services 3.0 uses SQL Server databases to store most of the content for the Web site and configuration settings. For example, all pages in the site, files in document libraries, files attached to lists, and information in lists are stored in the content database, and security and permission settings along with other configuration settings are stored in the configuration database in SQL Server.
Windows SharePoint Services 3.0 uses a service account to communicate with the database on behalf of a user request. This service account can be either a specific user name and password (domain name and password) or a predefined system account, such as Local System or Network Service. When a SQL Server database is created, a value for the maximum database size is set. Each database has a separate database size setting. Note that a Web application might be associated with one or many databases.
Windows SharePoint Services 3.0 enables you to bind an event handler to an event host (such as an entire site), a list, or a document library. For example, with this feature, you can use document library events to start other processes, such as workflow processes.
The Internet Information Services application pool that Windows SharePoint Services 3.0 uses runs as a service account when writing to a registry key or a file folder in the Windows file system.
Information Rights Management (IRM) allows content creators to assign rights to documents that they send to others. These documents are referred to as “rights-protected” documents. The data in rights-protected documents is encrypted so that it can be viewed only by authorized users. Furthermore, a rights-protected document stores an issuance license that specifies which rights users have to the content. For example, an author can specify the following rights for a document:
IRM relies on Windows Rights Management Services (RMS) to create the issuance license, and perform the encryption and decryption of rights-protected documents. When IRM is enabled on a list or library, Windows SharePoint Services 3.0 automatically adds the permissions that are assigned to an item to the issuance license of that item when that item is downloaded. This means that permissions that are set on documents in lists and libraries are enforced by IRM even after a document is downloaded from the site.
For more information about IRM and Windows SharePoint Services 3.0, see Deploying Active Directory Rights Management Services with Microsoft Office SharePoint Server 2007 Step-By-Step Guide (http://go.microsoft.com/fwlink/?LinkId=93136).
The second stage recycle bin contains all items that were deleted from the end-user recycle bins of all sites in a particular site collection. Farm administrators can configure quotas for the second stage recycle bin. When this quota is met, new items that are sent to the second stage recycle bin will cause the oldest content to be permanently deleted in order to make space for the more recently deleted content.
Several features of Microsoft Windows SharePoint Services 3.0 rely on scheduled background processes called timer jobs. Administrators can configure, schedule, and view the status of timer jobs by using Central Administration.
A Web Part can be registered as a safe control for use in Windows SharePoint Services 3.0. If an administrator removes the Web Part assembly that contains the Web Part from the front-end Web server, or marks the assembly as unsafe in the Web.config file for a particular server, the Web Part will no longer run, and the user will see an error message.