Version 4.2 MP1

Version 4.2

Collaboration 4.2 MP1 released March, 2007
Collaboration 4.2 released October, 2006

These release notes cover all releases of Collaboration 4.2, 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 http://www.oracle.com/technology/documentation/index.html.

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.2 MP1 supports the following:

• Operating Systems: Windows 2003 SP1; Solaris 8, 9, and 10; Red Hat Enterprise Linux ES 4; SUSE Linux ES 9; AIX 5.3; HPUX 11i v2.
• Database Servers: SQL Server 2000 SP3a, SQL Server 2000 SP4, SQL Server 2005, and Oracle versions 9.2.0.4, 9.2.0.5, 9.2.0.6, 9.2.0.7, 10.1.0.3, and 10.2.0.x, including RAC configuration.
• Browsers: Internet Explorer 6.0 and 7.0 on Windows clients; Netscape 7.2 and 8.x; Safari 2.0 (simple mode only); and Firefox 1.0, 1.5 and 2.0 on all clients. Refer to the Installation and Upgrade Guide for BEA AquaLogic Interaction Collaboration 4.2 for more detailed browser support information.
• Microsoft Office (For ALI Collaboration Office Tools Add-In): MS Office 2000 on Windows XP SP2; MS Office XP on Windows XP SP2; MS Office 2003 on Windows XP SP2; MS Office 2007 on Windows XP SP2.

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

At the time of release, Collaboration 4.2 MP1 supports the following:

• AquaLogic Interaction 6.1 MP1
• AquaLogic BPM WorkSpace Extensions 5.7

• After upgrading to Collaboration 4.2 MP1 from any previous version, it is required to rebuild the Collaboration search index. This feature can be accessed through Collaboration Administration.
• Collaboration 4.2 MP1 is not compatible with versions of the portal prior to 6.1 MP1 (including 5.0.x and 6.0).

• The Collaboration Notification service is unable to handle extremely large numbers of users subscribed to summary e-mails. This fix improves the performance of the notification service to handle large volumes of e-mail. (SR#1-4167938572)
• An unapproved document checked out via WebEdit is visible to all users. (Issue #57498)
• In a multi-domain configuration using Experience Definitions, notification e-mail links do not contain the correct domain in the URL. (Issues #58611 & #58546)
• There is a time-out setting in the portal that affects clustering behavior and should be changed if you are using clustering with Collaboration in the portal deployment. (Issue #49770)
• The OpenLog restrict-to-localhost parameter found in audit.xml is not functioning properly and sends UDP packets even if disabled (Issue #58434)
• Notification alerts are not sent on overdue tasks (Issue #52497)
• Read-only users who own a task receive a Collaboration Server error when attempting to add a note to that task. (Issue #52678)
• Users should not receive summary notifications for documents and document folders to which they do not have access. (Issue #53242)
• Documents attached to tasks in project templates do not retain their association when creating a project from the template. (Issue #54837)
• Users that are added to a task's "alerts" notifications list in a project template are not copied to a project created with the project template. (Issue #55016)
• Initiating a process from a Collaboration document times out when the user is logged into the portal using only the machine name in the browser. The user is not timed out when a fully qualified domain name is used. (Issue #56148)
• Task and task list name fields are limited to 60 characters; should be 100. (Issue #57811)
• Unix only: passwordChanger.sh* utility does not change the authenticationid password. (Issue #57973)
• Unable to rebuild Collaboration search index after upgrade to Collaboration 4.2 due to a document folder whose name contains a '/' (forward slash) character (Issue #57223)

• The issues below are in addition to those in the 4.2 known issues.
• If migration of Collaboration's pte file fails, the cause may be the license.bea. Run diagnostic.bat (ptportal/6.1/bin). If step #9 fails, there is a problem with the license settings. This will prevent portal and search from starting up properly, and will result in failure for the package import. (Issue #59444)
• Experience Definition URLs include user-specific fragments that preserve the correct look and feel of Experience Definitions for individual users. These URLs are cached by the Notification Service. If a portal user changes his or her login domain, the cached Experience Definition URLs for that user become invalid. There are other, less-common reasons why Experience Definition URLs can become invalid. If you are experiencing the same problem for a different reason, restarting the Notification Service will most likely resolve the problem for you, too. (Issue #58836)
• It is not possible to view details for document folders whose name contains a '/' (forward slash). The '/' character should be removed from all folder names. Document folders created in Collaboration 4.x will not contain the '/' character in the name, but folders created in versions of Collaboration prior to 4.0 may have included this character. (Issue #58642)
• WebEdit may not work in a multi-domain environment using SSL. The workaround is to modify Collaboration's config.xml file to <nonGatewayedAccess enabled="yes"/> (Issue #58576)
• If users encounter an error when creating an announcement or a discussion message in a multidomain environment using SSL, it may be necessary to disable the rich text editor control by modifying Collaboration's config.xml to <richtexteditor enabled="no"/> (Issue #58569)
• Sending e-mail to a discussion is rejected when too many characters (for example, more than 255) exist in the subject line. (Issue #57938)
• If nonGatewayedUploads is set to "yes" in config.xml (by default it is set to "no"), it may be necessary to modify the URL specified in the nonGatewayedUploads node to add a "/collab" to the end of the URL if the URL does not already contain this. (Issue #57749)
• WebEdit and WebFolders do not work correctly on clients running Office 2007 and Microsoft Vista. (Issue #60153)

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.2 supports the following:

• Operating Systems: Windows 2003 SP1 when used with AquaLogic Interaction 6.1; Solaris 8, 9, and 10; AIX 5.3.
• Database Servers: SQL Server 2000 SP3a & SP4, SQL Server 2005, and Oracle versions 9.2.0.4, 9.2.0.5, 9.2.0.6, 9.2.0.7, 10.1.0.3, and 10.2.0.x, 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 BEA AquaLogic Interaction Collaboration 4.2 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 BEA products.

At the time of release, Collaboration 4.2 supports the following:

• AquaLogic Interaction 6.1

The product distribution includes the following documents in the Documentation folder. For the most up-to-date documentation, go to http://www.oracle.com/technology/documentation/index.html.

Document Title and File Name	Document Description
Attributions Collaboration_Attributions.txt	Provides a list of third-party technologies used in the product, along with licensing information.
Installation and Upgrade Guide for BEA AquaLogic Interaction Collaboration 4.2 install.pdf	Describes how to install and upgrade the components of Collaboration 4.2
Collaboration 4.2 Installation Worksheet Collaboration_Installation_Worksheet.pdf	This document contains worksheets for entering the installation information required by BEA AquaLogic Interaction Collaboration 4.2.
Administrator Guide for BEA AquaLogic Interaction Collaboration 4.2 admin.pdf	Describes how to administer various components and features of Collaboration 4.2.
Online Help To access online help, click the Help icon on any Collaboration screen . . .	Describes how to use Collaboration functionality.

• Collaboration 4.2 now includes the ability to limit document versions.
• Collaboration 4.2 now includes the ability to manually notify entire portal groups via the "notify" feature.
• Collaboration 4.2 now includes the ability to copy document links directly from the details panel.
• Collaboration 4.2 now includes support for the new Clustered Search feature of AquaLogic Interaction 6.1.
• Collaboration 4.2 now includes additional features to the Collaboration portlets, including the ability to send notifications, create discussions, and filter on assigned tasks.

• After upgrading to Collaboration 4.2 from any previous version, we recommend that you rebuild the Collaboration search index. This feature can be accessed through Collaboration Administration.
• Collaboration 4.2 is not compatible with versions of the portal prior to 6.1 (including 5.0.x and 6.0)

• Community projects portlet shows incorrect list of projects for users who should have no projects shown. This bug only occurs for users who access a community that contains a Community Projects portlet and have NO ACCESS to any of the projects in the community project list. Instead of seeing an empty project list, they see a list of other projects they have access to. (SR# 1-4023269239; Bug 54221)
• The Task Alerts feature is not functioning properly - no overdue alert notification is sent. (Issue #52089)
• Documents that are automatically removed from the Recycle Bin are not being deleted from the Document Repository. (Issue #52475)
• Printing tasks are displayed in the wrong order. (Issue #53831)
• Simple/508-mode only: Task dates in non-US formatted dates are not recognized. (Issue#51973)

• The WebEdit functionality in Collaboration consumes multiple user sessions in the portal. If this functionality is used with a portal running with an SDK license, the user session limit will be exhausted quickly. Additional users will not be able to log in to the portal until one of the existing sessions has expired or the portal is restarted. (Issue #54472)
• 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 files and generate subscription e-mails for every file. (Issue #52395)
• An Internal Server Error returns when the file size reaches the maximum project size 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 in the portal deployment. The default time-out value for retrying a server that goes down is 3600 seconds (1 hour). We recommend that this value be changed to 60 seconds (1 minute). This change should be made in the portal 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.BEA.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)

• 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)
• 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. If this occurs, the correct application cannot be launched. (Issue #44912)
• User names that contain non-ASCII characters do not display correctly in user pickers. (Issues #45025, #45093)
• Clicking on Download Template>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 Collaboration6.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)
• 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 fewer than 230 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.
• Customers using Oracle might see the error "No more data available to read" in 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.

• Issue #60153, WebEdit and WebFolders do not work correctly on clients running Microsoft Vista, has been resolved for Office 2003 users on Vista clients with Microsoft update 907306 installed. WebEdit and WebFolders do not work for Office 2007 users on Vista clients. December 13, 2007