Release Notes for BEA AquaLogic Interaction Analytics 2.0
Contents
Version History
Release Notes Overview
Version 2.0
Supported Operating Systems, Application Servers, and Browsers
Supported BEA AquaLogic Interaction Products
Documentation
New Features
Issues Addressed
Known Issues
Version History

BEA AquaLogic Interaction Analytics 2.0 - released September 2006

Note: BEA AquaLogic Interaction Analytics is the updated product name for Plumtree Analytics.

Common Components Container 1.5 HF208996 - released January 2006

Plumtree Analytics 1.2 - released December 2005, for AIX, Solaris and SUSE Linux

Plumtree Analytics 1.2 HF205842 - released November 2005

Plumtree Analytics 1.2 - released September 2005, for Windows and Red Hat Linux

Plumtree Analytics Server 1.1 HF205447 - released November 2005

Plumtree Analytics Server 1.1 - released June 2005

Plumtree Analytics Server 1.0 - released March 2005

Release Notes Overview

These release notes cover only the BEA AquaLogic Interaction Analytics 2.0 release.

Release notes are occasionally updated after the release date. For information on a particular release, and for the most up-to-date release notes, go to the Product Center at support.plumtree.com.

Supported Operating Systems, Application Servers, Databases, and Browsers for 2.0

Refer to the Interoperability page of the Product Center in BEA Support Center at support.plumtree.com for the latest information on supported operating systems, application servers, and browsers.

At the time of release, BEA AquaLogic Interaction Analytics 2.0 supports the following:

- Windows 2000 and 2003 SP1, Red Hat Enterprise Linux 3.0 update 3, Solaris 8 and 9, SUSE Linux 9, AIX 5.3
- SQL Server 2000 SP3a^ and Oracle 9.2.0.4^ and 10.1.0.3^ in default or Oracle RAC configuration
- IE 5.5, 6.0^, Netscape 7.1, 7.2^, Firefox 1.0^

Note: The ^ sign means service packs with a version number greater than the listed version are also supported. For instance, Oracle 9.2.0.4^ means service packs including 9.2.0.5, 9.2.0.6 and 9.2.0.7 are also supported.

Supported BEA AquaLogic Products

Refer to the Interoperability page in the Product Center at support.plumtree.com for the latest information on supported BEA AquaLogic products.

At the time of release, BEA AquaLogic Interaction Analytics 2.0 supports the following:

- BEA AquaLogic Interaction 6.0 SP1, 5.0.5, 5.0.5J
- BEA AquaLogic Interaction Collaboration 4.1 SP2, 4.1 SP1, 4.1, 4.0.2
- BEA AquaLogic Interaction Publisher 6.2 SP1, 6.2, 6.1
- BEA AquaLogic Interaction Studio 2.1, 2.0.4, 2.0.3

Documentation

The product distribution includes the following documents in the Documentation folder.

Document Title and File Name | Document Description
--- | ---
Attributions AnalyticsAttributions.txt | Attributions files provide a list of other technologies used in the product, along with licensing information.
Installation and Upgrade Guide for the BEA AquaLogic Interaction Analytics 2.0 Installation_Guide_BEA_AquaLogic_Interaction_Analytics_v2-0.pdf | Describes how to install and upgrade the components of BEA AquaLogic Interaction Analytics 2.0.
Analytics Installation and Configuration Worksheets Analytics_Installation_and_Configuration_Worksheets.pdf | This document contains worksheets for entering the installation and configuration information required by BEA AquaLogic Interaction Analytics 2.0.
Administrator Guide for BEA AquaLogic Interaction Analytics 2.0 Administrator_Guide_BEA_AquaLogic_Interaction_Analytics_v2.0.pdf | Describes how to perform administration tasks for BEA AquaLogic Interaction Analytics 2.0.
Database Schema for BEA AquaLogic Interaction Analytics 2.0 Database_Schema_BEA_AqauLogic_Interaction_Analytics_v2.0.pdf | Describes all tables that are delivered with BEA AquaLogic Interaction Analytics 2.0.
| Online Help To access online help, click the Help icon in the Analytics Console or within the Administration Preferences of portlets created from the Analytics Portlet Templates. | The online help describes the attributes available to customize the content and format of each report and portlet.

New Features

- BEA AquaLogic Interaction Analytics now includes a remote API for extending Analytics tracking and reporting functionality.
- BEA AquaLogic Interaction Analytics now includes information security at the user level.
- BEA AquaLogic Interaction Analytics now includes support for database data partitioning.
- BEA AquaLogic Interaction Analytics now includes AquaLogic Interaction Publisher reporting.
- BEA AquaLogic Interaction Analytics now includes AquaLogic Interaction page traffic reporting.
- BEA AquaLogic Interaction Analytics now includes extended search reporting.

Issues Addressed

- On the Collaboration page in the Configurator, some of the validation errors are not consistent with the actual problem. For example, entering a null value in a field results in "The database information provided could not be validated. Check the information entered and try again" instead of "Validation Error: Value is required". (Issue #44251)
- In the event of a database failure when Analytics is installed on an Oracle 10g RAC environment, both of the Analytics services will need to be restarted. (Issue #47768)
- On a Windows installation of Analytics on the same machine as the Portal Server, data collection is not working. (Issue #47818)
- Sometimes, when editing an Analytics portlet, changes are not saved and the editor window is not dismissed when the Finish button is clicked. (Issue #41664)
- In the administrator for the Portlet Users stand-alone portlet, multiple check boxes cannot be selected for the Line display. (Issue #41866)
- In the administrator for the Portlet Response stand-alone portlet, users should not be able to select multiple checkboxes for the bar display option. Also, users should not be able to save the portlet without selecting any checkbox. (Issue #44893)
- In the Portal Users report, filtering and grouping by user property at the same time yields no data, even if there is data. (Issue #45314)
- Multiple portlets with the same name may generate incorrect results if they are on the same page within the portal. The results appearing on the Analytics report, for the portlets with the same name, may not be correct. (Issue #41759)
- The sync does not update a portal user property, on Analytics, if it has been edited. The edited property appears as if it's a new one. (Issue #43546)

Known Issues

Installation and Configuration

- The Configurator does not start automatically after running the Analytics silent installer. (Issue #53002)
- The Uninstaller does not uninstall the Analytics Jobs component files. (Issue #53007)
- When upgrading Analytics, the Analytics services are not shut down. The user has to manually shut down the services before the upgrade. (Issue #53548)
- In the Configurator for the Portal Settings, the checkbox for the Portal version only indicates 5.0.4J but should also be checked if using Portal version 5.0.5J. (Issue #53975)

Administration and Data Partitioning

- When loading the portal initially and browsing to the Analytics Console, an error is thrown and the Analytics_log.<date>.txt file (where <date> is the date when the file was written) shows the exception '2005-10-13 11:19:03 ApplicationDispatcher[/analytics] Servlet.service() for servlet jsp threw exception java.lang.NoClassDefFoundError: '. These errors can be ignored. (Issue #48621)
- You may see the following message in analyticsui.log: WARN HtmlGridRendererBase - PanelGrid reportForm307:tabularData:_id39 has not enough children. Child count should be a multiple of the columns attribute. This message is not fatal and can be ignored. (Issue #52812)
- The events list on the Event Registration page will display identical names since the spacing is not taken into consideration. For example, if 'Test 1' is created as one event and 'Test 1' is created as another event, both events will display as 'Test 1' in the events list. However, the database will correctly show the spaces in the display name. (Issue #52846)
- If a partitioned table currently in the view is removed, an administrator must go into Analytics Administration and click Finish in order to see data in the report (this will update the view). (Issue #53159)
- Event Registration cannot be completed if a newly-created dimension is removed from the event parameter which uses it. (Issue #53182)
- The following error may appear in the analyticsui.log: ERROR TabularMultipleSearchDataProvider - Exception occurred while trying to determine drillDownRow. This error is not fatal and can be ignored. (Issue #53250)
- If the "View Portal Document Related Data" option is disabled for a role within the Security Settings, the user will still be able to see the Document report options in the Analytics Console until they log off and their session is cleared. (Issue #53432)
- During initial creation of an Event, removing Parameters from the Event will throw a 500 error if the Event was not saved first. A workaround is to first save the Event before adding Parameters. (Issue #53781)
- Can't register new event with property called "date" when using an Oracle database. A workaround is not to use Oracle reserved words. (Issue #54232)

Report UI

- Time periods yielding no data are not displayed in any of the Analytics reports except for Summary Metrics - Users. For example, on the Community Traffic report, if the user filters by "last week", but there are only community traffic hits for Tuesday and Friday, the report will only display data for Tuesday and Friday for the selected community. (Issue #40035)
- In the Analytics Console Community, sometimes the console refreshes and resets to the default report settings, which clears the current report in view. (Issue #40341)
- In bar reports that have long names in the legend, the leftmost name gets truncated. (Issue #41406)
- Very long object names (such as community, portlet, auth source, etc) may push the report off the screen while displaying the entire object name. (Issue #41600)
- When viewing line reports grouped by week on systems with Monday as the first day of the week, the data points on the line chart are not aligned with the dates on the X-axis. Workaround: View the data in bar, tabular or pie form or export the data. (Issue #41834)
- An underscore (_) cannot be entered in the filter by User Property entry box. (Issue #41543)
- In the Portal Users report, the inactive/active users appear as inactive/active for the entire day, regardless of change of status within the day. This can be seen when the report is grouped by hour. (Issue #41568)
- For Line view, when Filter by This Week and Group by Week there is no text on the time axis describing the week for a single data point. (Issue #41511)
- For portlet templates, it is possible to configure a portlet without any view options (i.e. views, users). (Issue #48535)
- In Portlet Templates, the value set for top number of items to show may not be used if the user is also using the filter by user property feature. This results in Analytics displaying the top 5 items instead of the number set in the template. (Issue #49098)
- In the choose project popup window of the Projects report, the personal project is displayed with its project ID and not the personal project's name. (Issue #52486)
- In the Content Items stand-alone portlet, no radio button is selected by default when "select folder" is chosen. A folder option must be selected in order to use the "select folder" option. (Issue #52912)
- On the Portlet Usage/View/Response Time reports, when the "select portlets" option is used, the Portlet Selection window does not display portlets that exist within Community Folders. (Issue #52939)
- On the Search report for a 6.0 portal, the document view details always return all document views for that search regardless of your filter criteria. (Issue #53422)
- On the exported Portal Visit Duration report, the column header becomes "Not Available" when a bar or line report is selected. (Issue #53490)
- On the line view of the Portal Users report, although the user property dropdown is disabled, if there's a value showing from the previous report, the report displays an error "Grouping by User Property is not permitted in this line report." A workaround is to unselect the user property by using tabular view then proceed to line view. (Issue #53538)
- In the Portal Traffic report, the grouping dropdowns are enabled upon loading the report options. Grouping will be ignored if selected for pie report. Any change to the display or time settings will correctly disable the grouping dropdown for pie. (Issue #53539)
- In the Portal Users report line view, the grouping by error message incorrectly says user must group by time OR user property. Grouping by User Property is not allowed for the line view. (Issue #53543)
- In the Choose Project popup window of the Projects report, an HTTP Status 500 error may be displayed after clicking OK due to a timing issue. This only occurs when using IE. (Issue #53700)
- In the Choose Project popup window of the Projects report, any previous projects will no longer appear selected in the dialog; however, those selections still exist. (Issue #53705)
- The Search report after upgrade shows all previous search metrics as 0% abandoned. (Issue #53737)
- In the Search report, when the returned results are in multiples of 20, clicking last page button (>|) on the table control results in a page having a blank view. This could also show up in the Document Views report. (Issue #53738)
- The title is missing from the exported version of the Page Views report. (Issue #53743)
- When exporting user details in the Content Items report, the report is blank when the top level of "Count by Subfolder" is queried. A workaround is to select a subset of the subfolders that fall under the top-level folder. (Issue #53847)
- Document and Content Item Views reports return zero results on ORACLE when there are more than 1000 subfolders selected. A workaround is to break up the report into smaller sections selecting less than 1000 subfolders. (Issue #53895)
- When re-editing the Community Traffic Response Time Portlet Template Preferences from "THIS COMMNUNITY" to "TOP COMMUNITIES" or "BOTTOM COMMUNITIES" or vice versa in one session, the dialog will be unresponsive. A workaround is to close the dialog and re-edit the preferences (Issue #53899)
- In a stand-alone portlet for Page View, there is no error handling when grouping by time and user property. (Issue #53935)
- Editing a role name within the Analytics Administrator - Security Settings throws a 500 error if using UNIX or Linux with Oracle. A workaround is to create a new role with the desired name and delete the existing role. (Issue #54025)
- When selecting Count by Subfolder and specifying a folder in the Other Metrics – Content Items report, the Line report shows the message "No data to display". A workaround is to use another display type: Tabular, Pie or Bar. (Issue #54152)
- Line reports for Projects, Community and Portlet reports do not display the correct data; the graphs are correct but the legend and names don't match the data. A workaround is to view the data with another display type: Tabular, Pie or Bar. (Issue #54159)

Event Handling

- In some cases, portlet usage counts are correct when filtered or grouped by user property, although the aggregate count is correct. The portal keeps the gatewayed URL cached and registers the user ID as the last cached user. Once it is rendered, it picks up the new user ID. To track exact portlet metrics, a workaround is to set the portlet's web service cache to zero. (Issue #40166)
- A login event is tracked with each browser window opened in Firefox and Netscape when auto-login is enabled. (Issue #40446)
- Portlet Usage events for gatewayed portlets are not recording cached portlet uses on the browser. To track those particular portlets, set the http headers to return "no-cache". Please visit this URL for the http header specification protocol: http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html (Issue #40828)
- Searches within Collaboration projects or Publisher Explorer are not collected. (Issue #40579)
- Clicking on a Collaboration project pop-up window will generate a portlet usage event under the portlet which opened the project. (Issue #40957)
- Document View events for copies of Knowledge Directory documents are tracked under the original document. This is evident when using the "include subfolders" feature to generate the Document View report. (Issue #40983)
- Broken images still get counted as portlet use events. (Issue #41666)
- Document view events from within Collaboration projects are not getting captured when viewed through the WebEdit utility. (Issue #43429)
- Not all Collaboration document view events are captured when clicked upon through search results. (Issue #43981)
- If you do a search on a Studio record lookup portlet the use does not get counted in portlet metrics. In order for a portlet use to get registered, you must actually click on one of the search results in the pop-up results window or refresh it. (Issue #46632)
- If a portlet has a gatewayed link to a CSS or JS file, that link is counted as a portlet use. (Issue #47856)
- When uploading a Web Document (such as HTML) with the images, and then generating a Collaboration Document View report, Analytics may have multiple CDV events in the Console. (Issue #49162)
- Autorefresh page views are included in the counts, but should be ignored. (Issue #49639)

Internationalization

- The number format in reports does not follow the user locale settings. (Issue #41040)
- If the strings extracted from the portal database during the sync job contain Asian characters, and the user's locale is non-Asian, the Asian characters are not correctly displayed in the report. (Issue #41750)
- Some European locales display the wrong date format of mm/dd/yyyy instead of dd/mm/yyyy on the report UI. (Issue #44639)
- With the Community Traffic report's line and bar formats, the title is cut off in the Y axis on the French UI. (Issue #47057)
- In an exported Excel file, the time format follows the remote server's system locale instead of the client's locale. (Issue #47883)
- The font is not set to display Japanese characters in the y axis of the analytics reports. Workaround:
  1. Unpack the analytics.war file.
  2. Open the AnalyticsUIParams.properties file for editing. You can find this file in the analyticsui.jar file.
  3. Add these locale entries:
  <LocaleCode>_font_<OSName>=<LocalFont>
  <LocaleCode>_fontSize=14
  <LocaleCode>_fontSmallSize=10
  4. Save and repackage .war file.
  The locale entries should include these values:
  • The appropriate two letter language code
  • Your operating system: Windows, Solaris, or Linux
  • The name of the font that is appropriate to your locale and platform
  Windows example:
  ja_font_Windows=MS PGothic
  ja_fontSize=14
  ja_fontSmallSize=10
  (Issue #49450)
- Export User Details - US English date format is incorrect when using non-English server (Issue #52347)
- When creating a role in Security Settings, localized group names are displayed, but English names are displayed after it is saved. (Issue #52954)
- The portal side Configurator changes the UI language depending on the OS language, but the remote side Configurator always shows English (EN) UI. (Issue #53515)

Miscellaneous

- Reports with very large amounts of data may time out. Changing the gateway timeout in the report Web service to a higher value may solve this. (Issue #41499)
- Multi-valued user property values are not synched correctly in the ASDIM_USERPROPERTYVALUES table. Only the most recent value is synched and is overwritten when additional values are added. (Issue #49219)