# Administrator Guide

# Working with Analytics Reports

This chapter provides information on using and analyzing Analytics reports, creating portlets, and configuring the portal for most favorable tracking. It includes the following topics:

- Overview of Analytics Reports
- Accessing Analytics Reports
- Tips and Techniques - Using Analytics Reports

## Overview of Analytics Reports

This section provides descriptions of the reports that are delivered with Analytics.

The following table describes reports that are delivered with Analytics.

Table 3-1 Descriptions of Analytics Reports
Analytics Report | Description
--- | ---
Summary Metrics - Traffic | The Traffic console page displays metrics for many common events within the portal including desktop views, page views, search events, and portlet views.
Summary Metrics - Pages | The Pages console page reports on portal page views. The report displays the most visited pages (top pages), the least visited pages (bottom pages), and all pages. The data can be summed by hits (total number of page views) or users (unique number of users who viewed pages). Additionally, the report can be filtered to show only pages from specific desktops.
Summary Metrics - Logins | The Logins console page displays counts of logins into the portal. The data can be summed by Logins (total logins into the portal) or Users (unique users who logged into the portal).
Summary Metrics - Duration | The Duration console page shows the maximum and/or average duration of all portal visits. A visit is defined as the time between a user's first click on any page within the portal and the same user's first click on a page outside of the portal, regardless of whether or not that user has logged in to the portal. Note that this report provides metrics for portal visits in general, not for specific web applications within the portal.
Desktop Metrics - Views | The Desktop Traffic console page displays data regarding desktop page views. The report displays the most viewed desktops (top desktops), the least viewed desktops (bottom desktops), all desktops (which is only available in tabular view) and selected desktops. The report data can be viewed by Hits (page views), Visits (consecutive page views within a single desktops) and Users (unique users who viewed pages within the selected desktops).
Desktop Metrics - Response Time | The Response Time console page displays the length of time that has elapsed from when the portal server receives a request for a desktop page until the time the response is sent to the user. Because the tracking is done on the portal server, the length of time it takes for the response to reach the user's machine and be displayed on the browser is not included in this metric. This report displays the desktops with the fastest response time (top desktops), the desktops with the slowest response time (bottom desktops), all desktops (which is only available in tabular view) and selected desktops. The report shows maximum, average and minimum response times.
Portlet Metrics - Views | The Portlet Views console page tracks the number of times a portlet is displayed within the portal. That is, each time a page is viewed, all of the portlets on that page are counted as being viewed. The report displays the most viewed portlets (top portlets), the least viewed portlets (bottom portlets), all portlets (which is only available in tabular view), selected portlets and portlets within selected desktops. The report data can be viewed by Views and Users (unique users who viewed the selected portlets).
Portlet Metrics - Response Time | The Response Time console page displays the time from when the portal sends a request for a portlet until the time the remote server responds with the portlet content. This report is important because typically a desktop page response equals the response of the slowest portlet on that page. For this reason, when troubleshooting slow desktops it is important to find the worst performing portlet. The amount of time it takes for the response to reach the user's machine and be displayed on the browser is not included in this metric because the tracking occurs on the portal server. This report displays the portlets with the fastest response time (top portlets), the portlets with the slowest response time (bottom portlets), all portlets (Note: This option is only available in tabular view), selected portlets and portlets within selected desktops. The report shows maximum, average or minimum response time.
Other Metrics - Search | The Search console page tracks portal searches. The report displays the top search terms.

## Accessing Analytics Reports

To access Analytics reports:

1. Navigate to WebLogic Portal Administration.
2. Under Configuration & Monitoring, choose Analytics.
   The Analytics application appears.
3. Click the Reports tab.

## Tips and Techniques - Using Analytics Reports

The following table provides tips and techniques for how you can more effectively use Analytics reports to track activity and improve the performance of your portal.

Table 3-2 Tips and Techniques - Using Analytics Reports
Tip | Tip
--- | ---
Tip #1: Combine filtering and grouping when viewing reports | Combining filtering and grouping lets you utilize Analytics reports in some powerful ways. For example, you can view a breakdown of sales force activity by city, determine the most active city, then view the departments that are making that city so active. The following example provides steps that you might perform to make these determinations in a similar report of your own: Filter the report by the Department user property, which contains the Sales property value. Group the report by the City user property. The report displays a breakdown of sales force activity by city. Determine the most active city in the report. Filter the report by the most active city. Group the report by the Department user property. The report displays the departments that are making that city so active.
Tip #2: Use the Analytics Console as a portal "clean up" tool | Analyzing reports that track desktop usage can help you to improve the performance of your portal. You can use Analytics reports to: Find the least-active desktops and portlets in your portal. Once you have done this, determine if these desktops and portlets are valuable. If they are not valuable, remove them from your portal. Find the desktops and portlets that have the slowest performance in your portal, and determine whether you should fix or remove these desktops or portlets from your portal; then take appropriate action.