Saturday, June 9, 2012

How to configure usage reporting in SharePoint ?

Before you enable usage reporting in a SSP, you have to first enable Windows SharePoint Services usage logging for the farm hosting the Web application containing the SSP.
Use the following procedure to enable usage logging for the farm.

Enable usage logging for the farm
1.      On the Central Administration home page, click Operations.
2.      On the Operations page, in the Logging and Reporting section, click Usage analysis processing.
3.      On the Usage Analysis Processing page, in the Logging Settings section, select Enable logging.
4.      Type a log file location and number of log files to create.
5.      In the Processing Settings section, select Enable usage analysis processing, and then select a time to run usage processing.
6.      Click OK.

Enable usage reporting
1        On the SSP home page, in the Office SharePoint Usage Reporting section, click Usage reporting.
2        On the Configure Advanced Usage Analysis Processing page, in the Processing Settings section, click Enable advanced usage analysis processing.
3        In the Search Query Logging section, select Enable search query logging.
4        Click OK.

Activate usage reporting
After usage reporting is enabled for the SSP, site collection administrators must activate the reporting feature. Until the reporting feature is activated on a site collection, usage reports are not available.
Use the following procedure to activate the reporting feature.

1        On the Site Actions menu, click Site Settings.
2        On the Site Settings page, in the Site Collection Administration section, click Site collection features.
3        On the Site Collection Features page, click the Activate button for the Reporting feature.

No comments:

Popular Posts


The opinions expressed on this blog are the personal views of Pratik's SharePoint Blog, and do not represent or reflect the viewpoints or policies of any past, present, or future employer, colleague, or customer, or any other entity. The posts on this blog are provided ‘as is’ with no warranties, express or implied, and confer no rights. Use of information contained within this blog, including specific technical steps mentioned herein, is at your own risk. References to specific software products, processes, resources, or companies do not imply any endorsement.