BEA AquaLogic SharePoint Console 1.0 - released March 2006

These release notes cover the first release of AquaLogic SharePoint Console 1.0.

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.

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

At the time of release, AquaLogic SharePoint Console supports the following:

• Operating Systems: Windows 2003 Server SP1
• Application Servers: .NET 1.1 SP1, IIS 6.0
• SharePoint Products: Windows SharePoint Services 2.0

For the latest information on supported BEA products, refer to the Interoperability page in the Product Center at support.plumtree.com.

At the time of release, AquaLogic SharePoint Console supports the following:

• Plumtree Corporate Portal 5.0.4
• AquaLogic User Interation 6.0/Plumtree Foundation 6.0

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

• In the List Settings page of the SharePoint crawler, if you check an item type, go to another page, go back to the List Settings page and uncheck the item type, the unchecked setting will not persist when you click Finish to save the crawler setting. In order to uncheck the item type, you must reopen the crawler, go the List Settings page, uncheck the unwanted item type, then click Finish to save the editor.
• The name of the document created in the portal will be based on the Title property of the document in WSS and not the filename of the WSS document.

• The online help for the content source, crawler, and administrative settings for the portlets are not localized.

• Testing has shown that the SharePoint Search portlets could take several minutes to become functional after the initial installation of the SharePoint. This is due the the creation of custom properities that are used by the SharePoint Search Portlets and caching of the portal.
• When uninstalling the SharePoint Console, newly created websites and virtual directory for the search portlets are not removed. They are listed under SharePoint CWS/Custom Search. You should remove these manually if desired.
• When uninstalling the SharePoint Console image files, the .NET Web Controls that was installed along the images part of the console is not automatically uninstalled. This is because another application may be using those files. To remove .NET Web Controls, you must do so seperately via a seperate entry in the Windows Add/Remove Programs control panel.
• The icon for Knowledge Directory folders do not appear in the SharePoint Search or Most Recently Used portlets if a setting on the WS Server is not changed on 6.0 portals (5.0 or 6.0 SP1 portals are not affected). To change the setting:
  • Go to the machine where your WS Server is installed. You can find at least the URL of the WS server by going to the Portal Settings utility in the administration section of the portal UI and clicking on the portal URL Manager page.
  • Go to the folder \\<PT HOME>\settings\common\ where PTHome is the installation directory.
  • Edit the file serverconfig.xml.
  • Add /plumtree/ to the value for the ImageServerConnectionURL. For example, "http://baseURLimageserver" would become "http://baseURL/imageserver/plumtree/".
  • Restart the Plumtree API Service.

• Searches for parts of a word in the description of a WSS item will fail to return results for that word. For example, searching for "port" in the description will not return items with the term "portal" in the description.
• Click throughs through either the Search portlet results or the Most Recently Used portlet only work for Knowledge directory documents and Knowledge directory documents that link to WSS resources.
• For SharePoint Consoles running on French versions of Windows 2003, if the name or path of a document contains BOTH numbers AND double byte characters e.g. Japanese, click throughs directly to that document will fail. Clickthroughs to the properties page will still succeed.