IIS World Wide Web Publishing Service (W3SVC)
Applies To: Windows Server 2008
The Internet Information Services (IIS) World Wide Web Publishing Service (W3SVC), sometimes referred to as the WWW Service, manages the HTTP protocol and HTTP performance counters.
Managed Entities
The following is a list of the managed entities that are included in this managed entity:
| Name | Description |
|---|---|
An Internet Information Services (IIS) Web site is a unique collection of Web pages and Web applications that is hosted on an IIS Web server. Web sites have bindings that consist of a port number, an IP address, and an optional host name or names. |
|
Active Server Pages (ASP) enables Web servers to dynamically generate Web pages and create interactive Web applications by using server-side scripting technology. |
Aspects
The following is a list of all aspects that are part of this managed entity:
| Name | Description |
|---|---|
Internet Information Services (IIS) ISAPI (Internet Server Application Programming Interface) extensions and filters can extend and modify the request-processing capabilities of IIS. ISAPI filters require a long time to be written, offer no native support for session handling, and can be cumbersome to maintain. IIS 6.0 and IIS 7.0 run ISAPI applications in isolation to enhance server stability. While ISAPI filters can still be used in IIS 7.0, it is easier for developers to add managed or native modules that integrate into IIS 7.0’s new modular architecture. |
|
In order to perform its activities successfully, the Internet Information Services (IIS) World Wide Web Publishing Service (W3SVC) must be free of any I/O errors involving file access, memory availability, and network connections. In addition, any scripts that are used must be accessible and runnning, and any include files must be configured correctly. |
|
The Internet Information Services (IIS) World Wide Web Publishing Service (W3SVC) requires both the Windows Process Activation Service (WAS) and the HTTP service to function correctly. If the HTTP service is not available, W3SVC will not be able to process HTTP requests. |
|
The Internet Information Services (IIS) World Wide Web Publishing Service (W3SVC) can be configured to collect performance data and do HTTP compression. If the W3SVC is configured to perform HTTP compression, a valid compression directory that resides on an NTFS volume must be specified. |
|
An Internet Information Services (IIS) Web server can be configured for Site, Central Binary, or Central W3C logging. In Central W3C logging, all client requests for all sites are logged to a single log file in W3C centralized format on the server. Central Binary logging also logs all sites centrally to a single file, but does so in centralized binary format. In Site logging, all client requests are logged at the site level, not centrally at the server level. These logging types depend on the World Wide Web Publishing Service for their configuration. |
|
Internet Information Services (IIS) 7.0 enables developers to easily configure native and managed code modules that process requests made to the Web server. In order for worker processes to load them, the modules must be configured correctly. Proper module configuration requires that the module have a unique name, and a valid type or path. Managed modules can specify whether they should be invoked only for requests to ASP.NET applications or managed handlers. When specified, this setting can optimize performance. |
|
The Internet Information Services (IIS) World Wide Web Publishing Service (W3SVC) collects HTTP-specific performance counters for Web sites. The W3SVC initializes the counters and receives them from HTTP.sys, the protocol listener for HTTP. If W3SVC is not available, HTTP performance counter data cannot be gathered. |