Release Notes
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
This document contains information on the following subjects:
Note: For updated release notes, consult the BEA documentation Web site at the following URL: http://www.oracle.com/technology/documentation/index.html.
WebLogic Portal includes many powerful tools and services that make portal development and management substantially faster and easier. For an overall description of new portal features and enhancements, see http://download.oracle.com/docs/cd/E13196_01/platform/docs81/interm/whatsnew.html.
For more information on platform support, including hardware and software requirements, see the Supported Platforms page at http://download.oracle.com/docs/cd/E13196_01/platform/docs81/index.html.
This section describes problems that have been identified in this release. For each problem listed in the following tables, a problem ID is specified. These IDs enable BEA and users to monitor the status of issues while solutions are being developed. This section groups the known limitations by product area. For more information, see the following sections:
Note: Because Compatibility Domain is no longer supported, remaining issues are not applicable but are listed for reference purposes.
Table 1 describes known limitations and workarounds involving the Portal extensions in BEA WebLogic Workshop Platform Edition.
Table 2 lists the known limitations and workarounds stemming from issues involving the Administration Portal.
Content repository cannot be modified if the application is deployed as an enterprise archive (.ear). Users are not able to add, edit, or remove a content repository using the Weblogic Administration Portal when the application is deployed as an . Workaround: Before packaging your application into an EAR file, use the WebLogic Administration Portal to create any content management repositories you want to use in your application. This means creating only the root repositories, not the content nodes and content items. After you create repositories, they are registered in the Alternatively, you can deploy the application in an exploded format using a directory-based URI or shut down your server and manually edit the For information on creating repositories, see the "Add a New Repository Connection" in the WebLogic Administration Portal help system at http://download.oracle.com/docs/cd/E13218_01/wlp/docs81/adminportal/help/CM_CreateNewRepository.html. |
|
In Administration Portal deployed as an .ear, the placeholder preview does not use the correct tools webapp name, and therefore the images do not show up correctly. The placeholder preview under Interaction Management in the Administration Portal does not use the correct webapp name for image previews. It appears to use the deployed app name + "Tools". This works fine when you're running the application exploded, but if the application is deployed as an Workaround: By dropping the You can resolve this by doing the following: 2. Remove the application that was just generated and deployed (should be similar to 3. Go to 'Deploy a New Application', choose your This will give the application the same name as the tools application, and the preview will then start working. |
|
Portal Content Management Administration Portal running on HP-UX 11i requires HP JVM 1.4.1.06 or higher. The character sets used by the Portal Content Management Administration Portal are not available in earlier versions of HP's JVM. |
|
Portlet Instance Labels Change upon Update in Administration Portal -- Breaks "Listen To." Certain conditions can cause interportlet communication between two Page Flow portlets to break. Page Flow portlets communicate in a portal via the This instance label is defined by the developer in WebLogic Workshop when a portlet is placed on a page. However, if the portlet is placed on the page in either the Administration Portal or the visitor tools, it is generated by the framework (the framework uses a manipulated version of the instance ID that is based off of a sequencer). So if you place two portlets on a page in WebLogic Workshop, they will correctly communicate via the instance label that was defined by the developer. The problem arises when the portlet that is being listened to is removed and re-added from the page via the Administration Portal. This happens because when the portlet is removed from the page, the instance is deleted and when a portlet is added to the page, a new instance created with an auto-generated instance label. So now the original listening portlet is still listening to the old instance label and not the new auto-generated one. Workaround: BEA recommends that you implement interportlet communication (IPC) using the IPC model that is new in SP4. For more information, see the Interportlet Communication Guide at http://http://download.oracle.com/docs/cd/E13218_01/wlp/docs81/ipcguide/index.html. |
|
Problems might occur after creating a new BEA Content Repository and deleting the original. After creating a new BEA Content Repository in the Administration Portal using the same Connection Class as the original, if you attempt to delete the original BEA Content Repository you will receive an error: All subsequent attempts to access the old repository result in Null Pointer exceptions. Because the original repository has not been deleted, all content management queries return two copies of the same content because there are two identical repositories. |
|
Administration Portal cannot be used when used with non-default XML parsers. The Administration Portal cannot be used when the server is configured to use an alternate XML parser by setting the
and portal management functions would not be available. Workaround: Use the Administration Portal only from the Admin Server without changing the default server startup command line. Specify the setting |
|
Authentication Hierarchy Service: Tree cache is not immediately flushed and tree rebuilt upon selecting "Update & Build Tree." You may want to immediately refresh the tree after updating the Authentication Hierarchy Service configuration settings, rather than waiting for the tree to expire. Workaround: To rebuild the group tree immediately, remove the authenticator from the "Authentication Providers to Build" list within the Authentication Hierarchy Service, select "Update & Build Tree," then add back the authenticator, then select "Update & Build Tree." |
|
Content Management tools allow deleting a Content Type that is being used in a Library Service enabled repository. When working in a Library Services enabled BEA Content Repository, Content Types and Content Type Property Definitions can be deleted when associated only with Content Nodes in Draft state. If Published Content Nodes exist for the Content Type, the Content Type cannot be deleted. Workaround: If you delete a Content Type that has associated Content Nodes in Draft state, you must delete the associated Content Nodes in order to return the system to a stable state. You should not delete a type or modify its property definitions in a managed repository that has been associated with a node. You can, however, add new property definitions to the type if desired. |
|
Problem with static role creation and visitor entitlements if Admin Server is not running. When using entitlements in the Administration Portal, the first time the page is loaded several visitor roles are created/bootstrapped. If the Admin Server for the cluster is not running when this operation occurs, it will fail with an exception on the console. However, this is a one time operation, so once the roles are created and they exist when using the entitlements page, the user will not see this exception. Workaround: Make sure the Admin Server for the cluster is running the first time the Entitlements page is rendered for a Portal enterprise application. |
|
Updated Content Management Repositories sometimes hold previous repository information When Content Management repositories are modified or new ones added, there are some cases where previous repository information is not cleared out completely, leaving the repository in an unstable state. Workaround: After modifying a Content Management Repository or adding a new repository, log out and then log back in to the Administration Portal to assure that all previous repository information is cleared out and the proper settings are set for the new or updated repository. |
|
Password settings configured through the Administration Portal and persisted to the application-config.xml file can cause padding exceptions to occur upon deployment. On setting passwords through the Administration Portal, they are persisted in the application
These exceptions may incorrectly refer to a password in the Workaround: Follow the instructions for securing the administrator's login information as described at this link: http://download.oracle.com/docs/cd/E13218_01/wlp/docs81/wsrp/security.html#1003625 |
Table 3 lists the known limitations and workarounds stemming from issues involving the Portal Framework.
Table 4 lists the known limitations and workarounds stemming from issues involving the Portal search engine.
Table 5 lists the known limitations and workarounds stemming from issues involving third-party tools.
Table 6 lists the known limitations and workarounds stemming from issues involving WebLogic Portal interaction with databases.
Table 7 lists the known limitations and workarounds stemming from issues involving Compatibility Mode. Support for Compatibility Mode exists only through the SP2 release of WebLogic Portal; this limitation description is shown for reference purposes.
This section lists limitations that were fixed in WebLogic Portal Version 8.1 SP4.
Potential case sensitivity differences between Entitlements, User Profiles and Authentication Providers. |
|
Renaming the web application context causes a ServletException. |
|
JdbcSequencer lock contention occurs in a cluster, causing transaction rollback. |
|
An error occurs when SERVER_NAME is specified in the start script for a managed node. |
|
SP3 Upgrade/CM - receive error message when enabling Library Services for BEA repository in an upgraded app. This issue was resolved for SP3 and later releases but remains in SP2. For details, see Known Limitations and Workarounds in BEA WebLogic Portal 8.1 Service Pack 4. |
|
unifiedProfileTypeCache needs to be renamed in |
This section lists limitations that were fixed in WebLogic Portal Version 8.1 SP3.
This section lists limitations that were fixed in WebLogic Portal Version 8.1 SP2.
Yahoo Integration: JavaScript function required to be present for Yahoo! Content. |
|
Collaboration portlets setup instructions incomplete in WebLogic Workshop. |
![]() |
![]() |
![]() |