Release Notes for Plumtree Analytics 1.2
Contents
Version History
Release Notes Overview
Common Components Container 1.5 HF208996
Issues Addressed
Post-Release Updates
Version 1.2 HF205842
Issues Addressed
Version 1.2
Supported Operating Systems, Application Servers, and Browsers
Supported Plumtree Products
Documentation
New Features
Issues Addressed
Known Issues
Post-Release Updates
Version History

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 Septemeber 2005, for Windows and Red Hat Linux

Release Notes Overview

These release notes cover all releases of Plumtree Analytics 1.2, including hotfixes and service packs. For information on a particular release, please go to the appropriate section of these release notes.

Release notes are occasionally updated after the release date. For the most up-to-date release notes, go to the Product Center at support.plumtree.com.

Common Components Container 1.5 HF208996 for All Operating Systems

It is recommended that this hotfix be applied to ALL servers running any of the following products:

- Plumtree Foundation 6.0 Content Upload Service
- Plumtree Foundation 6.0 API Service
- Plumtree Collaboration 4.1
- Plumtree Studio 2.1
- Plumtree Analytics 1.2
- Plumtree Identity Services - LDAP 2.1
- Plumtree Content Service - Documentum 5.4
- Plumtree Portlet Suite - Lotus Notes 3.2
- Plumtree Portlet Suite - IMAP 3.1
- Plumtree Publisher 6.2 is also affected but has a different resolution. Please see the release notes for Plumtree Publisher for more details.

Issues Addressed

- In multiple products, headers greater than 4KB in size result in requests being truncated, which can negatively impact the functionality of affected products. Headers may exceed 4KB due to large portlet preferences passed by the portal, third party headers, SSO tokens, or other causes. Unexpected error messages may be returned by the portal as a result. (Issue #48757)

Post-Release Updates

- Plumtree Logging Utilties daemon may not restart after installation of Common Components Container 1.5 HF208996. (Issue #50560)

  Workaround: This hotfix stops all Plumtree services residing on a server in order to complete the installation process. It then automatically starts all services residing on that server. Please ensure that the all of the services have been properly restarted.
- Common Components Container 1.5 HF208996 deployment log is in an unusual location. (Issue #50562)

  Workaround: The deployment log is located at $PT_HOME/uninstall/ptportal/6.0/register/hotfix1_deployment.log (Unix and Linux) and %PT_HOME%\uninstall\ptportal\6.0\register\hotfix1_deployment.log (Windows).

Version 1.2 HF205842

It is recommended that this hotfix be applied to all Plumtree Analytics 1.2 servers installed on Red Hat Linux. This fix is only applicable for the machine running the Analytics server component. The release notes file, Release_Notes_Plumtree_Analytics_1-2-HF205842.htm, is available in the Product Center, and includes complete instructions on how to install this hotfix.

Issues Addressed

- Analytics sync assumes that it is started from a certain directory since it uses relative path. (Issue 48255)
- When installing on RedHat Linux, the wrapper.conf file retains Windows-like paths and syntax for setting variables. (Issue #48418)
- The PATH variable does not include the '.' current directory. (Issue #48482)
- %APPLICATION_PATH% is quoted in the collectord_wrapper.conf. (Issue #48483)

Version 1.2

Supported Operating Systems, Application Servers, Databases, and Browsers

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

At the time of release, Plumtree Analytics 1.2 supports the following:

- Analytics 1.2 supports Windows 2003 SP1, Red Hat Enterprise Linux 3.0 update 3, Solaris 8 and 9, SUSE Linux 9, AIX 5.3
- Analytics 1.2 supports SQL Server 2000 SP3a^ and Oracle 9.2.0.4^ and 10.1.0.3^ in default or Oracle RAC configuration.
- Analytics 1.2 supports 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 Plumtree Products

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

At the time of release, Plumtree Analytics 1.2 supports the following:

- Plumtree Foundation G6 6.0
- Plumtree Collaboration 4.1
- Plumtree Publisher 6.2
- Plumtree Studio 2.1

Documentation

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

Document Title and File Name | Document Description
--- | ---
Attributions Analytics_Attributions.txt | Provides a list of third-party technologies used in the product, along with licensing information.
Installation and Upgrade Guide for the Plumtree Analytics 1.2 Installation_Guide_Plumtree_Analytics_v1-2.pdf | Describes how to install and upgrade the components of Plumtree Analytics 1.2.
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

- Plumtree Analytics now includes support for Red Hat Enterprise Linux w3.0 update 3, Solaris 8 and 9, SUSE Linux 9, AIX 5.3.
- Plumtree Analytics now includes support for Plumtree Foundation 6.0.
- Plumtree Analytics now includes support for Oracle 10g database.

Issues Addressed

Installation and Configuration

- Installing the Portal component of Analytics on a machine with the Portal running on Tomcat, without shutting down Tomcat, may cause some errors to occur and the install to fail. Portals running on Tomcat were not supported for version 1.0 of Analytics. (Issue #40578)

Miscellaneous

- A non-fatal error may appear in sync.log during a sync if a portal property value exceeds the maximum length of 900 bytes. (Issue #43115)
- When running db_creation.sql on Oracle you may notice the following error: CREATE INDEX UT_REPORT_REPORT_ID ON ut_report_info report_id) * ERROR at line 1: ORA-01408: such column list already indexed." This error can be ignored. (Issue #45310)

Known Issues

Installation and Configuration

- During Installation, no warning or error appears if invalid characters, such as / \:*?"<>| are entered in the Analytics directory field. (Issue #40394)
- After installing Analytics, a non-critical exception error "com.plumtree.openfoundation.util.XPIllegalArgumentException: Null input passed error" appears in the log file the first time the ptapi.war starts up. This error can be ignored. (Issue #41167)
- The Configurator log displays a non-critical "TimeGenerate- Cannot create time record" error. This error can be ignored. (Issue #41827)
- On the Collaboration page in the Configurator, some of the validation errors are not consistent with the actual problem. For example, entering a null values 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)
- On Step 5 of the Configurator, it mentions "Plumtree Collaboration Server 4.0.2 or above is installed in my portal environment." This release of Plumtree Analytics only supports Plumtree Collaboration 4.1. (Issue #48007)
- 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. Workaround: Use an "*" instead of an IP in the PortalAnalyticsConfig.xml (Issue #47818)
- The Uninstaller does not remove the sync cron job on UNIX based systems. (Issue #48788)
- The font is not set to display Japanese chars in the y axis of the analytics reports.
  Workaround: 1) Unpack the analytics.war file. 2) Open the AnalyticsUIParams.properties file for editing. 3) Add three entries for their locale, in this case ‘ja’, one for font name and one for font size. 4) Save and repackage war file.
  The entries would take the following form:
  localecode_font_osname=MyFont
  localecode_fontSize=14
  localecode_fontSmallSize=10
  where localcode is the result of the Java Locale.getLanguage() method, and osname is the result of the Java System.getProperty(""os.name"") method. (Issue #49450)"
- When loading the portal initially and browsing to the Analytics Console, an error is thrown and the Analytics_log file 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)

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)
- Sometimes, when editing an Analytic Server portlet, changes are not saved and the editor window is not dismissed when Finish is selected. Workaround: Close the browser window and start again. (Issue #41664)
- 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)
- In the administrator for the Portlet Users stand-alone portlet, multiple check boxes cannot be selected for the Line display. (Issue #41866)
- 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)
- In the administrator for the Portlet Response stand-alone portlet, it is possible to select multiple checkboxes for the bar display option. Also, it is possible 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)
- 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 user is also using the filter by user property feature. This results in the Analytics Server displaying the top 5 items instead of the number set in the template. (Issue #49098)

Event Handling

- In some cases, portlet usage counts, when filtered or grouped by user property are incorrect, 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 supported with version 1.2 of Analytics. (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 generate a Collab Document View Report, the Analytics Server 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)
- On the Community Traffic report, 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)

Miscellaneous

- 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)
- Reports with very large amounts of data may timeout. Changing the gateway timeout in the report web service to a higher value may solve this. (Issue #41499)
- 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)
- Multivalued user property values are not synced correctly in the ut_user_property_values table. Only the most recent value is synced and is overwritten when additional values are added. (Issue #49219)