The portal now lets you quickly and easily generate reports on activity in the portal, either reports on how many users were logged on to the portal or reports on the most popular pages and iViews.
The portal includes an out-of-the-box iView template, called the Portal Activity Report iView, that you can add to any page or workset. You can then configure the iView (during design time) to display the exact information that you want.
The following shows the default Template Selection page for SP9, which is displayed after you specify that you want to create an iView:
After creating the iView, you open the following editor in order to configure the iView and display only the information you want:
You can configure the following settings:
- The time period to report on (a fixed time frame)
- The time interval (that is, whether to show how many users were logged on during each hour or each day or each week within the selected time period of the report)
- The type of report (that is, what information to display), either: (1) The number of users who logged on for a specific period; (2) The number of hits that were recorded for specific iViews and pages.
For reports that show you the number of hits for iViews and pages, you select the iViews and pages to be included in the report. This tyoe of report shows you only the total number of hits during the time period for the report, and does not break it down for each interval.
The following is an example of a portal activity report (this one shows the number of users who logged on during the selected period):
You can set up a variety of portal activity reports, each one for a different period of time or a different group of pages and iViews.
A setting in the portal activity service lets you indicate to the portal not to collect data on certain iViews and pages. For example, by default, no data is collected for the built-in navigation iViews.
In order to make the whole thing work, you must set up the portal mechanism for collecting the data to report. This mechanism has two parts:
- Data Collection Service: This service gathers raw data from the Portal Runtime (PRT) about processed pages, iViews, and the activities of logged on users.
- Aggregator Application: A stand-alone application that synchronizes and combines the collected data from all the nodes in the cluster.
This setup work is quick and easy (setting up the Data Collection Service may involve only changing a service parameter in the portal to true).
For more information on setting up Portal Activity Reports, see Portal Activity Report in the NetWeaver Administration Guide for the portal.
FUTURE PLANS: The capabilities of the Portal Activity Report are being expanded to include a report that shows which users logged on and how often. Additional settings enable you to see only the most active users, or only those users in a specified group.
Previous articles in this series: