Collaboration 4.1 SP2 released June, 2006

Collaboration 4.1 SP1 released December, 2005

Collaboration 4.1 released September, 2005

These release notes cover all releases of Collaboration 4.1, including hotfixes and service packs. For information on a particular release, 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.

We recommend that this service pack be applied to all Collaboration 4.1 servers.

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. The supported configurations have not changes from 4.1 SP1.

• There are no new features in this service pack.

• Common Components update. 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)
• '{' and '}' characters in URLs when creating new events caused problems with reverse proxy configurations. (Issue #47336)
• Importing an exported project displays all ? mark for Asian languages. (Issue#48742)
• Subscriptions are not copied from a project template to a project. (Issue #48755)
• Several Plumtree products can only handle headers less than 4KB in size by default. However, certain configurations of 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)
• If clustering is enabled, the log file may contain errors. (Issue #49770)
• Clustering of Collaboration has been verified to work with Plumtree Foundation 6.0 SP1 and Plumtree Corporate Portal 5.0.x; however, it is not recommended to use clustering with the original non service pack Plumtree Foundation 6.0 release. See Known Issues below for more information about clustering and Plumtree Foundation 6.0 SP1. (Issue #50135)
• Rejecting a document from a notification e-mail generates an error. (Issue #50390)
• Startup may be very slow for extremely large deployments with many projects. (Issue #51019)
• Check-outs and downloads from projects with an apostrophe can cause UI to hang. (Issue #51246)
• When trying to use the EDK method TaskListManager.QueryTasks(myList, taskFilter) an error may be generated about invalid status values. (Issue #51535)
• Uploading documents in very large projects can cause errors on Oracle. (Issue #52742)
• Users who attempt to use the bulk upload or WebEdit features in Collaboration will receive a warning that the certificate has expired (Issue #50937).

The following issues are in addition to the Known Issues listed below for Versions 4.1 and 4.1 SP1.

• After upgrading collab from 4.0.2 to collab 4.1, the due date of a some tasks which have dependencies may be changed. (Issue #49270)
• WebDAV may not function correctly if the "webdav extensions" are set to "allowed" instead of "prohibited" on the portal server gatewaying the traffic. This only applies when running the .NET version of the portal. (Issue #50584)
• When changing a Collaboration folder through Web Folders, all the files underneath are treated as newly uploaded file and will generate subscription e-mails for every file. (Issue #52395)
• Internal Server Error returns when the file size reaches the maximum project during bulk upload. (Issue #52442)
• There is a time-out setting in the Portal that affects clustering behavior and should be changed if you are using clustering with Collaboration and Plumtree Foundation 6.0 SP1 (this does not apply to Plumtree Corporate Portal 5.0.x, and it is not recommended to use clustering with the non service pack Plumtree Foundation 6.0 release) . The default time-out value for retrying a server that goes down is 3600 seconds (1 hour). It is recommended that this value be changed to 60 seconds (1 minute). This change should be made in the Plumtree Foundation 6.0 SP1 deployment as follows:

1. Find the file <PT_HOME>\settings\common\serverconfig.xml

2. Search for this section in the file:
<component name="openhttp" type="http://www.plumtree.com/config/component/types/openhttp">

3. Add this setting:
<Setting name="openhttp:FailuresTimeToClear">
<value xsi:type="xsd:integer">60</value>
</setting>

4. Restart the Portal.

(Issue #49770)

We recommend that this service pack be applied to all Collaboration 4.1 servers.

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.

In addition to the operating systems and application servers supported in Version 4.1, at the time of release, Collaboration 4.1 SP1 adds the following support:

• Operating Systems: AIX 5.3; Solaris 8 and 9; SUSE Linux

• Collaboration 4.1 SP1 now includes support for AIX, Solaris, and SUSE operating systems with Plumtree Foundation 6.0.

• The daily summary notification e-mail and the task summary notification e-mail might not send reliably. We recommend using the immediate notification option for subscriptions instead of the summary option. (Issue #47889)
• Daily summary and task summary notification e-mails might contain improper formatting. (Issues #47620, #47875, #47898)
• When changing the summary job time through Administration>Collaboration Administration>Collaboration Notification, the time might revert to 0:00. (Issue #47929)
• In Project Explorer, you cannot view the next page of search results when the number of search results is greater than the maximum number of projects allowed in the table pane. To workaround this issue, disable pagination. (Issue #47997)

The following issues are in addition to the Known Issues listed below for Version 4.1.

• (Oracle-only) If you have multiple Collab schemas in a single Oracle instance, then you may get errors from the portal-collaboration-server-role-grant . The workaround is when creating a collab schema after the first one is in place, you will need to comment out the following two lines in your portal-collaboration-server-role-grant script.
  --drop role CollabRead;
  --create role CollabRead;
• The new Collaboration 4.1 crawler only works with Portal Foundation 6.0; it is not compatible with 5.x versions of the portal.
• 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 #49524)
• You will need to run portal-collaboration-server-data.sql even if you are upgrading a 5.0.4 portal instance to Collaboration 4.1 if you change hostnames during the course of the upgrade. If the hostnames do not change, it is not necessary to run this script. (Issue #48614)
• Projects that have been archived in 3.x and restored in 4.1 display the following error when the documents tab is accessed: “You do not have sufficient permission to access this folder.” (Issue #49150)
• If clustering is enabled, the log file may contain errors. These errors can be ignored. (Issue #49770)
• Global Deployment features from Collaboration 3.x do not work and are not supported with any 4.x release including 4.1 SP1.
• 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 this issue for Collaboration or other services, you must update the file plumtree-bootstrap.jar on all servers that are running the affected products.
  The steps are:
  • Contact support and get a newer version of plumtree-bootstrap.jar .
  • Place the file in the following common folder that is used by all products:
    • Windows : \program files\plumtree\common\container\tomcat\5.0.28\bin\
    • Unix : /opt/plumtree/common/container/tomcat/5.0.28/bin/
  • Restart the services for all products running on that particular server (including Collaboration).
    Replacing plumtree-bootstrap.jar here will update all products running on that particular server and allow headers up to 16KB in size.

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, Collaboration 4.1 supports the following:

• Operating Systems: Windows 2000 and Windows 2003 when used with Portal 5.0.4, and Windows 2003 SP1 and Red Hat Enterprise Linux 3 Update 3 (ES & AS) when used with Foundation 6.0.
• Collaboration 4.1 is no longer deployed into a customer's application server; it is instead bundled with the technology required for operation.
• Database Servers: SQL Server 2000 SP3a, and Oracle versions 9.2.0.4, 9.2.0.5, 9.2.0.6, and 10.1.0.3, including RAC configuration.
• Browsers: Internet Explorer 5.5 or higher on Windows clients, and Netscape 7.2, Safari 1.2 and Firefox 1.0+ on all clients. Refer to the Installation and Upgrade Guide for Plumtree Collaboration 4.1 for more detailed browser support information.

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, Collaboration 4.1 supports the following:

• Plumtree Foundation 6.0
• Plumtree Corporate Portal 5.0.4

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

• Collaboration 4.1 provides improved platform support: Collaboration now supports Red Hat Linux 3, Windows 2003 SP1, Plumtree Foundation 6.0 and Oracle 10g.
• Collaboration 4.1 provides object-level attachments: Users can attach documents to discussion messages, tasks and events.
• Collaboration 4.1 provides the ability to e-mail a project: Users can create new discussion messages and documents by simply sending e-mail to a Collaboration project.
• Collaboration 4.1 provides UI customization: Users can modify which columns and buttons appear in each of the Collaboration portlets.
• Collaboration 4.1 provides event recurrence: Users have an expanded set of recurrence options when creating events.
• Collaboration 4.1 provides zip download: Users are able to download multiple files and/or folders using the Web user interface; moreover, users are able to zip archive, and therefore compress large documents prior to download.
• Collaboration 4.1 provides folder moderation: Project Leaders can designate users as folder moderators, allowing them to allow or reject documents in folders.
• Collaboration 4.1 provides Collaboration Crawler: Users can bulk publish Collaboration documents and folders to the portal's Knowledge Directory using an out-of-the-box Collaboration Crawler.
• Collaboration 4.1 provides general notification improvements: E-mail notifications have been improved in several ways:
  • Users can specify the format in which they receive e-mail notifications (plain-text or HTML).
  • Users are able to notify entire project roles.
  • Users are able to subscribe to events.
  • Users are able to subscribe to announcements.
  • E-mail notifications list the reasons for the notification.
  • Users are able to perform actions such as check-out, WebEdit, etc. from e-mail notifications.
• Collaboration 4.1 provides general task improvements: Tasks have been improved in several ways:
  • Users are able to specify a custom percentage value for task completion.
  • Users are able to specify task duration.
  • Users are able to define holidays.
  • Users are able to specify whether tasks (and events) should occur on holidays.
  • Users can re-order tasks and subtasks using a drag-and-drop interface.
• Collaboration 4.1 provides general administration improvements: Collaboration administration has been improved in several ways:
  • Administrators can set maximum project size on a per-project basis.
  • Administrators can configure various config.xml parameters via the Collaboration Administration utility.
  • Administrators can access the Collaboration log file via the Collaboration Administration Utility.
• Collaboration 4.1 provides recycle bins: Deleted projects and objects are temporarily stored in recycle bins until permanently deleted.
• Collaboration 4.1 provides a Plumtree Collaboration Office tools add-in: A new Office plug-in offers various options to users checking documents in via WebEdit or WebDAV.

• After upgrading to Collaboration 4.1 from any previous version, we recommend that you rebuild the Collaboration search index. This feature can be accessed through the Collaboration Administration page.
• Collaboration 4.1 is compatible with Portal 5.0.4; however, if you upgrade from Collaboration 4.0.2 to 4.1 without upgrading to Foundation 6.0, you must perform additional steps if the Portal is later upgraded to 6.0. These steps are described in Knowledge Base article DA_ 345175.
• When installing Collaboration 4.1 with Portal 5.0.4 as a clean install (not an upgrade from an earlier version of Collaboration), an additional pre-installation step is required prior to running the Collaboration 4.1 installer on the Image Server. Refer to the Installation and Upgrade Guide for Plumtree Collaboration for more information. (Issue #48055)

• When using WebEdit to edit a Microsoft Office document, the checked-out state is not automatically updated in the Collaboration Server view. The Microsoft Office Tools plug-in that ships with Collaboration 4.1 must be installed to address this issue. (Issue #30391)
• When scripting an Oracle database, if you run SQL Plus through the Enterprise Manager, the Collaboration Server SQL scripts should not be run in the same SQL Plus session as the portal scripts as there is a bad interaction between the two script bases. This does not apply to the command line version of SQL Plus. (Issue #31832)
• The script collaboration-server-3-x-x-to-4-0-0-upgrade.sql for Oracle on NT is missing a closing semicolon. (Issue #35351)
• Web folders with multi-byte characters in their names cannot be opened when running the portal on IIS 6 in IIS 5 isolation mode. Only Foundation 6.0 supports IIS 6 without isolation mode so this will still be an issue for Portal 5.0.4 customers. (Issue #39056)
• A user who only has guest access to a project will receive an error when attempting to add a note to a task. (Issue #40088)
• When a notification is sent after a document has been copied in a project, the notification states that the copy was checked-in by the user that originally uploaded the document, not the user that created the copy. The project view shows that it was checked-in by the correct user. (Issue #40345)
• When creating a task that is dependent on another task, the end date of the dependent task is saved incorrectly. (Issue #40444)
• Previously published Collaboration documents are not deleted from the Knowledge Directory when the source Collaboration document is deleted. (Issue #40986)
• If a discussion has a document attached, the Notify button does not work when attempting to notify from a discussion, or from the document itself. (Issue #41307)
• The number of discussion messages displayed in the discussions area of a project does not reflect the correct number of messages. (Issue #41446)
• The passwordchanger.bat file returns errors when used. (Issue #41473)
• When attempting to open an Outlook meeting or appointment with a colon (:) in the name from the Collaboration calendar using the Open in Outlook button, you receive a page cannot be found error. (Issue #41903)
• If an event occurs on different days in different time zones, the correct day is not highlighted when switching time zones. (Issue #42003)
• Users whose display name includes a comma (,) cannot be properly assigned to a task. (Issue #42005)

• When installing the Collaboration image service files, the Collaboration installer must be run on the same machine where the image service directory resides and cannot be installed over a network path. (Issue #43714)
• The Subscribe and Subscribe Others buttons should not be used in the context of a Project Template; they only function with regular Projects. (Issue #44273)
• Previous versions of Collaboration allowed the '#' character in documents and folders; however, these documents and folders cannot be accessed via WebDAV so it is no longer possible to create a document or folder with '#' in the name. (Issue #44909)
• When creating a new Microsoft Office document, the extension should not be deleted or the correct application cannot be launched. (Issue #44912)
• User names that contain non-ASCII characters will not display correctly in user pickers. (Issues #45025, #45093)
• Clicking on Download Template>Plumtree Collaboration Template File might result in a Page Not Found error. This occurs when the Microsoft Project Template extension, .mpt, is not registered as a MIME type in the portal's application server. Refer to your application server's documentation for information on registering a MIME type. (Issue #45405)
• When importing the plumtreeCollaboration-Portal60.pte file during installation, the message "Dropped ACL due to missing User or Group dependency" in the migration log can be safely ignored. (Issue #45756)
• The Microsoft Office plug-in does not support Asian languages. (Issue #47153)
• When clicking the New or Edit discussion message button you might be prompted to download "blank.html". This only happens with certain versions of Internet Explorer 6 and can be ignored. We recommend you upgrade to the latest service pack for Internet Explorer. (Issue #47329)
• Projects whose names contain the following characters will no longer be displayed as Web Folders: \ / * ? < > | #. New projects with these characters in their names can still be created, but the creator will receive a warning. (Issue #47479)
• When using Firefox, the state of a file is not updated in the Collaboration page after checking it in or out via WebEdit. (Issue #47583)
• Daily and monthly events in mixed time zones do not always display properly. A monthly or daily event created in one time zone will not always appear on the correct day if viewed in a time zone where the event would fall on a different day. (Issue #47712)
• It is not possible to open two Microsoft PowerPoint files simultaneously via WebDAV. (Issue #47769)
• When editing files through web folders, if the full Web folder path is greater than 229 characters, opening in Edit mode causes a DDE error. (Issue #47801)
  WORKAROUND: Make sure that the path of the file contains few enough characters. To do this, use one of the following methods.
  • Rename the file so it has a shorter name.
  • Rename one or more folders that contain the file so that they have shorter names.
  • Move the file to a folder that has a shorter path name.
• The daily summary notification e-mail and the task summary notification e-mail might not send reliably. We recommend using the immediate notification option for subscriptions instead of the summary option. (Issue #47889)
• When changing the summary job time through Administration>Collaboration Administration>Collaboration Notification, the time might revert to 0:00. (Issue #47929)
• The month name is displayed in English in the daily and weekly calendar views for non-English locales. (Issue #47935)
• When choosing a group to notify, the names of groups with non-ASCII characters are garbled in the selected groups displayed at the bottom of the picker window. (Issue #47937)
• It is possible to create a project with an illegal character in its name when using Firefox, even though projects with illegal characters in their names will not display as a Web folder. (Issue #47748)
• Non-ASCII characters are not displayed properly when subscribing others from the project general view. (Issue #47944)
• When creating a holiday by right-clicking on a day in the calendar, the default date is one day later than the day that was clicked. (Issue #47954)
• When using Internet Explorer, after clicking "All projects" under My Account>Collaboration Settings>Subscriptions, the screen displays "Saving . . ." but does not ever load. Clicking the Back button in the browser will return you to the My Account page. (Issue #47968)
• It is not possible to assign a user in a task list imported from Microsoft Project using Firefox. (Issue #47971)
• In Project Explorer, you cannot view the next page of search results when the number of search results is greater than the maximum number of projects allowed in the table pane. To work around this issue, disable pagination. (Issue #47997)
• It is not possible to export a project with a comma (,) in its name. (Issue #47999)
• The Project Explorer page in simple mode is not properly formatted. (Issue #48058)
• Customers using Oracle might see the error "No more data available to read" in the collaboration.log if statistics are not run on the database. All Oracle deployments must follow the steps in KB article DA_232966 to prevent this error.