Oracle® Fusion Middleware Oracle WebCenter Analytics Administrator's Guide (for Oracle WebCenter Interaction) 10g Release 3 (10.3.0.1) Part Number E14112-02 |
|
|
View PDF |
This chapter provides information on using and analyzing Oracle WebCenter 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 Oracle WebCenter Analytics. For advanced tips and techniques on using Oracle WebCenter Analytics reports, see Tips and Techniques - Using Oracle WebCenter Analytics Reports.
The following table describes reports that are delivered with Oracle WebCenter Analytics.
Table 2-1 Descriptions of Oracle WebCenter Analytics Reports
Oracle WebCenter Analytics Report | Description |
---|---|
The Traffic console page displays metrics for many common events within the portal including community page views, My Pages views, search events, directory document views, Oracle WebCenter Collaboration document views, content items views and directory views. |
|
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. |
|
The Users console page displays counts of total, added, inactive and active users. Note: The Summary Metrics - Users report has been deprecated. You can continue to use the report in this release, but it will not be available in future releases. The Summary Metrics - Users report is disabled by default and can be enabled on the Runtime Settings page of the Analytics Administration Utility. 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. |
|
The Logins console page displays counts of logins into the portal, even if users have Remember my password selected on their home page, thereby logging them in automatically. The data can be summed by Logins (total logins into the portal) or Users (unique users who logged into the portal). |
|
The Duration console page shows the maximum and/or average duration of all portal visits. Note: The Summary Metrics - Duration report has been deprecated. You can continue to use the report in this release, but it will not be available in future releases. The Summary Metrics - Duration report is disabled by default and can be enabled on the Runtime Settings page of the Analytics Administration Utility. 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:
The Visit Timeout can be set in the Analytics Administration utility. For details, see Configuring Runtime Settings. |
|
The Community Traffic console page displays data for community page views. The report displays the most viewed communities (top communities), the least viewed communities (bottom communities), all communities (which is only available in tabular view) and selected communities. The report data can be viewed by Hits (page views), Visits (consecutive page views within a single community) and Users (unique users who viewed pages within the selected communities). |
|
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. Oracle WebCenter 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 Search console page tracks portal searches. 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. For each search phrase, click the Details link to view the names of the documents that were opened in the search results. |
|
The Documents console page tracks knowledge directory document views. Document views include documents opened from the directory and search results page. Additionally, document views include documents opened from snapshot and link portlets, and custom portlets that include gatewayed document links. The report displays the top documents viewed in the portal. Additionally, the report can be used to show the document views of all documents in a particular folder, or in a particular folder and its subfolders. |
|
The Projects console page displays metrics for Oracle WebCenter Collaboration. The metrics include document views, new documents and discussion posts. These three metrics can be used to report on the projects with the most traffic (top projects), projects with the least traffic (bottom projects), all projects (which is only available in tabular view) and selected projects. |
|
The Content Items console page tracks 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. |
|
The Ensemble Resources console page displays data regarding Oracle WebCenter Ensemble resource views. The report displays the most viewed resources (top resources), the least viewed resources (bottom resources), all resources (which is only available in tabular view) and selected resources. The report data can be viewed by Hits (resource views), Visits (consecutive views within a single resource) and Users (unique users who performed views within the selected resources). |
To access Oracle WebCenter Analytics reports:
Log in to the portal as an administrator.
Note:
If you are not an administrator, you must join the Analytics Console community in order to add it to your My Communities list.Choose My Communities > Analytics Console.
The Analytics Console appears.
Oracle WebCenter 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 Oracle WebCenter Analytics reports:
Manage administrative access to the Analytics Console and portlet templates.
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 Oracle WebCenter 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.
Manage user access to Oracle WebCenter Analytics portlets.
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.
Ensure that guest users are never allowed to add Oracle WebCenter Analytics portlets to their My Pages.
For information on creating administrative groups and managing user and guest access to portal objects, see Administrator Guide for Oracle WebCenter Interaction.
Note:
Users should not add many Oracle WebCenter Analytics portlets to a single My Page; each additional Oracle WebCenter Analytics portlet slows down performance. If users experience unacceptable performance or timeouts, you can recommend that they include fewer Oracle WebCenter Analytics portlets on each My Page.You can use the Oracle WebCenter Analytics portlet templates to create portlets that provide custom usage reports. For information on creating portlets from portlet templates, see Administrator Guide for Oracle WebCenter Interaction.
When you create portlets, be sure to consider security and privacy issues, described in Managing Security for Oracle WebCenter Analytics Reports.
This section provides advanced tips and techniques for using Oracle WebCenter Analytics reports and maximizing portal usage tracking.
The following table provides tips and techniques for how you can more effectively use Oracle WebCenter Analytics reports to track activity and improve the performance of your portal.
Table 2-2 Tips and Techniques - Using Oracle WebCenter Analytics Reports
Tip | Technique |
---|---|
Combining filtering and grouping lets you utilize Oracle WebCenter 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:
|
|
Analyzing reports that track community, project and portlet usage can help you to improve the performance of your portal. You can use Oracle WebCenter Analytics reports to:
|
The following table provides tips and techniques for what you can do within your portal to most effectively track usage.
Table 2-3 Tips and Techniques - Maximizing Usage Tracking
Tip | Technique |
---|---|
Configuring your portlets to contain gatewayed links only improves the accuracy of the Portlet Metrics - Usage report. |
|
Importing user properties makes Oracle WebCenter Analytics reports more powerful and compelling because you can cross-reference user profile data with tracked metrics. For example, if you import the Department and Region user properties, you can easily create reports such as Community Visits by Department and Logins by Region. For details on importing user profile information with profile Web services, see Administrator Guide for Oracle WebCenter Interaction. |