Elczar Adame's Shared Points on SharePoint


 

WSS 3.0’s IIS 7.0 Role Services

 

In my preceding blog on WSS 3.0 in Windows Server® Code Name “Longhorn”, we have mentioned that installing WSS 3.0 role includes installation of Web Server (Internet Information Services 7.0) role and other features – e.g. .NET Framework 3.0, Windows Internal Database, and Windows Process Activation Service. As illustrated below, this is apparent during our installation.

 

Internet Information Services (IIS) 7.0 is the Web Server for Windows Server 2008. Not to mention that Windows Vista has also features depending on version, it provides all the features and services needed to host web applications. As compared to IIS 6.0, the Web server has been redesigned in IIS 7.0 with new components:

1.     A novel service, Windows Process Activation Service (WAS), which enables sites to use protocols other than HTTP and HTTPS. It manages application pool configuration and worker processes instead of WWW Service. Thus, we can run WAS without WWW Service if you do not need to listen for HTTP requests in HTTP.sys.

2.     A Web server engine that can be customized by adding or removing web server modules.

3.     Integration of request-processing pipelines from IIS and ASP.NET.

 

With its modular architecture, IIS 7.0 provides fundamental modules/role services for Windows SharePoint Services 3.0. It could be categorized as:

            1. Web Server

                        1.1. Common HTTP Features

                        1.2. Application Development

                        1.3. Health and Diagnostics

                        1.4. Security

                        1.5. Performance

            2. Management Tools

                        2.1. IIS Management Console

                        2.2. IIS 6.0 Management Compatibility

 

 

Common HTTP Features

Description

Static Content

Allows our WSS 3.0 web server to publish static web file formats.

Default Document

Allows configuration of the default page of our SharePoint site.

Directory Browsing

Allows browsing of the content of our SharePoint site directory. By default, it is disabled.

HTTP Errors

Since our SharePoint site is running in classic mode, custom errors apply only to non ASP.NET content.

           

Application Development

Description

ASP.NET

Provides a server-side object-oriented programming environment necessary of our SharePoint site. These are ASP.NET resources that are directly available to deliver for WSS 3.0 – e.g. Pages and Controls, Connection String, Providers, et al.

.NET Extensibility

Allows changes, additions, and extensions of web server functionality in the request pipeline, the configuration, and the user interface.

ISAPI Extensions

Supports dynamic web content development using Internet Server Application Programming Interface (ISAPI) extensions. For our SharePoint site, we have: aspnet_isapi.dll, author.dll, admin.dll, shtml.dll, and owssvr.dll.

ISAPI Filters

Gives support for web application that uses ISAPI filters. It is a program that enhances our WSS 3.0 server behavior. It receives every HTTP request made to our WSS 3.0 server to provide supplementary functionalities – e.g. logging request information, user authentication and authorization. Our SharePoint site, by default, implements aspnet_filter.dll.

 

Health and Diagnostics

Description

HTTP Logging

Grants logging of our SharePoint site activity. By default, it is logged at %SystemDrive%\inetpub\logs\LogFiles with W3C format. This is in addition of the usage event logging in Windows SharePoint Services 3.0 at \Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\Logs path.

Logging Tools

Provides infrastructure to manage our WSS 3.0 server logs and automate common logging tasks.

Request Monitor

Provides infrastructure to monitor our SharePoint site health. Thanks to the Runtime Status and Control API (RSCA).

Tracing

Provides infrastructure to diagnose and troubleshoot SharePoint site. With specificity to Failed Request Tracing, it disabled by default and configured to %SystemDrive%\inetpub\logs\FailedReqLogFiles directory with 50 maximum number of trace files.

 

Below is an illustration of the requests for the worker process.

 

 

Security

Description

Basic Authentication

Requires that users provide a valid user name and password to access our SharePoint site. It works across firewalls and proxy servers, but it transmits unencrypted base64-encoded passwords across the network.

Windows Authentication

Works only in an intranet environment. We can use the Windows domain security implementation already in place to authenticate client connections to our SharePoint site. It is our default authentication setting.

Forms Authentication

ASP.NET forms-based authentication works well for our SharePoint site on public web servers that receive numerous requests.

Request Filtering

With incorporation the core features of URLScan into a module called Request Filtering and additional feature called Hidden Segments, it screens all incoming requests based on configured rules – e.g. double-encoded requests filtering, high-bit-characters filtering, file extensions filtering, et al.

 

Below is an illustration of authentication feature view in IIS Manager.

 

 

Performance

Description

Static Content Compression

Provides infrastructure to configure HTTP compression on static content of SharePoint site. This is for effective bandwidth utilization, and to provide faster transmission times between IIS and compression-enabled browsers.

Dynamic Content Compression

Provides infrastructure to configure HTTP compression on static content of our SharePoint site.

 

Below is an illustration of compression feature view in IIS Manager.

 

 

Hoping to contribute something…Thanks…

 

 

Advertisements

Comments on: "WSS 3.0’s IIS 7.0 Role Services" (1)

  1. Thanks for this post! We are planning to migrate one of our WSS sites from IIS6 on W2003 to W2008 and IIS7 and your article is exactly what I have been looking for.
    Regards
    Carlo

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

Tag Cloud

%d bloggers like this: