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 a detailed description of new portal features and enhancements, see http://download.oracle.com/docs/cd/E13196_01/platform/docs81/interm/whatsnew.html.
If you developed applications using a prior version of BEA WebLogic Portal 8.1, consult the Upgrade Guide at http://download.oracle.com/docs/cd/E13218_01/wlp/docs81/index.html for information on making your previous data and customization available to the BEA WebLogic Portal 8.1 Service Pack 3 release.
For more information on platform support, including hardware and software requirements, see the Supported Platforms page at the following location:
http://download.oracle.com/docs/cd/E13196_01/platform/docs81/index.html.
This section lists the limitations from previous versions of WebLogic Portal fixed in 8.1 Service Pack 3.
This section lists the limitations from previous versions of WebLogic Portal fixed in 8.1 Service Pack 2.
YahooIntegration: JavaScript function required to be present for Yahoo! Content. |
|
Collaboration portlets setup instructions incomplete in WebLogic Workshop. |
This section groups the known limitations and workarounds for WebLogic Portal 8.1 Service Pack 3 issues by product area. For more information, see the following sections:
This section lists the known limitations and workarounds stemming from issues involving the Portal extensions in BEA WebLogic Workshop Platform Edition.
Intermittent deployment error when building/deploying a portal application from in WebLogic Workshop to a running server |
||
When using WebLogic Workshop to build/deploy a portal application with a server running, an intermittent deployment error can occur. The symptom is one or more dialogs that say "Error Communicating with Server." This message is usually harmless, and the deployment succeeds. In some cases, a ClassCastException is also dumped in the server Administration Console log, and the deployment does not succeed. In the WebLogic Server Administration Console, the application may be listed in state "inactive" and the application deployment/removal task may be stuck in state "Running" as shown in the WebLogic Workshop status bar. |
||
If no exception is logged in the server Administration Console, then there is no problem. The deployment is successful, and the error dialog can be safely ignored. If a ClassCastException is logged in the server console, you may need to restart the server and possibly WebLogic Workshop. |
||
Make data type terminology consistent throughout the BEA WebLogic Workshop Platform Edition and the Administration Portal |
||
Data types are named differently in BEA WebLogic Workshop Platform Edition and the Virtual Content Repository in the Administration Portal. |
||
Please use the following comparison for guidance: |
||
Administration portal URL is not updated automatically if the application is renamed. |
||
By default, the standard portal web modules For example, if the application name is |
||
Update the context paths for |
||
Parse exceptions may occur in server console when duplicating user segments and content selectors |
||
When a
Once the segment or selector is opened in WebLogic Workshop, Workshop will update data inside the duplicate file and the parse exception will not occur again nor cause any problems. This is caused by the |
||
Always be sure to open the duplicate file in WebLogic Workshop to get the internal data updated. |
||
A default locale must be configured on all machines running WebLogic |
||
If a default locale is not configured on a machine, and the user running WebLogic server also does not have a default locale configured, the |
||
Make sure that a default locale is set on the machine(s) running WebLogic Server. |
||
Non-portal web applications using p13n_controls will see lots of generated EJBs in the config.xml file |
||
Portal controls are application-scoped. The controls are packaged and behave correctly for a Portal web application. However, for non-portal web applications, the user will see the individual EJBs deployed (for example, many entries in |
||
Workaround: to use Portal controls, do one of two things: 1. Create a Portal web application (recommended) 2. Create a non-Portal web application, and copy the |
||
Portlets containing Page Flows that were created with the Page Flow Wizard may affect the look and feel of a portal when the page on which the portlet is displayed is selected. |
||
Page Flows which are generated with the Page Flow Wizard create conflicting style sheet settings. These style sheets are loaded by the <netui:template> tags in the generated JSP files associated with the Page Flow. These conflicts can cause the portal to render in unintended fashion. |
||
Edit the JSP files that were generated by the Page Flow Wizard by replacing the following lines <netui-template:template templatePage="/resources/jsp/template.jsp"> <netui-template:setAttribute value="Index" name="title"/> <netui-template:section name="bodySection"> |
||
WebLogic Workshop does not merge application configuration files or deployment descriptors upon application or project import. |
||
When importing an existing portal application into WebLogic Workshop, the WebLogic Workshop will back up the old application configuration files ( The same issue occurs when you import existing Web applications ( There creation of new application configuration files and deployment descriptors causes two problems: |
||
java.sql.SQLException: Data exception -- string data right truncation on PF_MARKUP_DEFINITION DB table |
||
In WebLogic Workshop, adding portlet preferences to a portlet beyond a certain number causes an ( |
||
If you receive this exception:
Either add these preferences to the portlet via the portal Adminsitration Portal or alter the varchar size of 2 columns (
|
||
to something larger, for example:
|
||
Cannot create an entitlement using the CONTAINS operator with a user profile property. |
||
An |
||
Specifying a default value for the user profile property in Workshop will avoid this issue. |
||
Search support for Asian locales is not included in the 8.1 distribution |
||
The "WebLogic Portal Search Support for Asian Locales" package is not included with the 8.1 distribution because of its size. |
||
Download the Asian locale package from http://dev2dev.bea.com/codelibrary/code/portal_asian.jsp The files in this distribution enable Chinese, Japanese, Thai, and Korean to be indexed by the WebLogic Portal 8.1 search engine with one exception. The Japanese locale is not available on Linux platforms even after applying the Asian locale pack. |
||
Rules expressions will continue to accept 'role' even though it's been deprecated |
||
The rules manager is able to recognize 'special' objects because those have been defined in 'parser-mapping-type.properties' in the expressions package. For example, the ruleset can refer to 'role', which represents the class com.bea.p13n.entitlements.common.Role. But that class has been deprecated. The Role class is useful to the rules engine because it allows a specific object type (Role) to be identified and inspected, rather than just a String called "PortalSystemAdministrator", for example. This class will likely remain 'undeprecated' and in the public API so the rules authors could use it. |
||
Ignore the 'deprecated' attribute for the class and continue to use it until a replacement is available. |
||
Some custom layouts may not be displayed properly in the WebLogic Workshop's Portal Builder |
||
Custom layouts that are created with complex tables can cause WebLogic Workshop's Portal Builder to display the layout incorrectly. The rendered portal's layout is correct but the representation of it in WebLogic Workshop is not. |
||
Contact Weblogic Portal Support to obtain a patch for this problem. |
||
Portal will not startup in a cluster with Domain Administration Port |
||
The cluster communications used by Portal for MBeans and Datasync do not A message such as the following, followed by several stack traces, will be
|
||
Do not enable the Domain Administration Port when using Portal. |
||
Pageflow portlet refreshAction not invoked on nested pageflows. |
||
The Pageflow portlet refresh action was added to 8.1 GA and SP2 as a patch (CR129301). Unfortunately, there is a bug with Pageflow portlets that forwarded to a second Pageflow (nested or non-nested). In those cases, the refresh action continues to be invoked on the original Pageflow, not the Pageflow to which it was forwarded. In 8.1 SP3, this bug has been fixed. The refresh action will always be invoked on the current Page Flow controller. |
||
If you have a Pageflow portlet that uses the refresh action and depends on the original controller being called after a forward to another Pageflow, you will have to change your portlet to account for the correct behavior. You can avoid putting duplicate refresh actions in all your Pageflows by placing a common refresh action in |
||
The WebLogic Workshop IDE displays a green squiggle under a legitimate Struts action. |
||
A green squiggle is displayed under a legitimate Struts action in Design View of WebLogic Workshop. The squiggle is not displayed in Source View. For example, in the struts/strutsInterop sample, a green squiggle appears in the Design View of |
||
Configuration needed for a non-Portal project to serve as a WSRP producer. |
||
Currently a non-portal project does not have all the necessary files to allow it to be configured as a WSRP Producer. Additional files need to be manually copied into the project. |
||
For WSDL remote portlets, it is not required that you have a portal license. You may make jpf, jsp, and java remote portlets. Currently WebLogic Workshop requires that you have a portal project installed before allowing you to create |
||
This section lists the known limitations and workarounds stemming from issues involving the Administration Portal.
This section lists the known limitations and workarounds stemming from issues involving the Portal Framework.
This section lists the known limitations and workarounds stemming from issues involving the Portal search engine.
This section lists the known limitations and workarounds stemming from issues involving the third-party tools.
Yahoo Integration: Support of default_locale preference on Yahoo portlets. |
||
Some of the Yahoo! portlets, (e.g. Annual Reports), do not return content if that portlet doesn't support the language chosen by the user. Other portlets will return content in the default locale, en-US. |
||
Note: This locale must be a valid locale as defined in |
||
Yahoo Integration: A new window should not be launched if linking is disabled. |
||
Users who have enterprise accounts that restrict linking through the 'First Time Activation' deployment setting have no way of turning off redirection to Yahoo! from the portal on a user's first login. |
||
There is not a workaround. Any time a user logs in for the first time, they are redirected to the Yahoo! linking page. If the enterprise account is configured in 'First Time Activation' to 'Skip this page flow', the user will be immediately redirected back to the portal. |
||
After a portal with Yahoo! content has been configured (i.e. set up with portlets, Deployment name/key set up, logged in to set up anonymous user), the Yahoo! content does not show up for the anonymous user on subsequent log ins. Yahoo! content also does not show up for users who are not logged in. |
||
As of this release, Yahoo! content is not available through the portal for anonymous users (users who are not logged in). There is currently no workaround to get content to anonymous users. As a Best Practice, these portlets should be configured via entitlements to not show up unless a user is logged in so anonymous users will not see an empty Yahoo! portlet. |
||
On logout of sampleportal the has Yahoo! content, the user gets four pop-up dialogs saying they are being redirected to secure, then non-secure, then secure, then non-secure |
||
When building a custom portal that is has Yahoo! content, on login and logout there needs to be specific Yahoo parameters passed along with the login/logout (the params are yahoo_login and yahoo_logout.). Remove the hidden parameters 'yahoo_login' and 'yahoo_logout' from the |
||
My Yahoo! Enterprise Edition setup instructions are incomplete in WebLogic Workshop help system |
||
End users of the My Yahoo! Enterprise Edition portlets may experience login and other issues if only the steps in the WebLogic Workshop help system are followed. |
||
After completing the steps in the Setting up My Yahoo! Enterprise Edition topic in the WebLogic Workshop help system, perform the following steps to complete the setup: 1. Make sure your server is running. With your portal application open in WebLogic Workshop, choose Tools-->WebLogic Server-->Start WebLogic Server.
Note: In following the previous step, for the initial block called <!-- Yahoo Integration: Filter to handle login -->, copy the entire block, which includes <filter>, 4. Add the Login to Portal portlet to your portal. See the WebLogic Workshop help system "Login to Portal Portlet" topic for instructions. 5. In the Data Palette window, drag one of the My Yahoo! Enterprise Edition portlets into the portal. For example, "Company News." |
||
Yahoo! mail portlet takes a long time to deliver new Yahoo! mail messages. |
||
The Yahoo! mail portlet can take a long time to display new Yahoo! mail messages. This is in part because the Update link is broken and cannot be used (see, CR124387.) |
||
Yahoo! annual reports portlet displays no content in en_US locales. |
||
The Yahoo! annual reports portlet displays no content unless the user has set their locale to one of |
||
This is a Yahoo! issue. The only workaround is to use one of the locales that Yahoo! supports for this module. |
||
Yahoo! business publications portlet inconsistently displays custom content |
||
The Yahoo! business publications portlet inconsistently displays custom content when used in WebLogic Portal. A message from Yahoo! is displayed that says: "You do not have permission to view this premium content from more than 800 business publications. Please click the X button to remove module. If you're interested in viewing this content, please contact your portal This occurs even if the content is enabled. If the user logs out and back in the content is sometimes displayed but may not be. |
||
This is a Yahoo! issue and there is currently no workaround. |
||
Update link in Yahoo! mail portlet generates a 404 (page not found error) |
||
When using the Yahoo! mail portlet a hyperlink is generated to allow the user to manually update the list of messages in the users Yahoo! inbox. This hyperlink contains an invalid URL that generates a 404 (page not found) error when selected. |
||
This is a Yahoo! issue and there is no workaround for this problem. |
||
Yahoo! subsytem can report "ERROR: 1001" when Yahoo! account is down. |
||
The Yahoo! integration in WebLogic Portal will display an "ERROR: 1001" when Yahoo! has disabled the deployment ID used by WebLogic Portal. This is a problem on the Yahoo! servers and is not related to an issue with WebLogic Portal. |
||
The customer must contact Yahoo! support to determine when the failure will be corrected. |
||
Problems with non-English character sets in the My Mail Portlet. |
||
When using the My Mail portlet with non-English character sets, the subject and body text for some email messages is displayed incorrectly. In addition, email dates and attachments may not be displayed correctly. |
||
Domain config wizard provides install scripts for Portal server to run as a Windows service in addition to startup scripts while creating a WebLogic Portal domain, but the Autonomy Portal Search engine only starts from startup scripts. |
||
Use instsrv.exe "PortalSearchDiSH"
Note: It is recommended to leave service names as above. Otherwise, Portal Administration Portal may not recognize Autonomy Search services as running. |
||
Administration Portal in Control Panel or command line "net stop <service |
||
Mozilla based browsers sometimes render layouts incorrectly. |
||
Bugs in the code used by Mozilla based browsers (Netscape, Mozilla, Firebird, etc.) sometimes cause the widths of various layout elements to be rendered incorrectly. For example, a two column table, where column one is 30% wide and column two is 70% wide, may display with the first column taking up the entire width of the screen. This puts the second column off the right hand side of the screen, which the user can scroll to see. The problem is intermittent and unpredictable. When the page is rendered correctly, you can see the first column take up the whole width of the screen as its being rendered, but when the second column begins rendering, the first will shrink to its correct size. The problem seems to be that sometimes the first column will not shrink to its correct size when the second column begins rendering. Some bugs filed against this are (there are several more): http://bugzilla.mozilla.org/show_bug.cgi?id=217476 |
||
You can avoid the problem by first rendering two empty cells that set the width, followed by the cells with your actual content. For example:
|
This section lists the known limitations and workarounds stemming from issues involving WebLogic Portal interaction with databases.
![]() |
![]() |
![]() |