Skip navigation.

Release Notes

  Previous Next vertical dots separating previous/next from contents/index/pdf Contents View as PDF   Get Adobe Reader

BEA WebLogic Portal 8.1 Service Pack 6 Release Notes

This document contains information on the following subjects:

Note: For updated release notes, consult the BEA docume ntation web site.


What's New in BEA WebLogic Portal 8.1 Service Pack 6

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 the WebLogic Platform 8.1 Service Pack 6 Release Notes.


Location of Supported Platform Information

For more information on platform support, including hardware and software requirements, see the Supported Platforms web site.


Known Limitations and Workarounds in BEA WebLogic Portal 8.1 Service Pack 6

This section describes problems that have been identified in the Service Pack (SP) 6 release. For each problem listed in the following tables, a problem ID called a CR number 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:

New Known Limitations for WebLogic Portal 8.1 Service Pack 6

Table 1 describes known limitations and workarounds that are new for WebLogic Portal 8.1 SP6.

Table 1 New Known Limitations for WebLogic Portal 8.1 SP6 

Problem ID



Group names cannot contain spaces.

The Admin Portal does not allow creation of a group with spaces in the group name.

Platform: All


    1. Unjar portalAdmin.war.

    2. Unjar wlp-admin.jar.

    3. Open the file Go to the line containing.

specialCharsRegEx=[, '\\"<>#|&~?(){}%*]

and remove the space from the list so that the line looks like this:


    4. Recreate wlp-admin.jar.

    5. Recreate portalAdmin.war.


Performance in the Admin Portal can be slow with millions of users.

When using the RDBMSAuthenticator, performance can be slow when displaying or managing millions of users in Admin Portal.

Platform: All.

Workaround: SP6 introduces a new system property flag. Set this to true to speed up the requests for groups and users:

-Drdbms.authenticator.optimization = true


A warning is issued when redirecting to an absolute URL.

It is not supported for a remote portlet (WSRP producer) to redirect from its pageflow's begin or refresh action. Because of this limitation, WLP logs a warning message when any portlet pageflow attempts to redirect from either of these two actions. It is legal to redirect from these actions if the portlet is not a WSRP producer, however a warning is logged even if the portlet is not a WSRP producer.

Platform: All.

Workaround: The following public class and method was added to help suppress these warnings:

Class : com.bea.netuix.servlets.controls.content.PageflowLoggingHelper

Method : public static void dontLogRedirectWarning(HttpServletRequest req)

Calling this method from the pageflow begin or refresh action prior to redirect will suppress the portal framework redirect warnings.


An entitlement policy on a floatable portlet is overruled

An entitlement policy on an instance of a floatable portlet can be overruled using the .portlet version of a standalone portlet URL, and the portlet will be displayed regardless of the entitlement.

Platform: All

Workaround: Disable the Floatable state from the portlet or place the entitlement policy on the portlet's definition label, instead of placing it on the portlet instance.


Deleting a user or group in the Admin Portal does not remove the user/group profile data.

When a user or group is deleted through the Portal Administration Console, the user or group profile is not deleted from the database.

Platform: All.

Workaround: To enable the deletion of the user/group profile when the corresponding user/group is deleted, set the system property:


The default is false.

Note: It is possible to have two users/groups with the same user/group name but different authentication providers. In this case the profile will only be deleted if the user/group is deleted from all authentication providers.


Performance is slow in the Admin Portal when navigating the "Delegated Administration" tree with a large number of delegated administration roles.

When building the delegated administration role nodes calls are made to validate all components of the role, including group and user configuration. To validate the groups and users many calls are made to the security realm which can create a cumulative performance hit if there are a large number of delegated administration roles. The only purpose of these calls when building the tree is to print out a red flag next to the name of the role if a certain user or group that is configured to the role has been removed from the realm.

Platform: All.

Workaround: A switch has been added to disable the functionality which flags the DA roles. To disable the functionality, add the following system property:



A more detailed error message is needed when Authentication fails.

While using com.bea.p13n.controls.login.UserLoginControl for authenticating users, an invalid login attempt results in a P13nControlException. There is no way to display more a descriptive message.

Platform: All.

Workaround: SP 6 introduces a new system property flag called "wlp.propogate.login.exception.cause". When set to "true", the LoginException ( thrown from the WLS servlet authentication service will be bubbled up through the p13n system to the LoginControl. Subclasses of LoginException are AccountExpiredException, CredentialExpiredException, FailedLoginException.


A pageflow's begin action is always called regardless of the portlet state.

When using pageflow portlets, the begin action is always called regardless of the portlet state. For example, if the portlet's "Default to minimize" attribute is set to "true" the pageflow's begin action is called. Since a minimized portlet doesn't need to render its contents, the execution of the begin action is not needed.

Platform: All

Workaround: A new property called skipPreRenderIfNotDisplayed has been added to pageflow portlets which will instruct the framework to skip the preRender method when the portlet contents are not being displayed (e.g., minimized, or another portlet on the page is maximized). Setting skipPreRenderIfNotDisplayed will cause the preRender method to not get called when the portlet contents are not visible. The effect of this will be that the pageflow action does not get called.


After setting <generate-xml-amp-entity> to true, forwarding to new page from JPF action using PageURL does not work.

After setting <generate-xml-amp-entity> to true in the url-template-config.xml file, forwarding to new page from JPF action using PageURL does not work.

Platform: All.

Workaround: The workaround involves a new public API and a new JSP tag option:

Public API:

The following new public method is available to override the <generate-xml-entity> in url-template-config.xml:


This new method forces the form of query separators used for the URL. This overrides the natural mechanisms for determining ampersand entity or character usage based on document type and/or configuration.

The parameter passed into setForcedAmpForm:

  • true if the url should be forced to use ampersand entity ("&amp;")

  • false if the url should be forced to use ampersand characters ("&")

A code snippet of how this works with <generate-xml-entity>true:

  • PageURL postUrl = PageURL.createPageURL(getRequest(), getResponse());

  • postUrl.setPageLabel("Test_page_6");

  • postUrl.setForcedAmpForm(false); // This will use the "&" as a separator.

  • postUrl.addParameter("test","test",true);

JSP tag option:

The following JSP tags have a new tag option called "forcedAmpForm":

    1. windowUrl

    2. standalonePortletUrl

    3. pageUrl

    4. postbackUrl

    5. resourceUrl

    6. toggleButtonUrl

    7. jspContentUrl

From the TLDs:






Forces the form of query separators used for this URL. This overrides the natural mechanisms for determining ampersand entity or character usage based on document type and/or configuration. If the value 'true' is used, then "&amp;" will be the separator. If 'false' is used, then "&" will be the separator.




Cannot deploy portal application if deployer is not part of portal admin group

Portal applications cannot be deployed if the deployer is not part of the PortalSystemAdministrator group.

Platform: All

Workaround: If you are not using the MailService EJB, unjar wps.jar. In ejb-jar.xml, remove the following stanza:






If using the MailService EJB, please contact Support for a workaround.


Possible cookie conflicts when multiple producers deployed on the same HTTP server.

When a multiple producers are deployed on the same http server and each app is using defaults for cookies, the cookies will conflict when providing resources such as images and static files. JSR-168.wars imported by this tool do not change the default settings, so they can be affected by this issue if they are deployed in this manner.

Platform: All

Workaround: Explode the EAR and modify the WEB-INF/weblogic.xml file with non-default and unique session descriptor elements. Then repackage it as an EAR and redeploy.


The newly added page does not show up when a streaming desktop is duplicated.

After adding a new page to a streaming desktop using the Portal Administration Tool, if you duplicate the desktop by clicking the Duplicate button, the newly added page does not show up on the duplicated desktop. This also applies to newly added portlets and WSRPs.

Platform: All

Workaround: Duplicate a desktop using the XIP tool.


WebLogic Workshop Portal Extensions

Table 2 describes known limitations and workarounds involving the Portal extensions in BEA WebLogic Workshop Platform Edition.

Table 2 Known Limitations in WebLogic Workshop Portal Extensions 

Problem ID



Data type terminology is not 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.

Platform: All

Workaround: 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 adminPortal.war, wps-toolSupport.war (or toolSupport.war if commerce is installed in the application), and datasync.war use a naming convention for their context paths that is based upon the application name.

For example, if the application name is myApp, then adminPortal.war is at myAppAdmin, wps-toolSupport.war is at myAppTool, and datasync.war is at myAppDatasync. If you change the name of the application when deploying it from outside WebLogic Workshop, these context paths are not automatically updated to match the new application name. This can occur if the application was built as an .ear and deployed to a production machine.

Platform: All

Workaround: Update the context paths for adminPortal.war, wps-toolSupport.war (or toolSupport.war if commerce is installed), and datasync.war.

    1. In WebLogic Workshop, right-click the module.

    2. Select Edit Context Path.


From outside WebLogic Workshop, edit the META-INF/application.xml of the application.


Parse exceptions may occur in server console when duplicating user segments and content selectors.

When a .seg or .sel file is duplicated but not opened in WebLogic Workshop, the following message can occur in the server window:

<May 20, 2003 6:10:38 PM MDT> <Error> <Rules> <BEA-401004> <An error occurred par sing the rule set XML document with URI /segments/GlobalClassifications.rls. Refer to the root cause below. com.bea.p13n.expression.internal.parser.ParseException: The parsing engine has encountered a fatal error condition; see embedded exception for details. (a duplicated .sel will say 'URI /contentselectors/GlobalContentSelectors.rls').

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 <cr:name> attribute in the file not getting updated to match the file name for the duplicate file during file duplication.

Platform: All

Workaround: Always be sure to open the duplicate file in WebLogic Workshop to get the internal data updated.


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 that 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.

Platform: All

Workaround: 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">




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.

Platform: All

Workaround: 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.


Cannot fire events from Page Flow portlet refreshAction.

If you have a Page Flow portlet with a refreshAction defined and the refreshAction attempts to fire an event, the event will not fire when the refreshAction is invoked. For example, if you have the following code in your refreshAction:

PortletBackingContext ctx =
if (ctx != null)

to set the Page Flow portlet back to its normal state, the event will not be fired when the refreshAction is invoked and the portlet will not return to its normal state.

This is a limitation of the refreshAction and cannot be resolved.

Platform: All

Workaround: One way you can work around this issue is to fire events from a backing file. So you could put a backing file on the <netuix:portlet> control of the Page Flow portlet and fire events from there.


Administration Portal

Table 3 lists the known limitations and workarounds stemming from issues involving the Administration Portal.

Table 3 Known Limitations in WebLogic Administration Portal 

Problem ID



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 .ear.

Platform: All

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 application-config.xml deployment descriptor. When you create the application EAR, application-config.xml becomes read-only and cannot be modified within the EAR. That is, you cannot add or remove repositories in the WebLogic Administration Portal when the application is in an EAR file.

Alternatively, you can deploy the application in an exploded format using a directory-based URI or shut down your server and manually edit the application-config.xml file in the ear.

For information on creating repositories, see the "Add a New Repository Connection" in the WebLogic Administration Portal help system at


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 .ear to an application name other than the original name, the image preview link uses the wrong application name, and the image is not found.

Platform: All

Workaround: By dropping the .ear in a running server, the Application Name is generated, and is different from the name of the .ear file.

You can resolve this by doing the following:

    1. Open the WebLogic Server console.

    2. Remove the application that was just generated and deployed (should be similar to '_appsdir_earFileName_ear').

    3. Go to 'Deploy a New Application', choose your .ear file, and give the application the same name as the .ear file.

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 or higher.

The character sets used by the Portal Content Management Administration Portal are not available in earlier versions of HP's JVM.

Platform: HP-UX11i with JVM

Workaround: Use HP 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 listenTo property defined on a portlet definition. This listenTo property specifies the instance label of the portlet that it is interested in listening to.

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.

Platform: All

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://


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: "-Error removing the Repository".

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.

Platform: All

Workaround: Restart the server.


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 -Djava.endorsed.dirs property to the server startup command line. For example, when open SAML based Identity Asserter is being configured, that requires the -Djava.endorsed.dirs, the Administration Portal would throw the following exception after login:

and portal management functions would not be available.

Platform: All

Workaround: Use the Administration Portal only from the Admin Server without changing the default server startup command line. Specify the setting -Djava.endorsed.dirs only on the managed servers.


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.

Platform: All

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.

Platform: All

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.

Platform: All

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.

Platform: All

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 META-INF/application-config.xml file. After building a portal .ear file in a development domain and deploying into a new domain on the same machine or different machines, padding exceptions will occur during deployment. The exception that appears upon deployment is similar to the following:

<Dec 20, 2004 8:59:45 AM EST> <Error> <WSRP-Consumer> <BEA-420731> <Exception [ - with nested exception:
[com.rsa.jsafe.JSAFE_PaddingException: Could not perform unpadding: invalid pad byte.]] thrown while trying to do task [handleTimerNotification] in class [].
com.rsa.jsafe.JSAFE_PaddingException: Could not perform unpadding: invalid pad byte.

These exceptions may incorrectly refer to a password in the config.xml file.

Platform: All

Workaround: Follow the instructions for securing the administrator's login information as described at this link:


Can't add proxy content error page via The Administration Portal

The WebLogic Administration Portal does not provide the ability to add a proxy content error URI for WSRP portlets.

Platform: All

Workaround: Service Pack 5 provides a skeleton-wide default error page for proxy portlets, at /skeletons/default/proxyportleterror.jsp which will be used by the framework as a default for rendering errors for proxy portlets. You can still override the error page for each portlet. If that is missing, the framework will try to render the skeleton-wide page, and if that does not exist, it will render directly to the servlet response.


Cannot change a password in the Administration Portal using Microsoft Active Directory Server. 

When using Microsoft Active Directory Server, attempting to change a password in the Administration Portal results in an error: "This operation is not currently supported....".

Platform: All

Workaround: Use WebLogic Console to change these passwords.


Portal Framework

Table 4 lists the known limitations and workarounds stemming from issues involving the WebLogic Portal Framework.

Table 4 Known Limitations in WebLogic Portal Framework 

Problem ID



Credential MBean does not have a tool for editing. The CredentialMBean was added to application-config.xml so that services requiring a plain-text password do not have to store the password on the file system in an unencrypted form.

The CredentialMBean has an encrypted "Credential" attribute that is automatically encrypted/unencrypted when the ApplicationConfigurationMBean (the parent MBean) is persisted/read.

Platform: All

Workaround: As is, the CredentialMBean requires a workaround to be used:

    1. Edit application-config.xml by hand to add a Credential.

    2. Use the Administration Portal to make a change to some other MBean. This causes an ApplicationConfigurationMBean.persist().

    3. Change the value that you changed in step 2 back to what it was.

Because the persist() method was called, your plain-text credential is now encrypted.

The MBean looks like this:

<Credential Name="LdapPropertyManager"



"<" and ">" characters not rendered correctly when used in Portal titles.

The "<" and ">" characters, when used in titles of Portal objects such as pages and portlets, do not render correctly in a browser because they are special characters that are interpreted and processed rather than displayed literally. The result is that you will not see these titles displayed in the browser.

Platform: All

Workaround: You can display these characters if you escape them; that is, you enter "&lt;" for "<" and "&gt;" for ">". If you do this, your title will appear in the tools as, for example, "&lt;Title&gt;", but it will display in the browser as "<Title>".


Deleting WSRP producers that were created in the IDE leaves .portlet files that are unusable.

If the producer is added in the IDE, .portlet files are generated for the proxy portlets. When the producer is later deleted, the proxy portlet no longer is listed in the Portal Management list of available portlets, but the .portlet file still exists. This leaves a .portlet file that cannot be used due to the fact that the producer was deleted, and if viewed in the .portal gives an invalid registration handle if rendered, and if added to a desktop is not seen.

Platform: All

Workaround: Delete the file manually.


SP2 Upgrade/CM - receive error message when enabling Library Services for BEA repository in an upgraded app.

This limitation was fixed in SP3 but remains applicable for SP2.

When a user upgrades from 8.1 SP2 to 8.1 SP4 or SP2 to SP3 and tries to upgrade their repository to be a managed repository, the following error occurs: "Error getting cache: nodePathCache.BEA Repository".

Platform: All

Workaround: Although the error message appears, Portal still creates the nodePathCache internally. The only drawback is that you cannot modify the settings of the cache (ttl, size, and so on). If you want to do that, add the correct entry to the app-config.xml and redeploy the application.

The entry you will have to add is as follows:

<Cache MaxEntries="50" Name="nodePathCache.<repositoryName>" TimeToLive="6000"/>


Receive wsrpKeystore.jks at startup.

The wsrpKeystore.jks file is required by WebLogic Portal for WSRP features.

The configuration wizard places this file in the admin server's domain directory (one directory above the server root directory).

The WebLogic Portal WSRP features require this file to exist at this location (one directory above the server root directory). So in a configuration wizard-generated admin server domain, everything works as it should. But in some other cluster configurations, such as when using NodeManager, whenever the server root directory is overridden, or a domain is created without using the configuration wizard, this file may not exist in this location. In this case, a warning and an exception are reported during server startup.

The error symptom is the appearance of messages during server startup of the following form:

<Apr 26, 2004 3:10:26 PM MDT> <Warning> <WSRP-Security> <BEA-420802> <There was a problem initializing the identity assertion token provider.>

<Apr 26, 2004 3:10:34 PM MDT> <Info> <Security> <BEA-090093> <No pre-WLS 8.1
Keystore providers are configured for server mC for security realm myrealm.>

and wsrpKeystore.jks (The system cannot find the file specified)

Platform: All

Workaround: Copy the wsrpKeystore.jks file to the server domain directory. Copy the file from a domain that was created with the Configuration Wizard.


NullPointerException during deploy after retargeting.

A NullPointerException is displayed on the server console and log for a WSRP consumer web app on trying to deploy the containing application after the latter's target server/cluster has been changed. This exception does not adversely affect any functionality and can be ignored.

Platform: All

Workaround: None


Servlet response wrappers with custom outputstream/writer cannot be used to render portal/desktops.

If you are using a servlet filter with a response wrapper to filter portals or desktops, and if the response wrapper overrides the getOutputStream() and getWriter() methods to return custom javax.servlet.ServletOutputStream and objects, you may encounter java.lang.IllegalStateException.

Platform: All

Workaround: Render the content that must be filtered in an IFRAME or a separate browser window.


Portal file caching logic does not work for archived webapps when pageCheckSeconds is set.

WebLogic Portal has the capability to cache the internal representation of a .portal file, which speeds up portal requests. However, this logic does not work if both the webapp is deployed as archived and pageCheckSeconds in weblogic.xml is set to a positive value.

Platform: All

Workaround: Set the value of pageCheckSeconds in weblogic.xml to -1. This can be a wise thing to do in any case for production mode deployments, as it removes the stale checks for JSP pages.


LdapPropertyManager throws ConfigurableEntitySystemException when credentialMBeanName is uncommented.

When configuring the Unified User Profile for LDAP, the LdapPropertyManager throws the following exception:

" Error reading ldap configuration".

Platform: All

Workaround: The LdapPropertyManager configuration in the p13n_ejb.jar ejb-jar.xml file was enhanced to permit encryption of the LDAP connection password. The credentialMBeanName environment entry is uncommented by default. If an encrypted password is not needed, comment the section.

A sample of the commented section would appear as:

<!-- env-entry >
<description>The name of the Credential MBean in application-config.xml that will be used to store the principal's
username and principal's password.
The password will be stored in an encrypted form. This is the
principal/credential used to bind to the LDAP server. The password
will be decrypted before it is used to bind to the LDAP server.
Using this entry will override anything set for the config/principal and config/principalCredential. If this entry and config/principal
and config/principalCredential are not specified then anonymous
bind will be used.

(this entry is optional)</description>
< /env-entry

Should an encrypted password be required, leave the section uncommented and place an additional LdapPropertyManager Credential section in the META-INF/application-config.xml file:



Portlet wizard and Generate Portlet allow portlet types that are not valid for the webapp.

It is possible have a webapp that has just WSRP-Producer installed in and not the full set of portal libraries. In those webapps, you can create new .portlet files, either via the New|File|Portlet menu item or the Generate Portlet right-click menu. Both actions will open the portlet wizard window. There, all of the possible portlet types (jsp/html, page flow, java, struts, and remote) will display and allow you to select them. However, only page flow and struts portlets will work in a WSRP Producer-only webapp.

Platform: All

Workaround: Don't select jsp/html, java, or remote portlets in WSRP Producer-only webapps.


forkRender portlets that include JSPs from a different webapp may behave inconsistently.

Due to thread safety issues regarding the root ServletRequest's context classloader, JSPs that are included from within forkedRenderPortlets that are in different webapps than the portlet may exhibit execution problems due to the incorrect context ClassLoader being in place.

Platform: All

Workaround: Either do not include JSPs from different webapps from forkRender portlets, or do not use forkRender with portlets that include JSPs from different webapps.


Document Structure tab malfunction when working with Look And Feel files.

When working with a Look And Feel, the Document Structure tab can malfunction, causing the CSS class names and their attribute values to cease to render in the Document Structure tree. This happens very infrequently, but does render the Document Structure tab unusable.

Platform: All

Workaround: Close and reopen the Look And Feel file (*.laf), and the Document Structure tab will return to normal.


Exceptions/warnings thrown when the float button is on a portlet that is part of a desktop.

When a user clicks a float button on a portlet that is part of a desktop, the following error message will be logged:

<BEA-423162> <One or more validation error(s) occurred during parsing /test.portlet. The error(s) were error: The document is not a root@ document element namespace mismatch expected

"";; got "";;.>

Platform: All

Workaround: None. This message can be ignored.


render:standalonePortletUrl tag creates incorrect link when a portlet using this link is consumed by a remote portal.

The render:standalonePortletUrl tag is used for creating a link that, when clicked, renders the portlet in a new browser window. However, when you host a portlet using this tag on a producer, and then consume this portlet in a remote portal, the link will not open the portlet in its own browser window.

Platform: All

Workaround: The workaround involves creating a backing for the remote portlet created on the consumer side, and some custom code within the portlet JSP. Here are the steps:

a. Create a backing file for the proxy portlet.

b. In the preRender() of the backing file, add the following code:

StandalonePortletURL url =
StandalonePortletURL.createStandalonePortletURL(request, response);
SimpleStateHolder state = new SimpleStateHolder();
state.addParameter("my_url", url.toString());
request.setAttribute(MarkupRequestState.KEY, state);

c. In the JSP on the producer side, use the following instead of

render:standalonePortletUrl tag to generate a link to float the portlet

SimpleStateHolder state = (SimpleStateHolder)
String url = (String) state.getParameter("my_url");
<a href="<%=my_url%>">Click</a>


Producer data and remote portlets might become unusable if the producer environment is changed to a different location.

When you add producers and create remote portlets, the producer registry (WEB-INF/wsrp-producer-registry.xml) and the portal framework database tables will contain the address (producer's WSDL address, and addresses of various ports described in the producer's WSDL) of the producer stored. If you move the producer from one environment from another, this data stored may become invalid. If this happens, you might not be able to use those portlets as the producer cannot be contacted at the old location.

Platform: All

Workaround: You can update the database entries by using the This API provides methods to obtain and update producer information.


Portal upgrade doesn't work with WSRP Producer-only webapps.

When upgrading from Service Pack 3, WSRP Producer webapps don't automatically have their libraries updated to Service Pack 4. This can cause problems when attempting to communicate to the webapp from the Portlet Wizard or other services.

The normal portal upgrade path, via the Install|Update Portal Libraries at the application level, will not correctly detect non-portal webapps that have WSRP Producer installed. Additionally, reinstalling WSRP Producer to the webapp will not update the library files.

Platform: All

Workaround: Copy the following files into your webapp WEB-INF/lib directory:


<beahome>/weblogic81/portal/lib/netuix/system/ext/web/struts-ad apter.jar

<beahome>/weblogic81/portal/lib/netuix/system/ext/web/struts-ad apter-html.tld

<beahome>/weblogic81/portal/lib/netuix/system/ext/web/struts-ad apter-naming.tld

<beahome>/weblogic81/portal/lib/netuix/system/ext/web/struts-ad apter-nested.tld

<beahome>/weblogic81/portal/lib/netuix/system/ext/web/struts-ad apter-tiles.tld


<beahome>/weblogic81/portal/lib/wsrp/adapters/wsrp-jpf-adapter. jar

<beahome>/weblogic81/portal/lib/wsrp/adapters/wsrp-struts-adapt er.jar

Redeploy the WSRP Producer webapp, if your server is running.

You will need to upgrade the other parts of your application normally.


onDeactivation portlet events for non-visible portlets may not work with portal tree optimization turned on.

When the "tree optimization" flag in a .portal file is turned on, not all non-visible portlets for a given request are processed. (A non-visible portlet is one that lives on a page that is not displayed for the given request.) This can be a problem if you are trying to catch an onDeactivation event for a portlet — once the portlet has been deactivated, it is no longer visible, and so the system doesn't process it to fire its deactivation event.

Platform: All

Workaround: The safest alternative is to set tree optimization to false for the portal in question. However, if you need tree optimization you can perform this workaround: for each portlet that you want to catch deactivation events for, define a dummy event handler (for example, create a custom event handler with event = "[some arbitrary string]" and set the property "Only If Displayed" to false. This will force the system to process the portlet whether visible or not.


Portlet preferences may not be reloaded from .portlet files by default.

Prior to Service Pack 4, when the server was bounced or redeployed, the preferences in the .portlet file always overrode the preferences in the database, so administrator additions and changes to any portlet preferences were lost on a server restart.

A new option allows you to control the way in which portlet preferences are reloaded on server restart. You implement this control using the "master" attribute on the "propagate-preferences-on-deploy" element in the WEB-INF/netuix-config.xml file.

Possible values for the master attribute are:


Provides the same behavior as in previous versions. The preferences in the file system always take precedence. To preserve existing behavior, select this value.


In the case of a restart, the values in the database always takes precedence. In the case of a first time startup, the database is seeded from the .portlet files.


The default behavior if the attribute is missing. The .portlet preferences are merged with the database preferences, with the database values taking precedence over the .portlet file's values.

The following example shows the element with an attribute value of both:



<propagate-preferences-on-deploy propagate-to-instances="true"
both"/> <reload-database-on-redeploy reload="false"/>


WebLogic Portal 8.1 SP4 - 'Return To Default Page' attribute on Books not working properly when tree optimization is on

When a Book's 'Return To Default Page' attribute is set to true, the portal should display the Book's default page when the Book is the target of a navigation URL. This is not happening.

Platform: All

Workaround: This CR only addresses the nesting of books where the immediate children of the Main Book are books and the return to default only applies when moving between books, not within books. Here is a simple portal hierarchy where each page has a portlet that contains a URL to Book2.

     Main Book - Book 2 is the default book for the main book

          Book 2 - Return To Default = true with default page = Page 2

               Page 2

               Page 3

          Book 3

               Page 4

               Page 5

When the above portal is rendered, Book 2 and Page 2 are displayed.

1. The user clicks on Page 3, moving off of the default page

2. The user clicks on Book 3 (which results in Page 4 being displayed and moving into a different book).

3. The user clicks on the URL for Book 2 and Page 2 is displayed

This works as expected as Page 2 is the default for Book 2 and the last active page in Book2 was Page 3.

When the above portal is rendered, Book 2 and Page 2 are displayed.

1. The user clicks on Page 3, moving off of the default page

2. The user clicks on the URL for Book2 and Page 3 is displayed

The reason for this is because Page 3 is within the same book and therefore, the return to default is not applied.

CR218066 (Continued)

In the following hierarchy where pages are the children of the main book, the Return to Default feature does not apply.

     Main Book - Page 1 is the default page for the main book

          Page 1

               Book 2 - Return To Default = true with default page = Page 2

                    Page 2

                    Page 3

                    Page 6

              Book 3

                    Page 4

                    Page 5

Using the above hierarchy, the user is returned to the last active page in Book 2.


Campaign - if an error exist in the campaign schema (goals), ensure the exception makes it to the console.

In creating a camping with goals, Workshop does not generate the entire XML required by the xsd. The following needs to be added manually:

<ca:ad-id xmlns:ca="";>


When the customer has not manually added this line, an exception is thrown, but it does not surface on the console. This is very misleading in that the goals do not take effect.

Platform: All

Workaround: None


The RDBMS Authenticator is not supported for XA drivers, Multipools and Driver level load balancing

If you put a XA driver, Server will not boot up.

Platform: All

Workaround: Use a non-XA driver for the RDBMS Authenticator; load balancing is not supported.


Provide a default content repository choice in CM tags

In WebLogic Portal 7.0 there is a "contentHome" parameter available in the Content Management tags that allows you to specify which content repository to use for a query. In WebLogic Portal 8.1, this parameter is available in the Java API (for example, the homeName parameter in ContentHelper), but was deprecated and is ignored in the JSP tags.

In addition, the tags do not provide the ability to specify a content repository to search if no repository parameter is specified; the default behavior is to aggregate across all repositories.

Platform: All

Workaround: Portal 8.1 Service Pack 5 added an optional parameter called "searchPaths" to the <pz:contentQuery> and <cm:search> tags. This parameter can be used to specify a specific repository to use for the content query. Service Pack 5 also adds the ability to set a comma-delimited, default list of search paths, using the "" system parameter. If present, this is used by the <pz:contentQuery> and <cm:search> tags when the "searchPaths" parameter has not been specified in the tag.


Commerce component Price Engine putting high pressure on database

When a discount is used, its use count is incremented in the database. For unlimited use discounts, a customer may not be interested in tracking the number of uses.

Platform: All

Workaround: Set the System Property to turn off tracking of usage counts for discounts whose usage limit is "UNLIMITED".


More Datasync repositories being created when application hit for the first time.

The Rules repository is not initialized until a rule the first time it is accessed. This initialization process can be time consuming and the application is unavailable during this time.

Platform: All

Workaround: Change the descriptor for the RulesetPersistenceManager EJB from




This will cause the Rules repository to initialize at server startup.


Mandatory pages can be deleted by users

In WebLogic Portal 7.0, the portal administrator had the ability to set a page attribute of mandatory to prevent certain pages from being removed as a result of a user's customizations. In WebLogic Portal 8.1, this functionality is not directly available because users can now utilize visitor tools to remove any pages to which they are entitled

Platform: All

Workaround: To achieve similar functionality to that of WebLogic Portal 7.0, you can use the removePlaceable() method in the PortalCustomizationManager interface to prevent a user from deleting a mandatory page. Keep the following considerations in mind if you plan to use this implementation to enforce mandatory pages:

You must set at least one entitlement per page. When a page is created, no entitlements exist and the default is to grant all privileges on that page. The removePlaceable() method checks for the UPDATE entitlement on the page that contains the book or portlet being deleted.

Because the SP5 Visitor Tools code calls into the PortalEntitlementHelper class, it is recommended that you use this class as the means of obtaining the entitlements for a page:

boolean isAllowed = PortalEntitlementHelper.checkPageDelete(new

CustomizationContext(request.getLocale(), request), <page_definition_id>)

This would require that you make the call, and then add a check in the Visitor Tool code to branch, based on the outcome of this call.

A future release will provide a more robust means of accomplishing this task.

For more information on the PortalCustomizationManager interface, see the WebLogic Portal Javadoc at


Description PortalContextAdapter ignores threadSafe attribute.

The threadSafe attribute is treated as always "true" for remote portlets, even if it is set to false in the portlet.

Platform: All

Workaround: None


"Verbose log could not be set, parent folder does not exist" errors occur using the Propagation Tool.

The default setting for the oamDataFilesystemPath element in the web.xml for the propagation.war is d:/propagation/81xDomain/inventories. If a D: drive does not exist, exceptions will be thrown similar to the following:

<Error> <InventoryServices> <machinename> <portalServerFrom> <ExecuteThread: '13' for queue: 'default'> <weblogic> <> <000000> <Verbose log could not be set, parent folder does not exist. logFile: d:\propagation\81xDomain\inventories\view_verbose_D13_H9_M42_S34.log>

These exceptions will be thrown at the following times:

  • Exporting the Application Inventory, when using the Zip file name (with full path) option on the Export Application Inventory screen

  • Importing the Application Inventory, when using the Specify the file option on the Select Import Source for Inventory screen.

Platform: All

Workaround: Change the oamDataFilesystemPath setting in the propagation.war's web.xml file to an existing drive.

On a Windows system, it could be changed such as:




<description>Base folder path for runtime data, such as inventory exports.</description>


On a UNIX system, it could be changed such as:




<description>Base folder path for runtime data, such as inventory exports.</description>



<cat:catalogSelector> tag does not work after enabling commerce services for a Portal application.

When enabling commerce services to an existing Portal application, not all the files needed to utilize the <cat:catalogSelector> tag are available as part of this installation. The code expects for find a GlobalCatalogSelectors.rls file located in <application>/META-INF/data/catalogselectors/GlobalCatalogSelectors. Also, there is no tooling for creating the GlobalCatalogSelectors.rls file in the 8.x line.

Platform: All

Workaround: The following is an example of a working GlobalCatalogSelectors.rls file for reference.

<?xml version="1.0" ?>

<cr:rule is-complete="true"










xmlns:xsi="" xsi:schemaLocation=" rules-core-2_1_1.xsd rules-extensions-2_1_1.xsd">


<cr:description />

CR236023 (Continued)





<wlcs:now />










<wlcs:expression>price &gt; 50</wlcs:expression>







Enabling preRender Forking on Pageflow portlets causes a failure to render content.

A new feature in 8.1 SP5 allows the preRender life cycle phase in portlets to be executed in a separate thread. This is also referred to as preRender forking (see e-docs for details). As of the Service Pack 5 release, this feature was not working correctly for Pageflow portlets. If preRender forking is enabled for a Pageflow portlet the portlet's content will fail to render. That is the portlet frame and title bar (if present) will render but content will not. This issue is being resolved and a patch will be posted under this CR as soon as it is available.

Platform: All

Workaround: Do not use preRender forking in Pageflow portlets.


In 8.1 SP6, Content Query expressions are generated incorrectly due to an order of precedence problem.

In the following expression: (a && (b || c), this gets evaluated/executed as (a && b || c). The order of precedence is not maintained when executing a Content Query expression.

Platform: All.

Workaround: This problem was fixed in 8.1SP6 such that the order of precedence is now maintained when executing a Content Query expression. A system property was added to disable this fix so that the expression is evaluated the same as in 8.1 Service Pack 5 or earlier:



Request parameters are no longer implicitly propagated from one WSRP request to the next.

This issue impacts only customers with a patch for CR 254373.

Prior to the fix for CR254373 the portal framework would add all request parameters to the WSRP navigationState url automatically. This was a violation of the WSRP specification and also caused a problem because the url could get too large. CR254373 removed this bug but it caused a common use case that some users had with pageflows to fail once the fix was supplied. The use case entails submitting a form to a pageflow action, the action forwards to a result.jsp that then displays the form contents by pulling them out of the request. This will work in a standard pageflow but fails when the pageflow is accessed via a WSRP consumer portlet because the submission of the form and the follow up display of the results requires two requests from the consumer to the producer (although it still appears to be a single request from the stand point a user interacting with the consumer). Submission of the form from the consumer to the producer is handled by a performBlockingInteraction() call. When that call completes the consumer then follows up with a getMarkup() request to the producer that returns the markup for the result.jsp page. However since the request parameter are not implicitly propagated from one request to the next the form parameters are no longer present when the getMarkup() request is processed. The pageflow example noted above is one way to demonstrate this issue but it applies to any case where a performBlockingInteraction() call is made.

Platforms: All.

Workaround: This is not really a workaround, but rather the proper way to implement this functionality. Implementers simply need to explicitly propagate the parameters they wish to keep in the request. Referring back to the pageflow example described above there are two simple solutions that could be used to fix the implementation. In the first solution the pageflow action that receives the submitted form can simply pass it along by explicitly including the form in the Forward object that is returned by the action. This can be done using a netui ActionForm object or individual parameter name value pairs can be included as pageInputs in the Forward object. The results.jsp should then retrieve the items in a manner suitable to method used. Another possible solution is for the pageflow to hold onto the desired parameters as part of its state. That is the action that receives the form retrieves the parameters of interest from the ActionForm or request, assigns the values to instance variables and provides access to those value through getters on the pageflow. The result.jsp can then access the values need using those getters.



Table 5 lists the known limitations and workarounds stemming from issues involving the Portal search engine.

Table 5 Known Limitations in WebLogic Portal Search Engine 

Problem ID



How to start Autonomy search engine as a Windows service.

The domain configuration 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 engine starts only from startup scripts.

Platform: Windows

Workaround: Use the instsrv.exe utility from Windows Resource Kit Tools (a free download from the Microsoft web site) to install Autonomy executables as a Windows service.

Installation steps:

    1. Make sure instsrv.exe is available from your PATH environment.

    2. Open a command shell and enter the following commands:

instsrv.exe "PortalSearchDiSH"

<WLINSTALL_HOME>\portal\thirdparty\search\windows\DiSH\PortalSe archDiSH.exe
instsrv.exe "PortalSearchDRE"

<WLINSTALL_HOME>\portal\thirdparty\search\windows\DRE\PortalSea rchDRE.exe
instsrv.exe "PortalSearchAutoIndexer"

<WLINSTALL_HOME>\portal\thirdparty\search\windows\AutoIndexer\P ortalSearchAutoIndexer.exe
instsrv.exe "PortalSearchHTTPFetch"

<WLINSTALL_HOME>\portal\thirdparty\search\windows\HTTPFetch\Por talSearchHTTPFetch.exe

Note: It is recommended to leave service names as above. Otherwise, the Administration Portal might not recognize Autonomy Search services as running.

Steps to uninstall:

    1. Stop running Autonomy Search Services by using either the Windows Administration Portal in Control Panel or the command line net stop service_name command.

    2. Make sure instsrv.exe is available from your PATH environment.

    3. Open a command shell and enter the following commands:

instsrv.exe PortalSearchDiSH REMOVE

instsrv.exe PortalSearchDRE REMOVE

instsrv.exe PortalSearchAutoIndexer REMOVE

instsrv.exe PortalSearchHTTPFetch REMOVE


Third-Party Tools

Table 6 lists the known limitations and workarounds stemming from issues involving third-party tools.

Table 6 Known Limitations in WebLogic Portal Third-Party Tools 

Problem ID



IE6 limitation on the maximum number of CSS files.

Internet Explorer6 SP1 has a limit on number of CSS files that can be used in a Portal. The maximum number of CSS files that can be used in a portal is 35. If the number is more than 35, IE doesn't display the portal properly. The CSS files are used in developing various skins for a portal.

Platform: All

Workaround: If there are more than 35 CSS files, you should organize the contents of all CSS files into fewer than 35 files.

If you merge contents of multiple files, make sure that CSS class names are unique across all CSS files within a webApp; this is an IE requirement.

If there are two CSS classes with same name in two .css files and both classes are used in a portal, the CSS class from .css file that is loaded first (by IE) will be used.


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 e-mail messages is displayed incorrectly. In addition, e-mail dates and attachments might not be displayed correctly.

Platform: All

Workaround: None. Please contact Support for an update on this issue.


AutoIndexer does not remove entries from the DRE for documents that have been deleted from the file system.

In order for AutoIndexer to remove entries from the DRE for documents/files that have been removed from the file system directory being indexed, the AutoIndexer job must be configured with a POLLINGACTION attribute of 7 or 8 (see the Autonomy AutoIndexer documentation).

However, if you use a relative path in your DirectoryPathCSVs attribute rather than a fully qualified directory specification, the entries will still not be deleted from the DRE even with POLLINGACTION set to 7.

Platform: All

Workaround: Update the DirectoryPathCSVs to specify a fully qualified directory path rather than a relative path.


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 across the entire width of the screen. This puts the second column off the right hand side of the screen, which the user must 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):

Platform: All

Workaround: 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:


<td width=30%>&nbsp;</td>

<td width=70%>&nbsp;</td>



<td><!-- Actual Content --></td>

<td><!-- Actual Content --></td>




Table 7 lists the known limitations and workarounds stemming from issues involving WebLogic Portal interaction with databases.

Table 7 Known Limitations in WebLogic Portal Database Interactions 

Problem ID



JMS prefix of 'cajun' or 'null' causes JMSState and JMSStore tables not to be created.

ORA-00942 errors on JMS JDBC store errors may occur during server startup if the database user has 'SELECT ANY TABLE' permissions. This permission may have been granted to the database user if the customer used a Portal supplied create_user.sql script to create the database user from a prior release (4.0/7.0) of Portal.

Error Text Example:

<May 14, 2003 5:00:13 PM MDT> <Alert> <JMS> <BEA-040052> <JMSServer "cgJMSServer" store failed to open java .IOException: JMS JDBC store, connection pool = <portalPoolOra>, prefix = <cajun>: change state java.sql.SQLException: ORA-00942: table or view does not exist

Platform: All

Workaround: Revoke the 'SELECT ANY TABLE' permission from the database user. Login to SQLPlus as a user with DBA privileges and to revoke these permissions from the database user. Example:



Integrity constraint errors may be encountered when adding content management nodes.

"java.sql.SQLException: ORA-02291: integrity constraint (DB.FK1_CM_NODE) violated - parent key not found" errors may be encountered when adding content management nodes to an Oracle 8.1.7 database that is not at the proper patch level

Platform: Any with an Oracle 8.1.7 database

Workaround: Check the version number of your Oracle database instance. If the version of your database is lower than you need to obtain the patch set from Oracle and upgrade your database to this patch set. If you are using SP2 and Oracle 9i, you need to upgrade Oracle to

For Oracle databases in a Windows environment, Oracle version or higher is recommended.


ORA-22866 may occur when creating database tables.

"ORA-22866: default character set is of varying width" errors will be raises when database tables are created in an Oracle 8.1.7 UTF database instance whose compatible parameter is set lower than 8.1.0. See Oracle Doc ID: Note:112531.1 for additional information.

Platform: Any with Oracle 8.1.7

Workaround: The compatible parameter for your database is set to 8.0.5 (or lower). Edit the init.ora parameter file with a compatible parameter of 8.1.0 or higher.


Need to set configuration to send campaign e-mails with Sybase.

The standard SQL used by the MailService to send batched e-mails is not supported in Sybase.

Platform: Sybase

Workaround: To send e-mails with mailmanager.bat and/or use MailService.sendBatch() and MailService.getMessagesInBatch() with Sybase, you need to set EnableOrderByWorkaroundForClobs to true on the MailServiceMBean.

This can done by editing META-INF/application-config.xml (while the application is undeployed or server not started). For example:

<MailService Name="MailService" SMTPHost="SMTPHost" EnableOrderByWorkaroundForClobs="true"/>

Remove that flag or set to false for any other database, which is the default configuration.


Error adding binary property on node, or binary property choice on node type may be encountered.

Adding binaries to a node, or node type choice using an Oracle database without using the proper driver may fail.

Platform: Any with an Oracle database and a non-certified BEA WebLogic Portal Driver

Workaround: Install the Oracle thin driver


Collaboration (Compoze) database table changes from SP2 to SP3.

The collaboration_create_tables.sql file was modified in SP3 to add primary key constraints and to add NOT NULL constraints to the primary key columns to several tables. However, during database upgrade, the scripts do not apply the changes.

Platform: All

Workaround: To take advantage of the NOT NULL column constraints and primary key additions, and to retain any data, rename the existing Compoze tables and replace them with the new Compoze tables defined in <WL_HOME>/portal/db/<DBMS>/<VERSION>/collaboration_create_tables.sql. Then, you can select data from the previous tables and place it into the newly created tables. The following are the affected tables:


Note: These changes were applied to columns that were already defined as 'NOT NULL' and 'UNIQUE' due to code restrictions. In addition, drops for those to primary key constraints were added to collaboration_drop_constraints.sql.


RDBMSAuthenticator does not work with XA drivers.

Portal's RDBMSAuthenticator does not work with XA drivers.

Platform: All

Workaround: Configure RDBMSAuthenticator to use a non-XA driver. Note that RDBMSAuthenticator cannot participate in global transactions because it does not use a data source; XA requires the use of a data source.


Failover with Oracle RAC takes longer than the time specified in Test Interval in RDBMSAuthenticator.

In a domain configured with Oracle RAC, the length of time required for failover to a secondary RAC node to complete is longer than the time specified in the Test Interval parameter in the RDBMSAuthenticator window.

Platform: All

Workaround: The RDBMSAuthenticator will failover to a secondary RAC node only after detecting a database connection failure, either through failed user authentication attempts or through RDBMSAuthenticator connection tests. Connections that fail the tests are closed and reopened to re-establish a valid physical database connection, as determined by the Test Interval parameter specified while creating the RDBMSAuthenticator.

The Test Interval setting should be based on a trade-off between system availability requirements and database performance impact. Lower settings will reduce the amount of time to detect RAC failures and reduce the likelihood of failed user authentication attempts, but will increase the database load. The default setting is 120 seconds. To minimize failed user authentication attempts due to RAC failures, set the Test Interval parameter to its minimum value of 5 seconds.

With the Administration Server running, log in to your domain's Administration Console and navigate to Security > Realms > myrealm > Providers > Authentication > RDBMSauthenticator. Select the Details tab then go to Test Interval. The Test Interval parameter sets the amount of time for connections to be closed and re-established.


If markup contains more than 4000 bytes, an attempt to store it in the database causes an error.

If markup contains more than 4000 bytes, an attempt to store it in the database causes the end_xml field in the PF_MARKUP_DEFINITION table to overflow. An error similar to the following occurs:

<21 juil. 2005 10 h 59 CEST> <Error> <netuix> <BEA-423334> <The end markup of size [ 2000 ] in file [ /PageStructureController.portlet ] was larger than the maximum, [ 2000 ]. Truncating the markup.>

Platform: All

Workaround: To obtain database scripts that correct this problem, contact BEA technical support and ask for patch number CR244936. The database scripts in this patch will create a new table and move content from the PF_MARKUP_DEFINITION table. For instructions on running these scripts, see the readme file that accompanies the patch.


Compatibility Mode

Table 8 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.

Table 8 Known Limitations in WebLogic Portal Compatibility Mode 

Problem ID



Options not visible in Compatibility Mode Administration Portal.

When first accessing the Administration Portal for a domain running in Compatibility Mode, not all Administration options are visible. User Management will appear as the only option. Other options, such as Portal Management, are not visible.

Platform: All

Workaround: Press the browser Refresh button to refresh the screen, and then all options will appear on the screen. Or, select User Management option, then click the Home button to return to the main Administration page. All options will appear on the screen


Limitations Fixed in WebLogic Portal 8.1 Service Pack 6

This section lists limitations that were fixed in WebLogic Portal 8.1 Service Pack 6. For more information, see the following section:

CR Number



For WSRP, the wrong port number can be encoded in remote portlets.

Issue-1: When a proxy server is used for WebLogic Portal, and port numbers are not specified in url-templates-config.xml, WebLogic Portal may generate URLs with incorrect port numbers.

Issue-2: When a proxy server is used with the WSRP producer, the dynamic WSDL generated at request path /producer/WSDL may contain invalid port numbers.


JAR file manifests for WLP 8.1 SP5 wrongly say SP4

The files contained in the .jar files for WebLogic Portal 8.1 SP5 wrongly say BEA WebLogic Portal 8.1 SP4.

Platform: All

Workaround: Ignore the version number in the manifest files. When speaking to BEA Support make it clear that you are using SP 5 since BEA Support cannot tell using the manifest. You can confirm you are using SP5 by checking the Version string in the server startup messages.



Limitations Fixed in WebLogic Portal 8.1 Service Pack 5

This section lists limitations that were fixed in WebLogic Portal 8.1 Service Pack 5. For more information, see the following sections:

Limitations Fixed for Portal Extensions

CR Number



Adding portlet preferences to a portlet beyond a certain number causes an xml truncation error (java.sql.SQLException: Data exception — string data right truncation).

For more information, see CR237251 in the Known Limitations section.


Page flow portlet refreshAction not invoked on nested page flows.


Webflow Portlets Refresh event not being processed in preRender Administration Portal


Limitations Fixed for Portal Framework

CR Number



Out-of-the-box samples — Receive the error "missing the file /framework/skins/avitek/" when attempting to consume portlets using the out-of-the-box applications.


Limitations Fixed for Database

CR Number



WebLogic Portal 8.1: Inconsistent string lengths for book labels, portlet labels, page labels in database



Limitations Fixed in WebLogic Portal 8.1 Service Pack 4

This section lists limitations that were fixed in WebLogic Portal 8.1 Service Pack 4. For more information, see the following sections:

Limitations Fixed for WebLogic Workshop Portal Extensions

CR Number



Non-portal web applications using p13n_controls will see many generated EJBs in the config.xml file.


WebLogic Workshop does not merge application configuration files or deployment descriptors upon application or project import.


Cannot create an entitlement using the CONTAINS operator with a user profile property.


Some custom layouts might not be displayed correctly in the WebLogic Workshop portal builder.


Portal will not start up in a cluster with Domain Administration Port enabled.


The WebLogic Workshop IDE displays a green squiggle under a legitimate Struts action.

This limitation continues to exist but is now documented in the WebLogic Workshop release notes.


Configuration needed for a non-portal project to serve as a WSRP producer.


Using WSRP producer portlets in a non-portal web app.


Limitations Fixed for Administration Portal

CR Number



When creating a new user in the top-level "everyone (All Users)" node of the Browse User-Groups tree, the resulting link to edit the new user is nonfunctional.


Cannot add Document Manager or Document Connection Pool Service via the Administration Portal.


Cannot login to the sample Avitek portal.


Console SocketException in the Administration Portal, Portal Management page when viewing a disassembled portal node.


Single quote character for user/group property values is not supported in the online tools.


Newly created Delegated Administration Role is missing from Administration Portal.


Portlet title should be shown as read-only in the Administration Portal.


Limitations Fixed for Portal Framework

CR Number



Potential case sensitivity differences between Entitlements, User Profiles and Authentication Providers.


LDAP UUP does not allow for LDAP-S.


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 6.


Unused attribute on ugm:createUser tag.


unifiedProfileTypeCache needs to be renamed in <APPLICATION>/META-INF/ application-config.xml.


Limitations Fixed for Search

CR Number



AutoIndexer exits when a directory name that doesn't exist is specified.


Portal search engine administration tools do not display an error if a process doesn't start.


Portal search engine does not remove content when a search is deleted.


Portal search engine fails to run on certain operating systems.


Limitations Fixed for Database

CR Number



Database Deadlocks may occur while processing a Proxy Portlet cleanup background task.



Limitations Fixed in WebLogic Portal 8.1 Service Pack 3

This section lists limitations that were fixed in WebLogic Portal 8.1 Service Pack 3. For more information, see the following sections:

Limitations Fixed for WebLogic Workshop Portal Extensions

CR Number



Page Flow Portlet behavior changed so that default action (begin) is not called at page refresh.


The 'taxonomy' parameter is no longer required for UserInfoQuery portal control.


URL rewriting for PageFlow Portlets has changed so that portletInstanceLabel_actionOverride=/modulePath/action instead of just portletInstanceLabel_actionOverride=action.


Standalone page flows do not honor the {url:securePort} token within url-template-config.xml.


Microsoft SQL Server 2000 case-sensitive settings may affect Content Management queries.


The mailmanager script has incorrect username and password.


load_cm_data.cmd displays a NoClassDefFoundError when the CLASSPATH environment variable is too long.


User or group creation appears to fail in a cluster with Default Authentication Provider.


Limitations Fixed for Administration Portal

CR Number



Tree Framework error in large trees.


Exceptions with content preview for nonexistent user.


Limitations Fixed for Portal Framework

CR Number



HTML entity references not supported.


"Input Line Too Long" errors on starting WebLogic Server.


When using Internet Explorer and uploading a file of zero bytes to the Content Management system via the WebLogic Administration Portal, you receive a warning message that the page has expired.


P13N request wrapper implements getRemoteAddr(), getRemoteHost().


Password of the principal in LDAPPropertyManager configuration needs to be encrypted.


Sample NT service script for WebLogic Portal.


Portal pages rendered by Netscape 7.0 have oversized width for column.


DRE port number incorrectly specified in ODBCFetch file.


JavaPortlet container throws NullPointerExceptions when weblogic-portal is present in a portal web app.


The visible property for an editable book may not reflect the accurate value.


Limitations Fixed for Search

CR Number



Portal search engine is not able to index some languages.


Limitations Fixed for Third-Party Tools

CR Number



A change of language is not detected if a user is logged in.


Limitations Fixed for Database

CR Number



Database page size need to be 8K.



Limitations Fixed in WebLogic Portal 8.1 Service Pack 2

This section lists limitations that were fixed in WebLogic Portal 8.1 Service Pack 2. For more information, see the following sections:

Limitations Fixed for WebLogic Workshop Portal Extensions

CR Number



When using the directory restriction feature of the My Content sample portlet, content nodes do not appear.


Portal drag and drop: unsupported drop actions cause portlets and books to disappear in portal design view.


When using the Tracked Anonymous User capability, the <um:createUser> JSP tag and createUserControl require the attribute "doPostProcess" to be set to "true."


Once a theme is set on a portal resource, such as a page or portlet in the WebLogic Workshop Portal Designer, it cannot be removed in the Property Editor window.


Using browse to set values for selected, rollover, and unselected image properties may result in inaccurate URI.


WebLogic Workshop becomes inoperable and gets WebLogic Server errors when using the Install Portal option from WebLogic Workshop while the server is running.


Unexpected error dialog appears when dragging from calendar picker in campaign, property set, placeholder, segment, discount, and content selector editors.


Receive errors in the WebLogic Workshop Portal Designer when setting "Navigation" and "Editable" properties on a book.


Portal Designer "inverting" unselected and selected page/book images.


Leaving the Rollover Image property blank causes undesirable browser rendering behavior.


Limitations Fixed for Administration Portal

CR Number



Role definitions not updated when users or user groups are deleted.


Unable to create a desktop from a portal template (.portal file) that contains a book that holds no pages.


User-group associations with entitlements and delegated administration roles cannot be reformed once deleted.


UserManagementException is thrown when updating group properties.


Console error received when modifying a campaign via the WebLogic Administration Portal in an application deployed in enterprise archive (.ear) format


Entitlements roles with titles that include apostrophes are not associable.


Delegated administration and entitlement roles cannot be predicated on a User Property Set property of type "Date/Time".


Unable to update clauses based on a "visitor's characteristic" that is based upon a Restricted Date/Time property.


Occasional problems moving page/book order in books in library.


Error when changing the theme of a book instance in a Desktop that has already been changed.


Limitations Fixed for Portal Framework

CR Number



Context root change may cause servlet deployment error.


Startup problems when installing into directory names with spaces.


Deployment of a new portal application may fail when the server is already running.


Changing placement of books/pages/portlets may not cascade.


Tutorial portal: portlet preferences page editing problems.


Cascading style sheets require correct mime-type for Netscape/Mozilla browsers.


In portal compatibility mode, the following entitlement exception occurs: javax.servlet.jsp.JspException: An error occurred in EntitlementHelper.


Limitations Fixed for Third-Party Tools

CR Number



Yahoo Integration: JavaScript function required to be present for Yahoo! Content.


Collaboration portlets setup instructions incomplete in WebLogic Workshop.




Back to Top Previous Next