Release Notes for Plumtree Publisher 6.2

These release notes cover all releases of Plumtree Publisher 6.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 Oracle Technology Network.

Version 6.2 Patch 1

Issues Addressed

Publisher Explorer can be accessed by a guest user with the same privileges as an administrator if the session is not properly terminated. (Issue #69473)
Workflow can be detached from a folder by a guest user if the portal URL with a session ID is compromised, even if the 'Cancel' button is clicked. (Issue #69552)
The Content Item Editor can be re-invoked if the URL is saved, even after a user has logged out of the portal. (Issue #69566)
The Publish to Directory Editor can be accessed by an unauthenticated user. (Issue #69567)
The Content Security Editor can be accessed by an unauthenticated user if the window is closed using the browser's 'x' button instead of the 'Cancel' or 'Finish' buttons. (Issue #69568)
The 'Items per page' Editor can be accessed by an unauthenticated user if the window is closed using the browser's 'x' button instead of the 'Cancel' or 'Finish' buttons. (Issue #69569)
Web folder link information can be accessed even after logging out of portal. (Issue #69570)
The 'Remove quick link' Editor can be accessed by an unauthenticated user if the window is closed using the browser's 'x' button instead of the 'Cancel' or 'Finish' buttons. (Issue #69571)
The 'Check in' versioning page can be accessed by unauthenticated user, although it is not functional. (Issue #69579)

Installing the Patch

This patch must be applied to all Plumtree Publisher 6.2 servers.

This Patch has two parts; one part must be installed on all servers hosting Plumtree Publisher, and the other part must be installed on all servers hosting the Plumtree Image Server.

Part One: To install the Publisher component of the critical fix on servers hosting Plumtree Publisher, perform the following:

1. Stop the Plumtree Publisher service.

2. Back up the original versions of the following files:

Filename Location

ptcs.war %PT_HOME%\ptcs\6.2\webapp

ptcs.ear %PT_HOME%\ptcs\6.2\webapp

Note: We recommend that you back up original files to a zip file to preserve path information, then save the zip file to a backup folder under the %PT_HOME% folder.

3. Unzip the PlumtreePublisher_6.2.1.zip zip file into the %PT_HOME% folder.

4. Clear the application server's cache by deleting the following folder: %PT_HOME%\ptcs\6.2\container\work

5. Restart the Plumtree Publisher service.

6. View the Plumtree Publisher diagnostics page by clicking on "Diagnostics" in the Publisher Administration portlet.
Verify that the Publisher version is: Version: 6.2.1.

Part Two: To install the Image Server component of the critical fix on servers hosting the Plumtree Image Server, follow these steps:

1. Stop the application server that is hosting the Plumtree Image Server (IIS, Tomcat, BEA WebLogic, Websphere).

2. Back up the existing versions of the following files:

Filename Location

jscomponent.xml %PT_HOME%\ptimages\imageserver\plumtree\common\private\js\jscontrols

jscomponent.justinstalled %PT_HOME%\ptimages\imageserver\plumtree\common\private\js\jscontrols

hablador.js %PT_HOME%\ptimages\imageserver\plumtree\content\private\js

navigate.js %PT_HOME%\ptimages\imageserver\plumtree\content\private\js

workflow.js %PT_HOME%\ptimages\imageserver\plumtree\content\private\js

Note: Oracle recommends that you back up original files to a zip file to preserve path information, then save the zip file to a backup folder under the %PT_HOME% folder.

3. Add a new entry (highlighted in bold below) to the jscomponent.xml file to include the new jscontrolsversion number, "229726":

<?xml version="1.0"?>

<name>jscontrols</name>

<current_version>229726</current_version>

<version number="229726">

<includes>

<include type="jscomponent" jscomponent="jsportlet"/>

<include type="jscomponent" jscomponent="jsutil"/>

<include type="jscomponent" jscomponent="jsxml"/>

<include type="strings" path="strings/PTControls-${LANG}.js"/>

<include type="js" path="PTControls.js"/>

<include type="css" path="styles/css/PTMenu.css"/>

<include type="css" path="styles/css/PTRichTextEditor.css"/>

</includes>

</version>

</includes>

</version>

</versions>

</jscomponent>

"XXXXXX" denotes the old jscontrols version number that the old Publisher build was using. Adding a new entry for the latest jscontrols version number should suffice.

4. Add a new entry (highlighted in bold below) to the jscomponent.justinstalled file to include the new jscontrolsversion number, "229726":

<?xml version="1.0"?>

<name>jscontrols</name>

<current_version>229726</current_version>

<version number="229726">

<includes>

<include type="jscomponent" jscomponent="jsportlet"/>

<include type="jscomponent" jscomponent="jsutil"/>

<include type="jscomponent" jscomponent="jsxml"/>

<include type="strings" path="strings/PTControls-${LANG}.js"/>

<include type="js" path="PTControls.js"/>

<include type="css" path="styles/css/PTMenu.css"/>

<include type="css" path="styles/css/PTRichTextEditor.css"/>

</includes>

<upgrade_policies>

<upgrade_policy comparator="&lt;" version="229726"/>

</upgrade_policies>

</version>

</includes>

</version>

</versions>

</jscomponent>

5. Unzip the PlumtreePublisher_ptimages_6.2.1.zip zip file onto the %PT_HOME% folder. This zip file contains 2 folders, 229726 and LATEST. It also contains 3 javascript files, hablador.js, navigate.js and workflow.js. Because the LATEST folder exists in this location, replace the old file with the new file when prompted to do so.

6. Restart the application server that is hosting the Plumtree Image Server (IIS, Tomcat, BEA WebLogic, Websphere ).

Version 6.2 HF208996 for All Operating Systems

This hotfix resolves the following issue in Plumtree Publisher 6.2. This issue is also present in 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

To resolve this issue on these products, please download the Common Components Container 1.5 HF208996 from Support Center .

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)

Version 6.2 HF206771

It is recommended that this hotfix be applied to all Plumtree Publisher 6.2 installations on Windows or Red Hat Linux. The hotfix is available in the Product Center and includes detailed installation instructions.

Issues Addressed

Action button icons in portlets (created from the announcement, news, content canvas or community directory portlet templates) are displayed as placeholders. (Issue #48354)

Post-Release Updates

The installation instructions presented in the original readme file for this hotfix were missing a step. The correct instructions are as follows:

From Publisher Explorer, delete the top level folder named "Portlet Templates."
Navigate to the Publisher Folder on the Portal Administration page, and delete the sub-folder named "Published Content Portlets."
Stop the Plumtree Publisher service.
Back up your existing ptcs.war and ptcs.ear files found in the directory $PT_HOME\ptcs\6.2\webapp.
Copy the new ptcs.war and ptcs.ear files to the directory $PT_HOME\ptcs\6.2\webapp.
Delete the directory $PT_HOME\ptcs\6.2\container\work\jboss.web.
Copy the published_content_portlets.pte file to $PT_HOME\ptcs\6.2\serverpackages.
Copy the published_content_portlets.zip file to $PT_HOME\ptcs\6.2\settings\migration.
Restart the Plumtree Publisher service.
Import published_content_portlets.pte using the Migration - Import utility.

Important: Wait a few minutes before attempting to create portlets from portlet templates.

Version 6.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 Publisher 6.2 supports the following:

Operating Systems: Windows 2003 SP1, Red Hat Enterprise Linux 3 Update 3; Solaris 8 and 9, SUSE Linux 9, AIX 5.3
Database Servers: Oracle 9i in default or Oracle RAC configuration; Oracle 10g in default or Oracle RAC configuration; Microsoft SQL Server 2000 SP3a
Browsers: Internet Explorer 5.0 or higher on Windows clients, and Netscape 4.71 and 7.2, Safari 1.2 and Firefox 1.0+

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 Publisher 6.2 supports the following:

Foundation 6.0
Collaboration 4.1
Studio 2.1 SP1

Documentation

The product distribution includes the following documents in the Documentation folder. For the most up-to-date documentation, go to the Oracle Technology Network.

Document Title and File Name	Document Description
Attributions Publisher_Attributions.txt	Provides a list of third-party technologies used in the product, along with licensing information.
Installation and Upgrade Guide for Plumtree Publisher 6.2 Installation_Guide_Plumtree_Publisher_v6-2.pdf	Provides instructions to install and upgrade the components of Plumtree Publisher 6.2.
Quickstart Installation Guide for Plumtree Publisher 6.2 Quickstart_Installation_Plumtree_Publisher_v6-2.pdf	Provides instructions for a rapid installation of Plumtree Publisher 6.2.
Quickstart Upgrade Guide for Plumtree Publisher 6.2 Quickstart_Upgrade_Plumtree_Publisher_v6-2.pdf	Provides instructions for a rapid upgrade of Plumtree Publisher 6.2.
Admin Guide for Plumtree Publisher 6.2 Administration_Guide_Plumtree_Publisher_v6-2.pdf	Provides information for performing initial and ongoing administrative tasks for Plumtree Publisher 6.2.
Online Help To access online help, click the Help icon in any Publisher portlet or Publisher Explorer.	The online help describes the attributes available to customize the content and format of each report and portlet.

New Features

Publisher 6.2 now includes support for operating systems Red Hat Enterprise Linux 3 Update 3, SUSE Linux 9, and AIX 5.3.
Publisher 6.2 now provides improved search results. Content Item search results display all associated portlets and communities.

Issues Addressed

When Publisher is configured to use the gateway for WebDAV requests, you may encounter problems with multi-byte characters if the portal is running on IIS. In some cases you may still be able to open the folder or file; in other cases this may fail. The folder or file will appear correctly in Publisher Explorer, even though it appears incorrectly in the Web Folder view. (Issue #37828)
A user's locale is not properly retrieved when creating a remote content source using the Publisher crawler web service. (Issue #42020)
Images with non-ASCII characters in their names do not get properly rendered through the rich text control. (Issue #43394)
The Publisher KD and Publisher Crawler content sources are available in the Submit a Document drop-down in the Knowledge Directory, even though they do not support this functionality. (Issue #43701)
Non-gatewayed access to WebDAV or WebEdit no longer works because Publisher now requires that the portal authentication ID and password are part of the request. (Issue #43889)
Some French and Dutch Workflow strings are improperly encoded. (Issue #44414)
Workflow does not use the alternate image server URL set in content.properties. As a result, it is necessary to create a ptworkflow.properties file as outlined in KB article DA_230242. (Issue #44667)
Images uploaded using the Rich Text Editor with LTCUseRelativeURLs set to true in content.properties are being gatewayed, even though there is an alternate publishing target set for images, and the image server URL is not in the published content web service's gateway space. (Issue #44964)
The Inherit Security functionality is not maintained for Content security in Publisher Explorer. (Issue #46063)
WebEdit does not work when the Publisher Administration portlet is in a community that the Everyone group does not have at least Read access to. (Issue #46605)
Default values are not copied when a DET is copied. (Issue #47221)

Known Issues

It is not possible to publish content via FTP using a port number other than 21. (Issue #44461)
It is not possible to re-publish an item to a Knowledge Directory folder different than the folder to which the item was originally published. (Issue #45903)
Object category names containing spaces and non-ASCII characters on the Advanced Settings screen of the portlet configuration editor for published content portlets are not properly escaped. (Issue #46013)
Child folders whose ACLs are emptied and inheritance settings are disabled automatically revert to inheriting security from parent folders. (Issue #46676)
Content items published to the Knowledge Directory with a comma in their name appear to be published into multiple folders. (Issue #46868)
Images uploaded to the rich text control have incorrect target URLs if LTCUserRelativeURLs is set to true and if images are published to an alternate image publishing target. (Issue #47402)
Object migration is not supported in Firefox 1.0+. (Issue #47500)
Sorting by "Modified On" in Publisher Explorer does not work. (Issue #47549)
Relative URLs will become corrupted if the preview publishing target is not in the gateway space of the portlet the rich text control is opened from. (Issue #47651)
A javascript error occurs when opening Publisher Explorer in Chinese Taiwan (zh-tw) locale. (Issue #48586)
Workaround: Rename imageserver/plumtree/content/private/js/resources/zh-tw to imageserver/plumtree/content/private/js/resources/zh_TW (i.e. change folder name zh-tw to zh_TW)
Preview of folders gives a 404 error when directory browsing is disabled. (Issue #48505)
Chinese Taiwan help files are not accessible. (Issue #48586)
Workaround: Rename the "zh-tw" help file folder (imageserver/plumtree/content/private/helpl/zh-tw) to imageserver/plumtree/content/private/helpl/zh_TW.
Publisher and Workflow images are missing when the Portal server has SSO enabled (SiteMinder 6.0.2.05 and Apache 2.0.53). (Issue #49324)
Workaround:
1. Log in SiteMinder Policy Server Admin Console
2. find and open the Agent Conf Object under System
3. in Parameter Name, find BadUrlChars
4. remove ""//"" from the Value string
WebDAV fails with Apache front end and WebSphere configuration on AIX. WebDAV/WebEdit functionality is not available on AIX when running an Apache front end with WebSphere. (Issue #49340)
On UNIX systems, locale information is not being set correctly in the Publisher service.conf file. To enable UTF-8 characters, the following modifications need to be made to the $PT_HOME/ptcs/6.2/settings/service.conf file. (Issue #48284)
Workaround:

On Solaris and SUSE environments:
1) Modify the line starting with "set.LANG" to read set.LANG=en_US.UTF-8
2) Modify the line starting with "set.LC_CTYPE" to read set.LC_CTYPE=en_US.UTF-8

On AIX:
1) Modify the line starting with "set.LANG" to read set.LANG=EN_US.UTF-8
2) Modify the line starting with "set.LC_CTYPE" to read set.LC_CTYPE=EN_US.UTF-8

Also, be sure to install any necessary operating system patches needed to support UTF-8 characters.
Several Plumtree products can only handle headers less than 4KB in size by default. However, certain configurations of the Plumtree Foundation may send headers that are greater than 4KB in size. This could occur by the portal passing large portlet preferences, third party headers, SSO tokens, etc. This will result in requests being dropped by affected products which could affect the functionality of that product. You may notice this as unexpected error messages being returned by the portal. You can also detect the size of the headers by using a TCP tracing tool such as Ethereal that can list header sizes. (Issue #48757)

To resolve the issue on Plumtree Publisher, you must edit the configuration on the server running Plumtree Publisher. The steps are:

1. Edit the file server.xml in the folder ptcs/6.2/container/deploy/jbossweb-tomcat50.sar/ and add the attribute maxHttpHeaderSize="8192" (or higher if necessary) to the HTTP/1.1 <Connector> element that appears at the beginning of the file.

2. Restart the Publisher