Plumtree Foundation 6.0 SP2 released April 2008, for all Operating Systems

Plumtree Foundation 6.0 SP1 released April 2006, for all Operating Systems

Plumtree Foundation 6.0 released December 2005, for SUSE, Solaris, and AIX

This release includes all fixes from the Plumtree Foundation HF204729 released November, 2005. Other information for this release is the same as for the Plumtree Foundation 6.0 for Windows and Red Hat release and is available in the section Version 6.0 for All Operating Systems in this document.

Plumtree Foundation 6.0 HF204729 released November 2005, for Windows and Red Hat

Plumtree Foundation 6.0 released September 2005, for Windows and Red Hat

These release notes cover all releases of Plumtree Foundation 6.0, 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 one.bea.com/support.

It is recommended that all Plumtree Foundation 6.0 systems upgrade to this latest service pack.

The release package for Plumtree Foundation no longer contains a "ThirdParty" folder with a copy of Apache Tomcat and Apache HTTP Server. The correct locations to obtain a copy of Apache Tomcat and Apache HTTP Server for your OS are:

• Apache Tomcat: http://tomcat.apache.org
• Apache HTTP Server: http://httpd.apache.org

• When a portlet is created while editing a community page, the resulting portlet is not added to the community page automatically. (Issue 51684)
• Sometimes when editing an experience definition, user will get a unique name violation exception. (Issue 51426)
• An experience definition cannot be modified when the ImageServer URL is relative. (Issue 47416)
• The High Availability login token expires prematurely, preventing some users from benefiting from the High Availability feature. (Issue 54224)
• Gateway malforms Javascript statements during transformation. (Issue 52878)
• Repeatedly calling the Approve Directory Content slows it down. (Issue 53012)
• Crawl jobs hang when crawler has 10 destinations folders with filters assigned. (Issue 53106)
• WWW crawler fails to crawl pages with invalid charset. (Issue 53010)
• Some documents are not removed from the Knowledge Directory when they no longer exist in the source repository. (Issue 53520)
• Document Refresh Agent job will reimport documents when their refresh date is due regardless of whether the document has changed. (Issue 53903)
• Gatewayed WWW crawl of a site protected by basic auth crawls in every card with the same title and properties as the first card in the batch. (Issue 51675)
• Access denied exception bubbles up to the UI when getting subcommunities. (Issue 53345)
• Documentum date format is unparseable. (Issue 55626)
• Portal server does not honor UserSessionPrefBytesTotal and GuestSessionPrefBytesTotal settings in portalconfig.xml (Issue 56487)
• Creating more than 25 pages in a community is erroneously allowed. (Issue 56636)
• The migration snapshot with content snapshot will cause portlet error due to an unknown error when displaying. (Issue 52364)
• Non-inherited community pages get reverted back to the settings of the page template after copying a community. (Issue 60507)
• Page Template does not get inherited when creating a new Community Page from the Community Editor. (Issue 61042)
• The dependency of Publisher portlet is lost at migration of Snapshot Query. (Issue 60640)
• Gatewayed portlet content that contains gatewayed .js and .gif (image) files will return the cached content of the portlet in the message body on HTTP 304 responses. (Issue 62229)
• The document with Card ID(OBJECTID) of 8388608 or more is not deleted from Search Index by Search Repair although is deleted from DB. (Issue 61442)
• Copy and add a page from administration in community. The menu (navigation menu [pages tag]) shows duplication after logon. (Issue 62787)
• SetPropertyData of IPTObjectProperties does not set the property date values. (Issue 64294)
• Search update agent (SUA) repair does not reconcile community pages after a search server rebuild. (Issue 56664)
• PPE-LB doesn't mark down service correctly if there are multiple app servers instances on the same host. (Issue 61325)
• Refresh (F5) makes New pages to do refresh after creating a new page in community editor. (Issue 61057)
• Mirrored references do not get auto-approved even when "Automatically approve imported documents" is set in the crawler settings. (Issue 61677)
• DCTM Crawler : mirrored DCTM documents appear and disappear over consecutive crawls. (Issue 61666)
• Crawlers are extremely slow in 6.0 SP1 as a result of the fix to bug number 51250. (59339)
• Duplicate cards are created by crawlers. (60506)
• Inherited portlets are editable but changes are not saved. (Issue 60054)
• DataDirect Oracle JDBC drivers version 3.4 cause intermittent problems when starting Portal or PTAPI Service with Oracle RAC. (Issue 59869)
• Error when adding a page to a community based on a page template which has been searched for. (Issue 57030)
• 2007 Daylight Savings Time rules not taking effect on .Net. (Issue 59119)
• Activity Servers are unable to generate image and JS base URLs when the PT-Imageserver-URI string is a relative URL. (Issue 55592)
• Binary gateway does not handle situation where temporary file is not accessible and causes serious upload problem with WebEdit in Collab. (Issue 57324)
• Documentum and Windows File Crawlers re-import all Cards if 'Refresh ACLS' is selected.(Issue 56225)
• Automation server deletes cards after a mirrored crawl in which errors were detected. (57311)
• Snapshot query link for Publisher content item is not secure. (Issue 54592)
• Community pages not properly inheriting content canvas portlets. (Issue 60903)
• Page template editor allows more than one content canvas portlet to be added. (Issue 61276)
• Can't save page after switching between content canvas portlets. (Issue 61272)
• ADO.Net exception occurs repeatedly on all queries executed after a query timeout exception. (Issue 53098)
• Web.config in .Net has debug set to true. (Issue 56136)
• Any application that generates an HTTP 302 redirect that is processed through the JSR-168 container generates *two* redirects for every underlying application redirect. (Issue 55717)
• Automation server does not gracefully call the shutdown to the DTCMCWS thread when the card refresh agent is being run. (Issue 54522)
• The replicate utility on AIX crashes and dumps core when run. (Issue 54577)
• Far Eastern characters are not recognized in the URL of Web Services that are associated with Remote Servers.(Issue 54184)
• Parent/child group integrity is not kept when a partial users/groups synch is run after a partial users synch. (Issue 53322)
• Editing the security of documents fails when the ID of the document is large (typically > 1,000,000.) (Issue 39885)
• OpenHTTP load balancer no longer supports recovery after fail-over. (Issue 48430)
• Creation of the Documentum mirrored references should be based on the datasource ID and not the crawler ID. (Issue 51250)
• Sequence of SQL statements when creating a user leads to long execution times and blocking. (Issue 52178)
• Netegrity SSO cookies sent to remote portlets do not necessarily pass the same SMSESSION info that is passed upon portal login. (Issue 42710)
• Access denied exception bubbles up to the UI when getting subcommunities. (Issue 53345)
• SetPropertyData of IPTObjectProperties does not set the property date values. (Issue 64294)
• CPU utilization at 100% due to stuck threads in the portal never ending. (Issue 61632)
• With multiple URL mappings in security mode 3, the portal will sometimes erroneously redirect the user. (Issue 64675)
• BEA Plumtree Portal cross-site scripting vulnerability. (Issue 64325)

It is recommended that all Plumtree Foundation 6.0 systems upgrade to this latest service pack.

• Null pointer exceptions no longer occur for WWW crawlers when no form fields are defined in the WWW content source. (Issue #37624)
• Crawler job suspension settings are now properly applied to jobs. (Issue #38854)
• Broken document link behavior is now properly applied when crawls are mirrored. (Issue #40493)
• Documents published from ALI Collaboration now use relative links to allow for server name changes. (Issue #42106)
• Deleting properties used by a Snapshot Query no longer disables the Snapshot Query. (Issue #42729)
• Files upload to the knowledge directory more reliably. (Issue #45644)
• The localization tag is exported with localized objects during migration. (Issue #46281)
• Mirrored file crawlers will now properly delete the resulting empty portal Knowledge Directory folder if the source folder is deleted. (Issue #46671)
• Users do not need Select access to Snapshot Query objects in order to suscribe to query e-mails. (Issue #47043)
• End user Snapshot Query date pickers work properly on Netscape and Firefox. (Issue #47548)
• Users no longer need Select access to properties being returned in a query to view the query. (Issue #47953)
• User profile categories can be successfully deleted. (Issue #47674)
• Checking and unchecking folders in the Smart Sort utility works properly. (Issue #47694)
• Web services now allow URLs greater than 255 characters in length. (Issue #48122)
• Scroll bars now appear in the document display pop up in the document approval utility. (Issue #48417)
• The portal now properly handles session timeouts when using SSO. (Issue #48486)
• The communitypagesdatatag now utilizes community IDs that are passed to it. (Issue #48657)
• Automation Service stability has improved for RedHat Linux systems. (Issue #48681)
• Portal performance when using basic authentication with portlets on .NET portals has improved. (Issue #49721)
• The login page works properly with Safari 1.3.1 browsers. (Issue #49326)
• Password protected files are now properly indexed. (Issue #50076)
• Documents opened in a new window from the Community Links Portlet now show the navigation bar. (Issue #50316)
• Best Bets now work with Publisher items. (Issue #50623)
• Clickthroughs to documents that first require an SSO login properly redirects to the document. (Issue #50816)
• Experience Definition rules can be migrated individually. (Issue #50927)
• WebEdit functions properly with ALI Collaboration on SSO enabled portals. (Issue #50969)
• Users who are members of more than 1000 groups can view documents. (Issue #51064)
• Community links portlets properly increment the counter when new links are added. (Issue #51138)
• Mandatory portlets properly display on MyPages. (Issue #51150)
• Custom properties are properly retained by the Search Update Agent. (Issue #51745)
• Custom user profile properties can now be properly mapped and imported. (Issue #51767)
• Remote servers that are load balanced via HTTP load balacing are now put back into rotation when they are available again without requiring a restart of the Portal Servers. (Issue #48430)

It is recommended that this hotfix be applied to ALL Plumtree Foundation 6.0 Portal and Administrative Portal servers running on Windows and Red Hat operating systems.

• The PT Configuration Manager tool properly opens in Linux deployments. However, there may still be issues opening the PT Configuration Manager tool if the Linux system is accessed via Cygwin in rooted mode. You should use rootless mode if using Cygwin and accessing the PT Configuration Manager tool. (Issue #47571)
• The .NET OpenHTTP component no longer utilizes 100% CPU under certain conditions. (Issue #47770)
• The binary gateway no longer utilizes 100% CPU when uploading files under certain conditions. (Issue #47880)
• They cryptography utility no longer results in portlet errors when the Web server is configured to use basic authentication. (Issue #48348)
• In a community page, portlets can be added to a column that already contains a portlet from the page template. (Issue #48511)
• Should an error occur, OpenHTTP now returns errors much more quickly. (Issue #48517)
• Top level Knowledge Directory folder creation is now significantly faster. (Issue #48533)
• PTSelector no longer utilizes 100% CPU under certain conditions. (Issue #48543)
• Null pointer exceptions no longer occur when running the portal with SSL under high load. (Issue #48677)

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, the Plumtree Foundation 6.0 supports the following:

• Operating Systems: Windows 2003 SP1, Linux Red Hat 3 Update 3 ES & AS (on x86), SUSE Enterprise Linux 9 (on x86), AIX 5.3 (on POWER3, POWER4, POWER5), and Solaris 8 and 9 (on SPARC).
• Databases: MS SQL Server 2000 SP3a, Oracle 9i (9.2.0.4 and 9.2.0.6), and Oracle 10g (10.1.0.3).
• Application Servers:
  • Windows: .NET 1.1 SP1, Tomcat 5.0.28 with JDK 1.4.2, BEA WebLogic 8.1 SP4 with JDK 1.4.2, IBM WebSphere 6.0.1 with JDK 1.4.2.
  • Red Hat: BEA WebLogic 8.1 SP4 with JRockit SDK 1.4.2_05-8140, Tomcat 5.0.28 with Sun SDK 1.4.2.
  • SUSE: BEA WebLogic 8.1 SP4 with JRockit SDK 1.4.2_05-8140, IBM WebSphere 6.0.1 with IBM SDK 1.4.2, Tomcat 5.0.28 with Sun SDK 1.4.2.
  • Solaris: BEA WebLogic 8.1 SP4 with Sun SDK 1.4.2_05, Tomcat 5.0.28 with Sun SDK 1.4.2.
  • AIX: IBM WebSphere 6.0.1 with IBM (32-bit) SDK 1.4.2 .
• Browsers: Microsoft Internet Explorer 5.5 and 6.0, Netscape 7.2, Safari 1.2 and 2.0.1 (Mac only), and Firefox 1.0 for browsing users and Microsoft Internet Explorer 5.5 and 6.0 for administrative users.

NOTE: The Plumtree Foundation 6.0 does not support IPv6. If a system is incorrectly configured to enable IPv6, errors may occur with your system. You must ensure that IPv6 is not enabled on your system before installing the Plumtree Foundation 6.0. For help verifying whether IPv6 is enabled, please contact customer support.

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, the Plumtree Foundation 6.0 supports the following:

• Plumtree Collaboration 4.1 SP1, Publisher 6.2, Studio 2.1 SP1, and Analytics 1.2
• Windows File Content Service 6.0.1, Active Directory Identity Service 6.2, and LDAP Identity Service 2.1
• .NET Web Consumer 3.0 SP1

As more platforms are supported, additional upgrade paths to the new supported platforms will be included.

• Plumtree Foundation 6.0 Windows currently supports upgrade directly from the Plumtree Corporate Portal 4.5WS SP3 on Windows.
• Plumtree Foundation 6.0 Windows currently supports upgrade directly from the Plumtree Corporate Portal 5.0.2 and higher on Windows.
• Plumtree Foundation 6.0 Solaris currently supports upgrade directly from the Plumtree Corporate Portal 5.0.4J Solaris.

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

• The Plumtree Foundation 6.0 now supports new operating systems, databases, and application servers.
• Enhanced Managed Experiences (formerly Subportals)
  • Multiple Experience Access per User
  • URL, IP, Community, Group, or Folder based Experiences, controlled by Experience Rules
  • Multiple Guest Users
• Community Enhancements
  • Securable and Localizable Community Pages
  • Unlinkable Community and Page Templates
  • Copyable Communities
  • Copyable and Movable Community Pages
• Snapshot Query Enhancements
  • Relative Time Based Queries
  • Configurable Return, Display, and End User Search Fields
  • In-Portlet Update
• Expanded Best Bets and Top Best Bets
• Native Unified Dynamic Group Management
• Fully Web Based Object Migration
  • Recursively Add Child Objects
  • Edit Existing Packages
• Expanded Developer Features
  • Adaptive Tag Infrastructure
  • Session Preferences
  • Credential Vault
  • AJAX API
  • CSS Enhancements
  • Portlet Debugging Modes
• Management and Diagnostic Tools
  • Diagnostic Pages
  • System Health Monitor
  • Plumtree Logging Toolkit

• If an AWS is disabled and has an appropriate disabled message, the message will not be displayed when a user tries to login using that AWS. The user will receive a generic error message instead. Also, the Administrator will not be able to edit the Authentication Source whose corresponding Web service is disabled. If a Web service object for a crawler is disabled, administrators may not be able to edit corresponding datasources and crawlers. (Issue #15755)
• Mandatory portlets not listed for users in 508 mode (Issue #42952)
• When editing "User Information - Property Map", if two properties are mapped to a same User Information Attribute, a vague error message will be displayed when Finish is clicked. The message is sometimes "Unable to store the UserInfoMap information" and sometimes "Duplicate mapping found. Please map each user information element to one and only one property." The administrator must find the duplicate and resolve that before saving the Map. (Issue #16082)
• When an administrative folder containing users is copied, all objects except for users will be copied. There is no warning or error message. Users cannot be copied. (Issue #20116)
• If you create a new community group in a subcommunity, it will appear on the Security page of the subcommunity with Read access. If you then change the settings on the Security page of the parent community, these changes will be propagated down to the subcommunity (if the user chooses to propagate the changes). Therefore, if the community group was not on the Security page of the parent community, it will no longer appear on the Security page of the subcommunity. The community group must therefore be added back manually to the Security page of the subcommunity. (Issue #33288)
• The operation may fail when trying to delete a large number of objects at once. (Issue #42399)
• Dynamic Membership statements with values that contain certain characters such as a semicolon may cause javascript errors on the page. (Issue #46462)
• For portals accessed via HTTPS, the system health monitor will throw a javascript error when clicking "Finish" or "Cancel". (Issue #47893)
• The system health monitor may erroneously report that there is an issue with Process Server even if there are no issues. (Issue #49704)
• Submitting community preferences will not automatically refresh the page. (Issue #51435)
• It is not possible to edit a document's security with the security matrix if the document's id is greater than 999,999. It is still possible to edit the security of the document in the document's editor itself. (Issue #51542)

• Reference type Properties are read-only in the User Profile Editor in Assistive Technology mode. (Issue #36042)
• In Assistive Technology mode, clicking "Go Back" on the Help page from the second page of the Document Submission editor takes you to your default MyPage, rather than to the first page of the editor. (Issue #36033)
• The General Information Portlet in users' profiles may not be visible in 508 mode. (Issue #44996)
• If the community owner views the community in 508 mode, a "Create Page" link is erroneously displayed. (Issue #47764)
• Non-508 compliant portlets appear on the portlet preference pages for MyPages and Communities. (Issue #47779)
• Communities may display the "Create New Page" link when accessed in 508 mode by users who have Edit or Admin access to the community. (Issue #47764)
• The community links portlet editor may be accessible in 508 mode even though it is not 508 compliant. (Issue #47779)
• The alt tag for a submitted federated search says "ALT+F" when it is actually "ALT+S". (Issue #49345)
• Search results always clickthrough in the main window and not in a new window regardless of the Document Display Settings when in 508 mode. (Issue #51252)

• The Web crawler is unable to read the value of a META tag if it is the very last tag in an HTML document. This is unusual since META tags generally occur in the HEAD section of the document and are followed by the content of the document in the BODY section. (Issue #37143)
• If an owner of a crawler does not have sufficient access to a folder in the target taxonomy, he/she will only receive an "insufficient privilege" message in the job log if that is the only folder you can go into. (Issue #43896)
• Job logs fail to download on Solaris systems. (Issue #49252)
• Mirrored file crawlers do not properly handle NT folders that have a space as the 63rd character in the name. The name will get truncated. (Issue #50730)

• The portal stores session states in cookies. If you store many session states, this may go over the maximum number of session cookies allowed in IE and may cause some cookies such as the login cookie to be removed from the session. When developing on the portal, be careful to minimize the number of session states stored on a page. (Issue #47642)
• You cannot set or get session preferences that contain unusual characters such as "?". (Issue #47708)
• OpenLog Logging from search native API code is not enabled for AIX or Solaris systems. (Issue #49527)
• Timeout errors detection and programmatic filter disabling do not work properly with .NET Web Controls 2.1 when used with Plumtree Foundation 6.0 without modifying the .NET Web Controls configuration files. It is highly recommended that .NET Web Controls 2.2. be used instead. (Issues #47632 and 47633).
  
  .NET Web Controls 2.1 can be made to work with the Plumtree Foundation 6.0 by telling it to use any CSP version to apply the portal 5.0 filter. This can be achieved by removing/commenting out the lines which include the text ‘CSP12Condition’. For instance, remove or comment out the following line:
  

  <condition class="Com.Plumtree.Remote.Transformer.Condition.CSP12Condition"/>

  Note that this prevents the installation from working with the Plumtree Corporate Portal 4.5WS.

• If you choose to clear the status of any currently indexed item while running the database upgrade, you MUST run a search repair operation or else you will not be able to delete Knowledge Directory documents. To run a search repair operation:
  • Set the Next Repair Date in the Search Service Manager utility. You can find this utility in the portal administrative hierarchy. To schedule an immediate repair, set the date to be in the past.
  • Click Apply then Finish. Note that when you click Apply the date and time is reset for now.
  • Start any of the Search Update jobs.
• Oracle RAC does not work with the .NET version of the Plumtree Foundation 6.0.
• When you run the Portal Configuration Manager to test the DB connection on an upgraded portal installation, you must enter the DB Login password.
• You cannot bypass a proxy server for local addresses. This is because the setting <setting name="openhttp:BypassProxyForLocalAddresses"> in the file serverconfig.xml in the folder <Plumtree Install Folder>\plumtree\settings\common\ does not work at this time. (Issue #50012)
• The portal upgrade does not properly upgrade the DB password for upgraded Solaris systems. You must run the Portal Configuration Manager and re-enter the DB password before starting the upgraded portal on Solaris systems. (Issue #49509)
• Values entered in the Portal Configuration Manager will always be saved if you test the DB connection. This is true even if you click Cancel after testing the connection. (Issue #47736)
• The Portal Configuration Manager window opens too small on Solaris system. However, you can manually resize the window. (Issue #47741)
• The AdminObjectPerPage setting in the portal Config.xml file should not be set beyond 30 or you may get javascript errors when opening administrative folders. (Issue #49329)
• When upgrading from Plumtree Portal 4.5WS to the Plumtree Foundation 6.0, you are required to use DocumentumCS.pte file from the Plumtree Content Service - Documentum v.5.3 release. Migration packages from previous releases of Documentum CS fail to create the Web service. (Issue #47244)
• Some of the CSS classes have changed between the Plumtree Corporate Portal 5.0 and the Plumtree Foundation 6.0. This could cause some customizations or portlets that depend on those classes to behave differently in the Plumtree Foundation 6.0 than in the Plumtree Corporate Portal 5.0. (Issue #47594)
• The Administration link may not work correctly in Security Mode 3. If there are security issues (page cannot be accessed), a workaround is to set the AdminSiteBaseURL in x_config.xml (j_config.xml for Java portals, n_config.xml for .NET portals) to be an absolute URL (i.e. http://mycomputer.mycompany.com/portal/server.pt). (Issue #28121)
• After upgrading from 4.5WS on Oracle, the default Incoming Federated Search, 'Public Access', will not be accessible, even to Administrators. The standard test that we recommend you run in order to test your installation will therefore fail by default. (You can create a replacement Incoming Federated Search to test the WS Server that accepts another portal authentication name besides GUEST.) (Issue #28343)
• The Plumtree Foundation 6.0 no longer supports Windows Authentication to connect to MS SQL Server databases.
• The Oracle Global Deployment Scripts should not be run on the Plumtree Foundation 6.0 database as it is not supported. (Issue #27272)
• When using a non-existent parameters file for the silent install a stack trace is shown instead of a simple error message. The specific error is an InvocationTargetException. To solve this problem type in the correct, full path to the silent properties file you wish to use. (Issue #47469)
• The installer only sets JAVA_HOME in the default ignite.ini file for the Plumtree Search component. If you wish to use a different config .ini file, you must manually enter JAVA_HOME in that file. The path to the files is <install folder>/plumtree/ptsearchserver/6.0/config. (Issue #48887)
• Uninstalling Foundation 6.0 on systems that have been upgraded from 5.0.4J on Solaris will not remove the 6.0 files. (Issue #49229)
• For the UICI, you must manually specify the default install path for Linux deployments because the installer does not utilize the Linux HOME environment variable. (Issue #48499)
• If you've selected to compress your Image Service files and you want to uninstall, to restore your original IIS compression settings you must run <install folder>\uninstall\ptportal\6.0\register\bin\iiscompressionbackup.bat. (Issue #46786)
• When the portal is auto-deployed onto WebSphere, the application name is "portal". However, when the portal is manually deployed onto WebSphere, the application name is "PlumtreePortal". (Issue #40641)
• When running .NET in IIS 6.0, the AppPool Config Options should be disabled when running the Plumtree Foundation 6.0. (Issue #47702)
  
  To disable the AppPool Config Options:
  1. Open IIS Manager.
  2. Expand the Local Computer and Application Pools.
  3. Right-click on the DefaultAppPool and select Properties.
  4. On the Recycling Tab make sure that the Recycle Worker Process options are disabled.
  5. On the Performance Tab, make sure the Idle Timeout option is disabled.
  6. Click OK to save changes.
     
• The Portal Configuration Manager Utility does not work with Oracle RAC systems. (Issue #47694)
  
  You should manually change the serverconfig.xml file located in the <install folder>\plumtree\settings\common folder. To encrypt any required strings e.g. passwords, use cryptoutil.bat or cryptoutil.sh located in the <install folder>\plumtree\ptportal\6.0\bin folder.
  
  
• The Portal Configuration Manager tool will save the Database Settings if you click Test DB Connection even if you click Cancel to close the tool after testing the DB connection. (Issue #47736)
• PTConfigmanager.sh does not bring up the configuration tool in Linux. (Issue #47571)
  
  To manually correct this problem, use the following steps:
  1. Copy swt.jar and jface.jar from $PT_HOME/ptlogging/6.0/lib/java to $PORTAL_HOME/lib/java
  2. Copy libswt*.so from $PT_HOME/ptlogging/6.0/bin/native to $PORTAL_HOME/bin/native
  3. Try running ptconfigmanager.sh again
  
  You may still have an error when clicking "Test Database" on the tool.
  
  If ptapi has been installed you can also copy the jface.jar file from $PORTAL_HOME/common/container/tomcat/5.0.28/work/ptapi/localhost/ptapi/WEB-INF/lib to $PORTAL_HOME/lib/java which will correct a problem with the 'Test Database' function.
• The port number displayed in the "API Service URL" panel of the installer always defaults to 11905 regardless of the port specified in the "API Service - Application Port" panel when installing the API Service. You must manually enter the correct port number in the "API Service URL" panel. (Issue #47756)
  
  Note: You will only see the "API Service URL" panel when installing the API Service and you will only see the "API Service - Application Port" panel when installing a Portal or Administrative Portal.
  
  If you did not change the port number in the "API Service URL" panel to match the port in the "API Service - Application Port" panel, you can change it after installing the portal and running the DB scripts by going to the "Portal Settings" utility and changing the port specified in the "SOAP Server URL".
• When upgrading to Foundation 6.0 from a non-English version of a previous version of the portal, the default names of many objects will revert to English. (Issue #47877)
• When upgrading to Foundation 6.0 from a non-English version of the Plumtree Corporate Portal 4.5WS SP3, default profiles including custom default profiles will not be properly stored in the proper Default Profiles folder (accessed via a utility in v6.0) and instead will be stored in a regular administrative folder in the path \\users\<default profiles> in the language set in the 4.5WS SP3 portal. This prevents those profiles from being used as default profiles. (Issue # 47867)
  
  In order to resolve this issue, you should run the following database script:

  UPDATE PTUSERS SET FOLDERID = 3
  WHERE FOLDERID = SELECT OBJECTID FROM PTADMINFOLDERS WHERE NAME = '<localized name for Default Profiles>')

  You may need to modify the script for your particular database.

• The objects that make up the Content Upload service are named "File Upload..." when imported into the portal. You can change the names as needed. (Issue #47711)
• If you are utilizing the File Upload Web Service in the 5.0.x version of the portal, the portal installer does not properly upgrade the URL of the remote server object of File Upload Web Service to the 6.0 Content Upload Service. You must manually update the URL. In order to resolve this issue:
  1. Install the new 6.0 Content Upload Service.
     • Record the URL and port number.
     • Do NOT import the migration package to the portal. The portal objects created by this package will not be able to access previously uploaded documents because those documents will still be associated with the data source based on the old File Upload Web Service. The goal is to switch the underlying version of the upload web service that this data source uses and not replace the data source itself with a new one.
  2. Locate the old File Upload Remote Server object in the administration hierarchy of the Plumtree Foundation 6.0.
  3. Edit the remote server URL to match the URL and port number of the newly installed 6.0 Content Upload Service. This will switch the version of the upload service that the original data source object utilizes while maintaining the data source's association with previously uploaded documents.

• For the UICI, ANT_OPS and JAVA_OPTS are not set in unixvars.sh. (Issue #48519)
• For the UICI, the portaluiinfrastructure project has an invalid Default output folder for the Java Build Path. (Issue #48573)
• For the UICI on SUSE, the portaluiinfrastructure project fails to build because the PTPersonalSettingsHelper.java could not be read. (Issue #48522)
• There is a general issue that affects all applications that are deployed on an IBM WebSphere 6.0 instance that has been upgraded to 6.0.1. Upon migrating to WebSphere 6.0.1 with the IBM HTTP Server and installing the plugin, applications are not displayed on the administrative console. Restarting IBM WebSphere will start those applications even if those applications are not displayed. IBM plans a fix for this in fixpack 6.0.1.2. Please visit the IBM support site for more details.
• When upgrading to Foundation 6.0 from a non-English version of a previous version of the portal, the default names of many objects will revert to English. (Issue #47877)
• 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)
  
  The products affected are:
  
  
  • Plumtree Collaboration
  • Plumtree Publisher
  • Plumtree Studio
  • Plumtree Analytics
  • Plumtree Identity Services - LDAP
  • Plumtree Content Service - Documentum
  • Plumtree Portlet Suite - Lotus Notes
  • Plumtree Portlet Suite - IMAP
  
  To resolve the issue for all of these products except Publisher, you must update the file plumtree-bootstrap.jar on all servers that are running the affected products. The steps are:
  1. Contact support and get a newer version of plumtree-bootstrap.jar.
  2. 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/
  3. Restart the services for all products running on that particular server.
  Replacing plumtree-bootstrap.jar here will update the all products running on that particular server and allow headers up to 16KB in size.
  
  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 service.
• Uninstalling the Plumtree Foundation on a machine where the Plumtree Logging Utilities is present will cause the the Logging Utilities to fail. The workaround is to copy the \\Plumtree\common\jre\1.4.2 directory under \\Plumtree and rename it to jre142. (Issue #51543)
• For the UICI, custom .jar files should be manually put in the portal.war/ear if ALI Analytics is also installed. (Issue #51678)
• For the UICI, on Solaris configurations, the PATH environment variable may need to be modified in unixvars.sh to ensure the correct version of Java is used when editing UI customizations. This is because Solaris comes with its own version of Java. In order to resolve the situation:
  • After the UICI has completed, edit plutree_ui_source/unixvars.sh in a text editor.
  • In the line with the export PATH command, move ${PATH} to the end of the line and save the file. For example, the revised command might look like this: export PATH=/opt/apache-ant/bin:/opt/j2sdk/bin:${PATH}
  • Source the modified unixvars.sh as you normally would when editing UI customizations.

• In an exported Excel file, the time format follows the remote server's system locale instead of the client's locale. (Issue #47883)

• In the Smart Sort utility (accessible from the Administration hierarchy), checking the Check All/Uncheck All box does not properly display that appropriate check boxes have been checked. However, the check boxes behave as if they were checked. Unchecking the Check All/Uncheck All box does not uncheck the boxes under any circumstance. (Issue #47724)
• Security changes are not properly propagated for changes to the Knowledge Directory because propagation jobs are not being created. (Issue #49694)
• Media files e.g. AVI, MPEG files do not open reliably from Knowledge Directory clickthroughs. (Issue #50732)

• When creating a page layout, you receive an error if you collapse the tips after adding a portlet. (Issue #34611)
• You cannot edit the access level of a group to a subcommunity if the group has Admin access to the parent community (regardless of the group's access level on the subcommunity). To workaround this, edit the group's access level on the parent community and propagate the changes to the objects in that community. (Issue #37466)
• For portals running on BEA application servers and Windows operating systems, you cannot choose to unlink pages from a page template. While adding a new page to a community, the editor will skip the page where the inheritance is specified. The next click of "New Page" will bring up the inheritance page but it will have no affect on the page already added. When "OK" is pressed, you will receive the message, "Error - An unexpected error occurred when reposting this page." You can ignore this error and continue to add pages although you will not be able to unlink them. (Issue # 47830)

• No unresolved dependencies are reported after deleting all dependencies after uploading a package when some of the dependencies don't exist on the importing portal. (Issue #42402)
• Migrating a community links portlet does not migrate the folder of links correctly. (Issue #27145)
• The migration import utility allows the selection of a web service of the incorrect type when resolving dependencies. (Issue #42401)
• When migrating activity rights, there may be a FolderID Exception in the migration log. This can be ignored. (Issue #46079)
• The migration utility only stores 2 digits for year values. Therefore some dates may be migrated improperly if they are in the distant past or future. (Issue #46941)
• Migrating a community and its community template will not apply the header or footer from the template into the child community on the target system. (Issue #47730)
• When exporting a folder with export dependencies = true and export parent folders = false, the entire folder hierarchy is exported. It is recommended that the export parent option not be used when migrating folders or communities. (Issue #47920)
• When exporting communities with export dependencies = true, all objects stored in the community folder will be exported recursively down the object hierarchy. (Issue #47953)

• The online help menu is not expanded when accessing the help in Safari browsers. (Issue #47705)

• When a remote server is re-added to the pool of HTTP load balanced remote servers, the re-added server will get all of the requests until the load across all load balanced servers is equalized. (Issue #48430)
• Under certain conditions, if an IIS customer uses SSL between the portal and the remote tier, a CPU on a portal machine may spin to 100%, but the remaining portal CPUs still operate normally. Certain patterns of document uploads and document downloads can cause a thread to pin a CPU to 100%, while the portal remains responsive (when other threads have work to do they can still utilize that CPU). This issue is fixed in an upcoming hotfix, please contact Support for details. (Issue #47880)
• Under certain conditions, a portal running on IIS can indicate portlets are timing out when in fact they are not. If a Portlet Web Service is secured using Administrative Basic Authentication, and the password was set in a release prior to 6.0, and has not been re-set during upgrade, the RC2 decryption algorithm can in certain cases become dysfunctional under load. This will be clearly indicated in the Logging Spy if it is run while the error is produced. To remedy this, go into your Administrative screens for the Portlet Web Service, re-type the Basic Authentication password, and Save. If the issue persists, please contact Support. (Issue #47805)
• When expanding a list of users on the administration site, if there are a large number of users (i.e. 1000), the portal can respond very slowly or even timeout. This can usually be solved by optimizing the database. (Issue #27566)
• The Perfmon adaptor adds a few percentage points of overhead to overall system performance. (Issue #46230)
  
  If you see problematic slowdown with the Perfmon adaptor enabled and want to disable the adaptor, in PT_HOME\settings\serverconfig.xml, set:
  
  opencounters:perfmon-enabled to false.

• Safari 2.0 (412.2.2) does not work with the Plumtree Foundation 6.0. This is due to the security update 2005-007 v1.0 or v1.1. It is recommended that Safari users upgrade to 2.0.1 (412.5). (Issue #47659)

• If a mandatory reference property is mapped to an administrative object or a document folder, the Properties&Names page does not properly enforce that the mandatory property has a value selected. Therefore when a user is creating or editing an object with a mandatory reference property, if no value has been set for that property, no error notification will be displayed when closing the editor. (Issue #26210)
• There are no scroll bars in the help file page of AWS/PWS wizards. The workarounds are as follows:
  o If you highlight the text, you can drag the mouse down and then the rest of the text will show.
  o You can press CTRL-N to open the window in a new window, which will have scroll bars. (Issue #27920)
• If you open two editors for the same portlet at the same time in the same session, changes made in one editor overwrite changes made in the other. (Issue #34922)
• In the content source editor, some of the information, i.e. the state, is not maintained when switching between pages of the editor. (Issue #43436)
• In the Group Editor, dynamic group date conditions e.g. "date property come before..." on the Dynamic Memberships Rules page are decreased by 1 day every time the page in the editor switches away from and back to that page. (Issue #47704)
• If you set a portlet Web service to send basic authentication, you must first configure the portal to capture basic authentication information or else the basic authentication headers will not be sent. (Issue #47774).
  
  To set the portal to capture basic authentication information, go to the PortalConfig.xml file in the <portal install directory>\plumtree\settings\portal folder and set the value for the CaptureBasicAuthenticationForPortlets setting to "1" e.g. <setting name="CaptureBasicAuthenticationForPortlets"><value xsi:type="xsd:string">1</value></setting>
• CSS files will be transformed by web services even if the "Transform CSS Files" option is not checked. (Issue #50528)

• Pressing Enter on the Advanced Search page refreshes the page, but does not run a new search. Click 'Search' to perform a new search. (Issue #13773)
• The "More From Each..." link may appear at the bottom of the Federated Search results page when some of the Federated Searches do not have more results to be displayed. This is a bug. Clicking the "More From Each..." link under these circumstances may result in improper result count text, for example "Showing results 6-6 of 1", and/or it may result in the original results being repeated in the "More From Each..." page. There is no workaround for this. (Issue #28063)
• Certain federated search errors will result in an incorrect or misleading error message being displayed to the end user initiating the search. For example, a search for "*ra*" should cause the message "Specify at least three characters when wildcards appear at both the beginning and end of a query" to be displayed. Instead, the message "The Search Server for the Portal being searched could not be contacted" is shown, which is incorrect. (Issue #30234)
• You can choose to disable objects that cannot be disabled if a user object is part of the search result set. However, you are not notified that the object will not be disabled. (Issue #42546)
• When a Federated Search request to an external search Web service takes too long to complete (times out), the user sees this error message: "An error was returned by the search service: 'An Error occurred while conducting this search.'". Note that this generic message does not specify that the timeout was the cause of the failure. The first incoming federated search request to a newly started WS Server is often slow, so your first attempt to test federated search may result in this generic error. Try repeating the request; subsequent attempts should be faster. (Issue #35290)
• Snapshot Queries using "In the Last" comparison operator includes future dates in the search results. (Issue #46105)
• When sorting search results by name, the portal and Plumtree Search currently look at only the first few characters of object names. Search results, directory folder contents (in browse mode), and items listed in Snapshot Query portlets that share the same first few characters may appear out of alphanumeric order if they share the same first few characters. (Issue #47142)
• Users need at least "Select" access to the Snapshot Query object as well as the Snapshot Query portlet in order to subscribe themselves to the query mailer e.g. the "Subscribe to e-mail" link. Users who have already subscribed will not be affected. (Issue #47043)
• Users need at least "Select" access to custom properties that are displayed on Snapshot Query portlets or else they will receive an error when viewing on a portal page. Uses with at least "Select' access to customer properties displayed in a Snapshot Query portlet will not have this issue. (Issue #47593)
• Date parameters fail on snapshot query portlets with search fields if the date property is not the first property to be displayed in Netscape, Firefox, and Safari browsers. This is not an issue with IE browsers. (Issue #47548)
• Snapshot query portlets are sometimes referred to as "content snapshots" in online help and snapshot query portlet tips. (Issue #47687)

• If AllowGuestAccess is set to 0, guest users can access unsecured documents and objects. In order to properly protect data, remove the guest user from the ACL for objects. (Issue #45898)
• For portals that use Netegrity SSO, users may receive a warning when trying to join communities with an apostrophe (') in the name. (Issue #49552)
• Clickthroughs to gatewayed portlet URLs will succeed for unauthenicated users if Guest users are on the ACL of the portlet even if Guest access is disabled in the configuration of the portal in general. (Issue #50756)

• JSPortal dropdown menus cannot be opened until the page completes loading (until you see 'Done' at the bottom of the browser). Wait until the page finishes loading before using the menus or use another navigation scheme. (Issue #29933)
• Pop up pages with no content type set to text/html are not displayed correctly by the portal. (Issue #46028)
• The markup tag PT:TreeLink does not properly handle empty selections. You will receive an error if you deselect all in a tree node. (Issue #33730)

• Username/loginname can become corrupt during user import synchronization if there is a user that is missing their login name attribute. (Issue #28614)
• It is not possible to delete user profile categories using the portal UI. Clicking the Finish button after deleting categories causes a Javascript error. (Issue #47674)
  
  A workaround is to use a JavaScript debugger to simulate clicking "Finish." When editing the General Information portlet, in the popup window for Configure this Portlet, you can use a JavaScript debugger to submit the form and bypass the JavaScript problem. (Firefox with the Venkman JavaScript debugger will suffice.) Make your category deletions as desired, then launch your JavaScript debugger on the User Profile Portlet Configuration window and execute the following statements:

  document.mainform.in_hi_PostToSelf.value=2;

  document.mainform.submit();

  After the window closes, click “Finish” in the General Information portlet editor. The user profile categories will be deleted.
• Editing user profile portlet configuration and closing the browser can cause a profile page to be locked. It cannot be unlocked with the Release Item Locks utility. This can be repaired by connecting to the portal database, in the PTOBJECTLOCKS table, find and delete the row(s) with CLASSID 59. (Issue #47713)