|
M aintenance
1) Analyzing Web Site Usage
 If you want to know what kind of impact your Web site
has, you need to track how many users visit your site, the type and number of
hits your site receives, and other site-usage information. Microsoft Windows
SharePoint Services Beta 2 includes features that analyze the usage of your
site. Summary and detailed usage reports supply information such as:
· Number of
page hits for each individual page
· Number of
unique users
· Browser
and operating system information
· Referring
domains and URLs
Tracking usage information can be
useful for identifying which content on your site is being heavily used (and
therefore should be kept) and which content is not being heavily used (and may
be a candidate for archival). In addition to site usage statistics, you can also
keep track of how much storage space your site is taking up, and the level of
activity your site is generating. This information is gathered as part of the
quota tracking for sites. For more information about quotas, see
Configuring Site Quotas and Locks.
The usage reports rely on usage log data gathered from
the Web sites and stored in the content database for each virtual
server. The log data is a summary record of transactions on your Web site.
When you view a usage report in Windows SharePoint Services Beta 2 the data is
arranged into a list format. You must be a member of the administrator role
(or have the View Usage Data right) for a site in order to view
the site usage statistics.
You can view summary data about a site from the Site
Administration page.
View site usage summary data
1. On the site you want to view data for, click
Site Settings.
2. Under Administration, click Go to
Site Administration.
3. Under Management and Statistics,
click View site usage data.
You can view the usage data and quota settings for an
entire site collection at the same time. Note that this feature is not
available at the subsite level.
View usage data and quota information for a site
collection
1. On the top-level Web site of the site
collection, click Site Settings.
2. Under Administration, click Go to
Site Administration.
3. Under Site Collection Administration,
click View site collection usage summary.
You can also see detailed reports about storage and
user activity.
2) Using Monitoring Tools
This is a preliminary document. Additional information about this feature
will be provided prior to final commercial release.
Monitoring the Event Log
Using Query Logging
Monitoring Performance Counters
3) Monitoring Events for Windows SharePoint Services
Windows SharePoint Services Beta 2 has a decentralized
store of events. To monitor your server and keep it running in the best possible
state, you can monitor events and processes using the following tools:
· Windows
SharePoint Services Beta 2 event log
· Dr.
Watson logs
· Usage
analysis logs
· Windows
Application event log
· SQL
Server
· IIS
performance monitor and event logs
· OLEDB
logs
Monitoring the Windows SharePoint Services Beta 2 Event Log
The event log for Windows SharePoint Services Beta 2 is stored at (name?
path?). This log stores critical events for Windows SharePoint Services Beta 2,
such as ???. The data in this log file provides you with the best set of
indicators for determining how well your server is running and what to fix when
it isn't running as well as expected.
Monitoring Dr. Watson Logs for Windows SharePoint Services Beta 2
<description? name? path? I need to talk with MikeCook
about DW terminology>. If you don't want to use Dr. Watson to monitor Windows
SharePoint Services Beta 2, you can disable it by setting the following registry
key to 0: <TBD reg key goes here>. The log for Dr. Watson is queued, and can
hold up to 50 entries. The log does not automatically purge old entries - you
must delete old log entries manually to make room for new ones.
Microsoft does not collect any confidential data in Dr.
Watson logs - they are used primarily for finding stack information and
debugging issues. <Check with Mike on approved wording for this>.
Monitoring Usage Analysis Logs
Usage analysis data is stored in two logs: the log for Internet Information
Services (IIS), and the log for Windows SharePoint Services Beta 2. These two
data sets are complementary. The Windows SharePoint Services Beta 2 log tracks
page hits in document libraries and lists, while the IIS log tracks page hits
for structural and functional pages in the site, such as the Home page, the
Create page, or the site administration pages. The Windows SharePoint Services
Beta 2 log tells you which content in a site is generating the most interest or
is the most heavily used, and can be used in combination with quota data to see
if you have reasonable quota limits set for a particular site. The IIS log can
track who makes changes to a page, and how many times they made changes (for
example, which administrator account added a user on the Adduser.aspx page).
Monitoring the Windows Application Event Log
Monitoring SQL Server
You can monitor particular stored procedures by using the SQL Server Trace
tool. If you want to know how well your database is handling (issue a,b,c), it
is recommended that you monitor the following procedures: .
Monitoring the IIS Performance Monitor and Event Logs
Because Windows SharePoint Services Beta 2 relies on Internet Information
Services to run, you should also monitor the IIS performance monitors and event
logs to be sure that IIS is functioning properly. For more information, see the
IIS 6.0 Help system.
Monitoring OLEDB Logs
The OLEDB log can keep track of database connections that timed out.
4) Binding to a Document Library Event Handler
Windows SharePoint Services Beta 2 includes changes
that allow you to bind an event handler to a document library. With this
feature, you can use document library events to start other processes, such as
workflow processes. You can develop managed code that leverages document library
events and create an application based on Windows SharePoint Services Beta 2 to
perform whatever actions you need. When you combine document libraries, your own
event-handling managed code, and possibly XML forms, you can create even complex
workflow processes that are easy for users to work with.
For example, in the Healthcare industry, when a new
patient is admitted to a hospital, there is a lot of paperwork that needs to be
generated, and it needs to be done in a specific order. You can write an
application that interacts with XML forms in a document library to:
· Track
when a new admissions form is added to the document library.
· Extract
the insurance information and forward it to the billing application.
· Notify
the staff in the appropriate section of the hospital to pull the
patient's chart.
· And so
on.
The following events can be tracked for document libraries.
| Event |
Description |
| Insert |
A new document is
added to the document library. |
| Update |
An existing
document is edited. |
| Delete |
An existing
document is deleted. |
| Move |
A document is
moved or renamed. |
| Copy |
A document or
folder is copied. |
| Check In |
A document is
checked in. |
| Check Out |
A document is
checked out. |
| Cancel Check-Out |
Changes made to a
checked out document are undone. |
For more information about writing managed code to
interact with document library events, see the Windows SharePoint Services
Software Development Kit.
If you want to allow developers in your organization to
use the document library events to write code, you must enable this feature at
the virtual server level.
Enable document library events for a virtual server
1. Click Start, point to All Programs,
point to Administrative Tools, and then click SharePoint
Central Administration.
2. Under Virtual Server Configuration,
click Configure virtual server settings.
3. On the Virtual Server List page,
click the name of the virtual server you want to configure.
4. On the Virtual Server Settings page,
under Virtual Server Management, click Virtual server general
settings.
5. On the Virtual Server General Settings
page, in the Event Handlers section, next to Event handlers
are:, select On.
6. Click OK.
After the feature is enabled, you can write code to handle the events, and
then specify the code to use for a particular document library in the document
library settings.
Enable document library events for a specific document
library
1. On the appropriate Web site, navigate to the
document library you want to monitor.
2. Under Actions, click Modify
columns and settings.
3. Under General Settings, click
Change advanced settings.
4. In the Event Handler section, in the
Assembly name box, type the strong name of the assembly
containing the event handler class.
5. In the Class name box, type the full
class name for the event handler.
Note The Class name value is case-sensitive.
6. In the Properties box, list any
appropriate properties for the event handler.
7. Click OK.
Note Be aware that event settings are preserved when a document library
is saved as a list template. For more information about templates, see
Working with Templates.
5) Viewing and Deleting Diagnostic Logs
You can view and delete diagnostic logs.
View and delete diagnostic logs
1. On the SharePoint Portal Server Central
Administration for Server server_name page, in the Component
Configuration section, click Configure diagnostic tools.
2. On the Diagnostic tools for server
server_name page, in the View diagnostic logs section, in the
Diagnostic logs list, select a diagnostic log, and then do one of
the following:
o
To view the selected log, click View Log.
o
To delete the selected log, click Delete.
3. To delete all log files, click Delete All.
You cannot delete log files that are in use.
4. Click OK.
19/06/2003
| 
SharePoint
au
Quotidien
avec
EROL
