16.01.2013 Views

Microsoft Sharepoint Products and Technologies Resource Kit eBook

Microsoft Sharepoint Products and Technologies Resource Kit eBook

Microsoft Sharepoint Products and Technologies Resource Kit eBook

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

246 Part III: Planning <strong>and</strong> Deployment<br />

Configuring the Log Files<br />

IIS logging is enabled by default for each virtual server. The recommended log file<br />

format is W3C, which is the default. This enables you to specify which fields are<br />

included in the log file. By limiting logging to the W3C fields that are most important<br />

to your customer, you can limit the log file size <strong>and</strong> simplify the analysis. Depending<br />

on the amount of traffic to your sites, the size of your log files can begin to consume<br />

valuable memory resources <strong>and</strong> CPU cycles. You need to balance the gathering of<br />

detailed data against the need to limit IIS log files to a manageable size <strong>and</strong> number.<br />

The following W3C log file fields are the most important for analyzing Web<br />

traffic for scale-out decisions:<br />

■ User name. The name of the user who accessed the server.<br />

■ Server IP address.<br />

generated.<br />

The IP address of the server on which the log entry was<br />

■ Server port. The port number to which the client is connected.<br />

■ Method. The action the client was trying to perform—for example, a GET request.<br />

■ URI stem. The resource accessed, such as an HTML page, a Common Gateway<br />

Interface (CGI) program, or a script (the most relevant resource for a scaling<br />

decision).<br />

■ URI query. The query, if any, the client was trying to perform. One or more<br />

search strings that the client was seeking to match are recorded.<br />

■ Protocol status. The status of the action, in HTTP terms.<br />

■ Protocol substatus. Records additional status of the action, in HTTP terms.<br />

■ Win32 status. The status of the action, in Windows operating system terms.<br />

More Info For a complete list of W3C log file fields, visit http://www<br />

.microsoft.com/technet/prodtechnol/windowsserver2003/proddocs/st<strong>and</strong>ard<br />

/log_customw3c.asp.<br />

Usage Analysis Processing<br />

Usage analysis processing provides usage reports on Windows SharePoint Services<br />

sites. This information can help you to determine which Windows SharePoint Services<br />

sites <strong>and</strong> subsites receive the most visitors.<br />

Usage analysis data is taken from the IIS logs on the front-end Web servers <strong>and</strong><br />

gathered into temporary files. When usage analysis processing takes place, the logs<br />

are merged into the content databases on the computer running SQL Server. For<br />

more information, see “Configuring Usage Analysis” in the online SharePoint Portal<br />

Server 2003 Administrator’s Guide.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!