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:
This section provides descriptions of the reports that are delivered with Analytics. For advanced tips and techniques on using Analytics reports, see Tips and Techniques - Using Analytics Reports.
The following table describes reports that are delivered with Analytics.
The Pages console page aggregates My Pages and community page views. The report displays the most visited pages (top pages), the least visited pages (bottom pages), the top entry pages and the top exit pages for the portal.
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 communities. Finally, if My Page views are included in the report they are summarized so that every user's My Pages are counted as one page.
|
|||
An inactive user is someone who has not logged in to the portal for a period that exceeds the active user timeout setting that you specify on the Runtime Settings page. An active user is someone who has logged in to the portal for a period of time that is within the active user timeout setting. For details on the Active User Timeout setting, see Configuring Runtime Settings.
|
|||
A portal visit starts when a user logs into the portal and ends when the user either logs out, logs in again or the Visit Timeout expires. The Visit Timeout is used instead of a session timeout because:
For instance, it is safe to assume that the user is no longer “using” the portal after 3 minutes of inactivity. For this reason, a new visit will be tracked the next time that the user clicks on a link in the portal or refreshes the page.
The Visit Timeout can be set in the Analytics Administration utility. For details, see Configuring Runtime Settings.
|
|||
The Response Time console page displays the length of time that has elapsed from when the portal server receives a request for a community 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 communities with the fastest response time (top communities), the communities with the slowest response time (bottom communities), all communities (which is only available in tabular view) and selected communities. The report shows maximum, average and minimum response times.
|
|||
The Portlet Usage console page displays data about clicks within portlets. Analytics tracks user clicks on a gatewayed button or link within portlets.
The report displays the most used portlets (top portlets), the least used portlets (bottom portlets), all portlets (which is only available in tabular view), selected portlets and portlets within selected communities. The report data can be viewed by Activity (portlet clicks) and Users (unique users who used the selected portlets).
|
|||
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 communities. The report data can be viewed by Views and Users (unique users who viewed the selected portlets).
|
|||
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 community page response equals the response of the slowest portlet on that page. For this reason, when troubleshooting slow communities it is important to find the portlet with the slowest performance. 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 communities. The report shows maximum, average or minimum response time.
|
|||
The report displays the top search terms. Additionally, for each search term the report displays the number of times the search was performed and abandoned. An abandoned search means that the user did not select any of the search results. Also, for each search term the report displays the documents that the user clicked on. Finally, the report can display searches that returned zero results.
|
|||
The Content Items console page tracks AquaLogic Interaction Publisher content item views. A content item view refers to each time a user views a published content item from within a Publisher portlet.
The report displays the most viewed content items (top content items) and the least viewed content items (bottom content items). Additionally, the report can display content item views within a folder or within a folder and its subfolders. Finally, the report can group content item views by Publisher Explorer folders.
|
|||
Analytics reports are intended to make usage metrics visible to a limited set of administrative users who perform particular business functions, such as capacity planning, QoS analysis, ROI analysis, “best bet” customization for Search, and so on.
The Analytics Console and portlet reports contain usage data that is valuable for enterprise portal analysis but might be regarded as private or sensitive to portal users. For example, the Search, Document, Community, and Portlet reports can be configured to display activity metrics for a particular user, based on several user properties such as E-mail Address, First Name, or Last Name.
To protect security and privacy interests before you roll out Analytics reports:
To ensure that only a limited number of administrative users can add the Analytics Console community to their My Communities or create portlets based on Analytics portlet templates, create a new administrative group and manage group membership accordingly. Members of this administrative group require Read access to the Analytics Console community and Select access to the Admin Objects directory that contains the portlet templates.
When you create portlets, configure metrics that do not contain private or sensitive data unless such a view is particularly intended. If the metrics in the report do contain private or sensitive data, configure security so that only appropriate, specified users have Select access and can therefore add the portlet to their My Pages.
For information on creating administrative groups and managing user and guest access to portal objects, see Administrator Guide for BEA AquaLogic Interaction.
Note: | Users should not add many Analytics portlets to a single My Page; each additional Analytics portlet slows down performance. If users experience unacceptable performance or timeouts, you can recommend that they include fewer Analytics portlets on each My Page. |
You can use the Analytics portlet templates to create portlets that provide custom usage reports. For information on creating portlets from portlet templates, see Administrator Guide for BEA AquaLogic Interaction.
When you create portlets, be sure to consider security and privacy issues, described in Managing Security for Analytics Reports.
This section provides advanced tips and techniques for using Analytics reports and maximizing portal usage tracking.
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.
The following table provides tips and techniques for what you can do within your portal to most effectively track usage.