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.

Chapter 10: Performance Monitoring in <strong>Microsoft</strong> Office SharePoint Portal Server 2003 245<br />

Internet Information Services (IIS) Logs<br />

IIS logs include detailed information, such as who has visited sites <strong>and</strong> what was<br />

viewed, in terms of total visits, average visits, page views, <strong>and</strong> trends over time.<br />

Careful analysis of the IIS logging data helps you to discover how much traffic is<br />

going to portal sites, how much is going to Windows SharePoint Services sites, <strong>and</strong><br />

how much is going to search operations.<br />

You can use IIS log data to help identify bottlenecks <strong>and</strong> performance issues.<br />

More importantly, you can use this data to identify the SharePoint Portal Server <strong>and</strong><br />

Windows SharePoint Services sites that are used most often. This information helps<br />

you to underst<strong>and</strong> the impact of Windows SharePoint Services sites on your frontend<br />

Web server traffic <strong>and</strong> to decide when to move one or more site collections to<br />

a dedicated Windows SharePoint Services server farm.<br />

Setting Up Log Files<br />

Set the logs to be created on a daily basis, which creates a new log file each day for<br />

each virtual server.<br />

Set up SharePoint Portal Server to place the log files on a hard drive separate<br />

from the one that contains the operating system (drive C). Ensure that the local<br />

Administrators group <strong>and</strong> the IIS_WPG group have the appropriate permissions to<br />

access the log files directory.<br />

Within the Logfiles directory, IIS creates a separate directory for each IIS virtual<br />

server log, with naming based on the virtual server instance number.<br />

To view the directory <strong>and</strong> log file name for each virtual server through IIS Manager,<br />

follow these steps:<br />

1. Right-click a virtual server, click Properties, <strong>and</strong> then select the Properties<br />

button next to Active log format.<br />

2. The Log File name is displayed at the bottom of the screen.<br />

Reading the Log File Data<br />

The IIS logs are ASCII files that can be read using a text editor, but third-party utilities<br />

are typically used to analyze IIS logs <strong>and</strong> generate meaningful, formatted reports <strong>and</strong><br />

graphical representations of usage data. How the IIS logging information is presented<br />

<strong>and</strong> accessed depends on the third-party tool used to present the IIS log data. You can<br />

also use <strong>Microsoft</strong> Commerce Server Web Analytics to gain this information.<br />

IIS log files can also be logged in a database that complies with Open Database<br />

Connectivity (ODBC), such as a <strong>Microsoft</strong> SQL Server database, <strong>and</strong> SQL Server Query<br />

Analyzer can be used to generate reports. For more information about configuring<br />

IIS logs to an ODBC database, see “Log File Formats” at http://www.microsoft.com<br />

/technet/prodtechnol/windowsserver2003/proddocs/st<strong>and</strong>ard/log_aboutlogging.asp.

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

Saved successfully!

Ooh no, something went wrong!