The Analytics Portlet Usage portlet reports the number of uses per portlet. A use is defined as any user activity that causes a request to the server, such as selecting a link or clicking a button. The following sections describe the attributes that you can set to customize the report.
Note: To enable readability, the graphic charts display a maximum of 25 data points, beginning with the first in time. For example, if you configure settings for a bar chart report for a duration of 3 days and group by hour, your request is for 72 data points; only the first 25 hours are displayed in the bar chart. To improve readability, labels do not always exist for all data points. In tabular reports, the report includes a maximum of 1000 data points. However, when you export data for the report to Excel, the report includes all data points.
These settings allow you to specify the display format and to select the portlets to appear in the report.
You can choose to display your report in the following formats:
Selection | Description |
Top Portlets | Displays the portlets that have been used most. You can specify that you want to display the top 5, 10, 15, or 20 portlets. |
Bottom Portlets | Displays the portlets that have been used least. You can specify that you want to display the bottom 5, 10, 15, or 20 portlets. Portlets with no uses are not included in this report. |
All Portlets | Displays all portlets. Only available in tabular view. |
Specify Portlets | Displays usage metrics for a specific portlet or multiple portlets. When you select this option, click Browse to choose the portlets you want to display. |
Specify Communities | Displays usage metrics for all portlets in a specific community or multiple communities. When you select this option, click Browse to choose the communities whose portlet usage metrics you want to display. |
Option | Description |
Activity | Displays the usage activity for the portlet(s) selected during the filtered time period. |
Users | Displays the unique users for the portlet(s) selected during the filtered time period. |
You can filter the report according to the following properties.
Filter Type | Description |
Date Range | Allows you to filter data based on a range of dates. If you select Specify Date Range, you can choose the start and end date. |
Authentication Source | Allows you to filter data based on the authentication source. |
User Property | Allows you to filter data based on the user properties defined in your portal. After selecting the desired property, select Contains or Does Not Contain and the property value by which you want to filter. |
If multiple portlets are selected, the data is automatically grouped by portlet name. In addition, you can group reported data according to the following attributes.
Property | Description |
Time Interval | This option groups the data by the selected time period. A line chart must have a time interval group by parameter selected. |
User Property | This option groups the data by the selected user property. Users are grouped by the property value in their user profile. |
Enter a title for the report display and specify whether to allow users to specify a custom date range.
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 the like.
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, Search, Document, Community, and Portlet reports can be configured to display activity metrics for a particular user, based on several user properties, such as Email Address, First Name, or Last Name.
To protect security and privacy interests before you roll-out Oracle WebCenter Analytics reports:
1. Manage administrative access to Analytics Console and portlet templates.
To ensure only a limited number of administrative users can add the Analytics Console community to their My Communities and create portlets based on the 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.
2. Manage non-administrative user access to Analytics Console data.
If you are allowing non-administrative users to add the Analytics Console to their My Communities, configure the console’s security accordingly in Analytics Administration. For more information, see Security Settings.
3. Manage user access to 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.
4. Ensure that guest users are never allowed to add Analytics portlets to their My Pages.
For information on creating portlets from portlet templates, see the Administrator Guide for BEA AquaLogic Interaction.
For information on creating administrative groups and managing user and guest access, see the Administrator Guide for BEA AquaLogic Interaction.