Release Notes

     Previous  Next    Open TOC in new window    View as PDF - New Window  Get Adobe Reader - New Window
Content starts here

WebLogic Portal Release Notes

This document contains information on the following subjects:

Note: For updated release notes, consult the WLP documentation web site.


Installing Patch Set Update (PSU) Releases

This section explains the steps you must follow to install WLP 10.3 PSU releases.

Note: These release notes contain a full list of the bugs fixed in each PSU. See Key Limitations Fixed in PSU, Key Limitations Fixed in PSU, and Key Limitations Fixed in PSU

This section includes these topics:

Patch Installation Tools

You can install patches using SmartUpdate GUI or with the Smart Update command line utility. For detailed instructions on running and using Smart Update GUI, see “Oracle Smart Update Installing Patches and Maintenance Packs” in Oracle Smart Update Installing Patches and Maintenance Packs. For detailed information on using the command line utility, see “Using the Command-Line Interface” in Oracle Smart Update Installing Patches and Maintenance Packs.

Installing the WLP PSU

Note: If either the WLP or PSUs are installed on your system, you must remove them before you install the WLP PSU. The WLP PSU includes all of the fixes implemented in the previous PSU releases, plus a new set of fixes.
  1. If necessary, remove previous PSU releases WLP and/or from your system.
  2. Install the PSU. The Patch ID is: 76EM.
Note: If you are installing PSU into an existing WLP domain that has not yet been modified to support PSU 10.3.1,, or, you must first install PSU, then perform a domain upgrade, and then start the upgraded domain. If you already installed one of these previous PSUs, you do not need to perform this domain upgrade, even after you remove the older PSUs. For detailed information, see Update Existing Domains,” in the UCM VCR Adapter Guide. These instructions explain how to remove certain J2EE Shared Libraries and install new ones. You must perform this domain upgrade whether or not you intend to use the UCM VCR Adapter feature.

Installing Previous WLP 10.3 PSUs

Note: All of the PSUs described in this document require a one-time domain upgrade if you are installing the PSU into an existing WLP domain. You must perform the domain upgrade after installing the PSU, and before restarting the domain. If any of the PSUs described in this document were previously installed on your system, then a domain upgrade is not necessary, because the domain upgrade would have been performed already. For detailed information, see Update Existing Domains,” in the UCM VCR Adapter Guide. These instructions explain how to remove certain J2EE Shared Libraries and install new ones. You must perform this domain upgrade whether or not you intend to use the UCM VCR Adapter feature.

If you are installing a WLP PSU older than WLP, you must install the patches in this order:

  1. Install the 10.3.1 PSU (patch APD4). If APD4 is not installed on your system, SmartUpdate will require you to install it.
  2. Install the (patch AVW6).
  3. Install the (patch ZKHC).
  4. Install any new patches, in the order of their release.

After installing the patch(es), you must perform a domain upgrade, as explained in the previous note.

If You Want to Use the UCM VCR Adapter

If you want to use the UCM VCR Adapter, follow the detailed installation instructions in the UCM VCR Adapter Guide. Note that you must install PSU releases in the order specified previously in Installing Previous WLP 10.3 PSUs.


What’s New in Oracle WebLogic Portal 10.3

Oracle WebLogic Portal and Workshop for WebLogic 10.3 provide tools to build enterprise portal applications.

This release includes:


Installing the Portal Examples

Before you can use any WLP example application, the Portal Examples feature must be installed. This feature adds the available WLP sample applications and the sample domain to your installation. Portal Examples are not installed by default.

Install the Portal Examples using the Oracle WebLogic Portal Installer. You can install the examples into a new installation or into an existing installation by following these steps:

  1. Run the Oracle WebLogic Portal Installer and choose to perform a Custom Installation.
  2. In the Choose Products and Components dialog, select Portal Examples.
  3. Use the wizard to complete the installation.
Note: If you intend to add the Dynamic Visitor Tools Sample facet to a web project that you wish to enable for DVT, you must also perform these steps to add the Portal Examples feature. See the WebLogic Portal Samples Guide for more information.


Required Patches

When you install WebLogic Portal 10.3, the required patches in Table 1 are installed automatically. If you uninstall any of these required patches and need to reinstall them, use the information in Table 1 in conjunction with the Smart Update utility to reinstall and apply the patches. For detailed information on using Smart Update, see Installing Patches and Maintenance Packs Using Smart Update on e-docs.

Table 1 Required Patches for WLP 10.3
Patch ID


Supported Platform Information

For information about Oracle-supported hardware and software configurations, see the supported platform documentation.


Supported Standards

This release of WebLogic Portal supports the standards listed in Table 2.

Table 2 Java Standards
JSF - Sun Reference Implementation
1.1, 1.2
1.1, 1.2
JSR 170 and JSR 170-compliant repositories
1.0 Level 1 and Level 2 (excluding optional features)
1.1, 1.2


Known Limitations and Workarounds in WebLogic Portal

This section describes problems that have been identified in WebLogic Portal. For each problem listed in the following tables, a problem ID called a CR number is specified. These IDs enable Oracle and users to monitor the status of issues while solutions are developed. This section groups the known limitations by functional area.

For more information, see the following sections:


Table 3 lists known limitations and workarounds for installing WebLogic Portal.

Table 3 Known Limitations and Workarounds for Installation 
Problem ID
Uninstalling Weblogic Portal within a domain that includes WebLogic Integration results in removal of domain dependent files.
The uninstall process removes portal-based p13n files that WebLogic Integration domain provisioning requires.
Platform: All
Workaround: Do not uninstall Weblogic Portal.
A harmless warning is thrown by Message Driven Beans once during deployment in the WebLogic Portal Sample Application
The Message Driven Beans throw the following warnings when the deployer can’t obtain distribute destination information:
Message-DrivenEJB: MessageBufferTopicBean is unable to connect to the JMS destination: weblogic.portalApp.WlwRuntimeAppScopedJMS#MSG_BUFFER_TOPIC. The Error was:Can not get distribute destination information. The destination JNDI name is weblogic.portalApp.WlwRuntimeAppScopedJMS#MSG_BUFFER_TOPIC, the provider URL is null
This warning is thrown only once and can be safely ignored.
Platform: All
Workaround: None

WebLogic Portal and Workshop for WebLogic Upgrade

Table 4 lists known limitations and workarounds for upgrading WebLogic Portal and Workshop for WebLogic.

Table 4 Known Limitations and Workarounds for WebLogic Portal and Workshop for WebLogic Upgrade 
Problem ID
The location of WLP upgrade wizard
The location of WLP upgrade wizard has changed. The script is located at WLPORTAL_HOME/common/bin instead of WEBLOGIC_HOME/common/bin.
Note that the upgrade wizard link from the Windows Start Menu, Oracle Products > WebLogic Server 10.x > Tools > Domain Upgrade Wizard does not start the WLP Upgrade Wizard. It points WEBLOGIC_HOME\common\bin and starts the WLS Domain Upgrade Wizard. To use the WebLogic Portal upgrade wizard, locate WLPORTAL_HOME\common\bin\upgrade.cmd and double click on it.
Platform: All platforms
Workaround: cd to WLPORTAL_HOME/common/bin and execute the upgrade.cmd/.sh script.
Possible build errors after upgrading a web project that depends on an
EJB project
After upgrading some web project which depend on classes from an EJB project in an EAR, the EJB classes will show as unresolvable in the web project in the Problems view.
Platform: All
  1. Open the web project properties and go to J2EE Module Dependencies.
  2. Go to the Web Libraries tab.
  3. Check the EJB project(s) and click OK.
That triggers a rebuild and the classes should be found.
Changes to public XmlDisassemblerContext methods
The class com.bea.netuix.application.transform.disassembler.XmlDisassemblerContext had several methods that used methods from JDOM version 0.9. This version of JDOM turned out to be incompatible with new releases of JDOM. The 0.9 version of JDOM was repacked into* classes, and the methods in XmlDisassemblerContext have been updated accordingly. Users of these methods will have to change their code.
Platform: All
Workaround: Replace all references to methods of XmlDisassemblerContext that use org.jdom.* with*.
Potential when upgrading an application from JDK 1.5.0_06 or prior to JDK 1.5.0_07
If you upgrade an application originally built with JDK 1.5.0_06 or earlier to WebLogic Portal 10.2, you may see an exception similar to the following when starting the server: javax.xml.namespace.QName; local class incompatible: stream classdesc serialVersionUID =
4418622981026545151, local class serialVersionUID =
The problem is actually with the 1.5.0_07 version (and later) of the JDK, in which there is an incompatible change of the serialVersionUID of the javax.xml.namespace.QName class.
Platform: All
Workaround: Set the old compatibility value by setting the system property:
Or you can add the following option to the Java command in the script you use to start WebLogic Server:
- Dcom.sun.xml.namespace.QName.useCompatibleSerialVersionUID=
After upgrading a 9.2.2 domain, the Portal Administration Tools’ Portal Management page and Content Management page may display an Unable to Render error.
After upgrading a 9.2.2 domain, accessing the Portal Administration Tools’ Portal Management page or Content Management page may result in a browser error, such as “Unable to render /framework/skeletons/wlp-tools/tree_header.jsp.” Additionally, the server log contains a java.lang.NoClassDefFoundError: javelin/jsp/JspContextWrapper error. These errors occur when the these pages have been first accessed in a 9.2.2 domain, and then accessed again in the upgraded 10.2 domain.
Platform: All
Workaround: Search for and delete the jsp_servlet directory under the <DOMAIN_HOME>\servers\MyServer\tmp\_WL_user\MyApp directory, where MyServer is the name of your server and MyApp is the name of the affected application.
An SQLException may occur when migrating RDBMSAuthenticator data if the data contains WebLogic Portal system user or group names during domain upgrade
When a domain with an RDBMSAuthenticator is upgraded to 10.2 and its data is migrated to SQLAuthenticator during the upgrade, an SQLException may occur if certain WebLogic Portal system user or group names exist in the RDBMSAuthenticator. Specifically, if the RDBMSAuthenticator has the users “weblogic” or “portaladmin”, or has the groups “Administrators”, “AppTesters”, “Deployers”, “Monitors”, “Operators”, or “PortalSystemAdministrators”, an SQLException similar to the following will occur:
SQLException when executing file:/C:/<WL_HOME>/common/p13n/db/<DATABASE>/upgrade_fromdbmsauth_towlssqlauth.sql
Platform: All
Workaround: To avoid this error, edit the file <BEA_HOME>/wlserver_10.0\common\p13n\db\data\required\p13n9_insert_system_data.sql prior to running the domain upgrader. Remove from this file any INSERTs that correspond to users, groups, or group memberships that already exist in the RDBMSAuthenticator. For example, if the user “weblogic” exists in the RDBMSAuthenticator, remove the “INSERT INTO USERS” statement that applies to “weblogic”.
Confusing informational message about running SQLAuthenticator.sql displayed when domain is created with “Customize Environment and Services Settings” set to Yes
The following error message is displayed by the Configuration Wizard after domain creation:
Before booting this domain, it is necessary to run the SQL file located at <DOMAIN_DIR>\security\SQLAuthenticator.sql in order to initialize a domain security admin user in the database.?
If Run Scripts were not selected on the Run Database Scripts panel, the database objects needed to execute SQLAuthenticator.sql and other components will not exist in the database.
Platform: All
Workaround: Create a new domain and execute Run Scripts from the Run Database Scripts panel.
Deployment of an 8.1.6 application that has been upgraded to 10.3 may fail due to NoClassDefFoundErrors
Deployment of an 8.1.6 application that has been upgraded to 10.3 may fail due to NoClassDefFoundErrors if the application was imported and upgraded in the default workspace or a workspace that had contained previously imported applications that have been deleted.
Platform: Windows 2003
Workaround: Import and upgrade all 8.1.6 applications to 10.3 using a new custom workspace that is clean.
Shared library build errors after upgrading 8.1.x application
After upgrading, numerous build errors will display in the Problems view about issues with share libraries, such as:

'beehive-controls-1.0.1-10.0' library is on the classpath of this project but is not in the weblogic-application.xml file of the EAR project

Platform: Linux
Workaround: In the EAR project, make a minor change to the EarContent/META-INF/weblogic-application.xml file (e.g. add a space or empty line) and save the file. After a build, the build error should go away.
Build and runtime error with pageflow strutsMerge annotation after upgrading and application on Linux
In an upgraded web application that uses the strutsMerge functionality in a PageFlow, a build error appears in the Problems view similar to:
File 'struts-config-merge.xml' could not be found in the web application.
If the projects are published to a server even with the error, a org.apache.beehive.netui.pageflow.UnresolvableForwardException from the PageFlow will occur at runtime.
Platform: Linux
Workaround: Create new projects in Workshop and import the source artifacts.
WLP 10.2 create database failing against DB2 V9.5.
During creation of WLP databases on DB2 only, an invalid SQLSTATE code was used in several 'CREATE TRIGGER' statements. On DB2 9.5, this prevented the Configuration Wizard from successfully populating the database due to a script error. On prior versions of DB2, this invalid code has the minor impact of causing an uninformative error message to be displayed rather than the intended, informative error message in certain rare cases of referential integrity violation.
Note: This issue has been fixed. New domains created with WLP 10.2 Service Pack 1 and later Service Packs will be unaffected by this issue.
Platform: Linux
Workaround: For domains created with 10.2 GA, users may choose to upgrade the database to fix the affected triggers. This step is optional, as the impact of the affected triggers is considered minor. To fix this issue in a 10.2 GA domain, simply run the script upgrade_pf_create_fkeys.sql located in BEA_HOME/wlserver_10.0/portal/db/db2.
For users upgrading WLP domains from 8.1, 9.2, or 10.0, the affected triggers will be fixed automatically when upgrading with the Domain Upgrade Wizard or the upgrade_db script.

Workshop for WebLogic Framework and Development

Table 5 lists known limitations and workarounds for Workshop for WebLogic framework and development.

Table 5 Known Limitations and Workarounds for Workshop for WebLogic Framework and Development 
Problem ID
JRockit JVM is the recommended JVM for iterative development.
JRockit JVM is the recommended JVM for iterative development. Using other JVMs may result in significant errors after a number of application redeployments.
Platform: Windows and Linux.
Workaround: Use JRockit JVM as the default JVM for all iterative development.
Opening WebLogic Portal Administration Console may fail to publish projects
If your Portal EAR project has been published, untargeted, and subsequently retargeted on a server instance, the open WebLogic Portal Administration Console menu action may fail to republish your application when invoked. This will manifest itself as a 404 response code upon access to the WebLogic Portal Administration Console.
Platform: All
Workaround: Manually publish your Portal EAR Projects by right-clicking the appropriate server entry in the Servers view, and selecting Publish. The open WebLogic Portal Administration Console menu item will then work properly.
Application deployment in a domain with a DB2 database may result in a warning message regarding the privilege to perform SELECT on table SYSIBM.SYSDUMMY1
When an application is deployed in a domain that uses a DB2 database, a harmless warning message may be displayed such as:
Platform: All
Workaround: To prevent this message, grant the privilege to perform SELECT on the table SYSIBM.SYSDUMM1 to PUBLIC. For example, GRANT SELECT ON SYSIBM.SYSDUMMY1 TO PUBLIC;
Some Workshop for WebLogic JSF tooling features are suppressed in order to support both JSF and NetUI
When developing a Portal-enabled web application that uses JSF, some of Workshop for WebLogic’s JSF tooling features are suppressed in order to support both JSF and NetUI including:
  • The button that launches the Select Navigation Case Chooser dialog does not appear in the Workshop for WebLogic property sheet.
  • Validation warnings for referencing non-existent actions are suppressed.
  • Workshop for WebLogic does not support the Ctrl+hover gesture used to click-through to navigation cases in faces-config.xml.
Platform: All
Workaround: None.

WebLogic Portal Framework and Development

Table 6 lists known limitations and workarounds for WebLogic Portal framework and development.

Table 6 Known Limitations and Workarounds for WebLogic Portal Framework and Development 
Problem ID
The Export/Import Utility creates an additional locale for artifacts imported in a non-English locale
This problem occurs in the situation where the user localizes a book in the library to a non-en_US locale, and then exports the book as a .pinc and imports the .pinc to a destination in the non-en_US locale. Upon importing the resource, scoped to the Library level, the Export/Import Utility creates an entry in the L10N_LOCALE table for all pages and books in the library rather than only in the main book, even though the other library artifacts were not localized.
Platform: All
Workaround: Avoid using the Library scope when importing the .pinc resource in a non-en_US locale.
KeyBootstrap class failed to generate keys
Because of incompatible use of domain-scoped start up classes, commerce applications built using Oracle commerce functionality do not support the use of application-scoped JDBC pool.
Platform: All
Workaround: None
When async rendering is enabled for a portlet, portlets cannot directly change window modes or states
WebLogic Portal allows portlets to change the current window state and/or mode of a portlet either programmatically, or via parameters added to URLs. When async rendering (either via AJAX or iframes), these mechanisms will not provide a consistent view to the end user. Particularly, the title bar rendered above the portlet will not reflect the change in the mode or state immediately.
Platform: All
Workaround: None
Proxy portlet state management: 8.1.x consumers do not properly recover producer session timeouts
For a federated configuration in which the consumer is running 8.1.x, the consumer may not recover properly from producer session timeouts.
Platform: All
  1. The consumer session timeout must be strictly less than the smallest positive session timeout of all producers. For example, suppose a consumer portal has three proxy portlets PP1, PP2 and PP3 corresponding to three remote producers RP1, RP2 and RP3. RP1 has no sessions (session timeout = 0), RP2 has a session timeout of 5 min. and RP3 has a session timeout of 2 minutes. Then the session timeout for the consumer must be less than 2 minutes.
  2. Assign all proxy portlets to a different group. The downside of this option is that remote portlets that wish to share state cannot.
  3. Finally, if (1) and (2) are not viable options, the user will need to close his or her browser and reopen the portal in the event of a producer session timeout.
Uncompressed URL templates must be used when generating off-site URLs
When using GenericURL, its subtypes or the corresponding JSP tags to generate off-site URLs (i.e.: URLs to resources that are not hosted in the web application of the code generating the URL) in a web application that has compression enabled, a URL template with compression disabled must be specified.
For example,
GenericURL redirectURL = GenericURL.createGenericURL(request, response);
where “no_compression_template” is the name of a URL template that excludes the {url:compression} pseudo-token.
Platform: All
Workaround: Do not use URL compression, or do not use GenericURL to construct URLs to off-site resources.
Server port changes that are made to a running server require a portal application restart
If a server port (HTTP or HTTPS) is made to a running server, any affected portal applications need to be restarted for the changes to be picked up.
Platform: All
Workaround: Redeploy the EAR.
WebLogic Portal does not support changing the context-root of an existing portal web application with customized portal objects.
Once a .portal file has been customized, or if entitlements have been created for a desktop, the context-root of the web application cannot be changed without losing the customizations and the entitlements.
Platform: All
Workaround: Do not change the context-root value:
The onInit events are not supported for remote portlets
Portlets can optionally register an event handler to get notified when portlets gets initiated by registering a handler of type “onInit”. This feature is not currently supported for remote portlets.
Platform: All
Workaround: In general, portlets can run onInit logic lazily either when a user interaction occurs, or when another event is handled.
Expression-based visitor roles, which use multiple-user property-set values, may return a false negative, preventing a visitor from correctly assuming the role
If a visitor role has multiple property-based conditions OR’d together, and if any of the input values (supplied via UUP impl or the default property manager) to a condition are null, the result (and therefore the role) is indeterminate because null is not explicitly checked for.
Platform: Occurs only in XACML security providers.
Workaround: Always include a default value for property set attributes, so a null is never used during comparisons.
Portlet render dependencies do not support fully-qualified URLs to reference HTTP addressable resources
A portlet’s render .dependencies file does not support using fully-qualified URLs to reference script, style, and other HTTP addressable resources. For example, a script reference to Google Maps that is defined in a .dependencies file will result in an error such as “The look and feel resource at base path <path> could not be found.”
Platform: All
Workaround: Two workarounds are available:
  • The com.bea.netuix.laf.DynamicHtmlRenderDependencies class programmatically supports adding script, link, and style references to a portal during rendering via its “add” methods. This class can be used in a backing file to ensure that the resources for a portlet are correctly defined.
  • Add dependencies from a portlet’s view.
  • DynamicHtmlRenderDependencies.add(Script|Link|Style)(...)

Note: Use of this approach is limited if multiple portlets attempt to load the same resource. If this is the case loading duplicated resources in this way should be protected against in JavaScript or should be avoided.

REST requires fine granularity to determine who can create new library portlets
REST requires a fine granularity to control the ability for end users to create new library portlets.
Platform: All
Workaround: Use the rest-config.xml or web.xml file as follows:
  • Disable the REST servlet.
  • Disable the create portlet REST command via rest-config.xml.
  • Implement a version of to perform custom access checking and configuring via rest-config.xml.
Default polling changed from 3 to 5 seconds
The default polling interval has been increased. This interval is set in the system property:
Platform: All
Workaround: None.
Icons do not to render in Portal Administration Console tools when a space exists in the name of a Portal EAR project
For example, if there is a space in the name of a Portal EAR project, icons in the console do not appear in the Create Desktop wizard and the administration console displays missing icon errors:
<Aug 30, 2007 1:33:00 PM MDT> <Error> <netuix> <BEA-423139> <The look and feel resource wlp-help-16.gif could not be found in the path /framework/skins/default/images.>
Platform: All
Workaround: Remove any spaces in the Portal EAR project name.
JSF validation does not work with the portal namingContainer tag and causes IllegalStateException: Client-id
A known problem exists in some versions of JSF 1.1, where the sequence number used to generate IDs for components that do not specify their own client ID is not reset. This eventually results in the IllegalStateException in cases where a MyFaces page is re-rendered and there is no navigational rule defined.
Platform: All
Workaround: Several workarounds are available:
  • JSF 1.2, where the generated ID sequencing is handled differently.
  • Use a version of JSF 1.1 where the issue has been fixed (currently no such versions ship with 10.2).
  • Surround the namingContainer component with an f:subview component, which serves to reset the sequence generation.

Note: No portal behavior changes due to this problem.

Cannot remove title bar from Java Portlets (JSR-168)
The title bar cannot be removed from Java Portlets (JSR-168).
Platform: All
Workaround: Use the borderless theme on your portlet to remove the title bar.
Different bean instances are used for JSF than for JSTL tags using jsp:useBean
If a JSF portlet attempts to integrate JSTL tags with JSF managed beans using jsp:useBean, different bean instances are used for JSF than for the JSTL tags.
Platform: All
Workaround: This is due to the fact that jsp:useBean is not aware of the managed bean environment used by JSF. To work correctly, the bean instances referenced by jsp:useBean must first be “primed” by either accessing them from within JSF or explicitly calling to the variable resolver with something like:
   getCurrentInstance(), 'myVar');
When an Apache MyFaces is the underlying JSF implementation provider, invalidating the session results in an IllegalStateException
In a JSF portlet that uses Apache MyFaces as the underlying JSF implementation provider, invalidating the session in JSF application logic results in an IllegalStateException following the processing of the JSF action.
Platform: All
Workaround: Use one of the following methods:
  • Do not invalidate the session on logout.
  • Use a different JSF implementation, such as Sun RI.
  • Use a different version of MyFaces, where the installed NavigationHandler checks to see if the request is for a MyFaces JSF bridge, checks the session validity, or catches IllegalStateExceptions when the session has been invalidated.
  • Perform the session invalidation in a backing file.
  • Redirect to an intermediate non-JSF portlet, such as a servlet or .jsp, that invalidates the session and forwards to the login page.
<f:param> JSF tag does not work with WSRP
The <f:param> tag will not work when using WSRP. This is due to request parameters being unavailable during the pre-render and render life cycle stages.This is true for all portlet types consumed via WSRP. See Avoid Accessing Request Parameters in Rendering Code.
Platform: All
Workaround: Parameters should be placed in a container managed bean or processed during the handlePostbackData.
Portlets must have title attribute specified to be disassembled into the database
The .portlet XML schema allows for portlets to not specify the <title> attribute. However, titles are required for successful disassembly of a portlet into the database. Attempting to disassemble a portlet that has no <title> attribute set will produce an XmlDisassemblerException.
Platform: All
Workaround: Add a <title> attribute to your .portlet file to ensure successful disassembly.
When publishing a portlet, publishing service does not properly reflect themes from publishing contexts
If a portlet instance is influenced by a theme, render dependencies may not properly reflect the influence of the theme. Subsequently, the published version of the portlet will not correctly render the theme. This applies to portlets published in API and URL modes.
Portlets published in full URL mode will not include visual aspects of the theme.
Platform: All
Workaround: There is no known workaround for this issue.
Asynchronous JavaScript imports via XIE may cause Internet Explorer 7 to hang if referenced script does not exist
If portlet content or render dependencies are loaded via XIE that refer to an external JavaScript resource that does not exist, or may otherwise fail to load, XIE lifecycle processing in Internet Explorer 7+ will hang. This is because XIE attempts to mimic initial browser loading behavior by executing scripts serially, even when such scripts are fetched asynchronously by the browser, as with IE7+. If the attempt to load the script fails (typically because it does not exist), IE7+ halts advancement of the readyState field for that script at “loading” and produces no error message.
Platform: All
Workaround: Ensure that .js files referenced in this way exist at the specified path.
Content Presenter Preview Mode will not show Theme changes
Content Presenter’s Preview Mode shows the current user a preview of how the portlet will render with the current wizard settings. However, in this release the Preview Mode will not show changes to the Theme setting. To see the effect of your Theme selection, please save the changes made in the wizard.
Platform: All
Workaround: Save your changes to see your Theme applied.
Problems on Linux platform when using drag and drop operations in portal editors
There are known problems dragging and dropping components when multiple portal (or other associated portal artifact) editors are opened simultaneously. This problem is only applicable to the Linux platform. Drag and drop operations targeting the active (visible) portal editor will be mishandled and incorrectly delivered to the underlying inactive (not visible) portal editor tab. This problem has been noted both when dragging components from the workshop design palette over to a portal editor or when using drag and drop to reposition components within a portal editor.
Platform: Enterprise Linux 5
Workaround: Close other inactive open editor tabs such that you are only working with ONE open portal (or other associated portal artifact) editor at a time.
Non-web facets are displayed when modifying the facets of a project that had facet install failures during creation
During project creation, if a facet failed to install (e.g. the WLP DVT Sample facet), the wizard for modifying the project's facets available from the project properties will show non-web facets which are not valid for the project. The wizard won't let you select those facets and their appearance is harmless.
Platform: All
Workaround: Ignore the additional facets.
No JSP created when a PageFlow Portlet is created via the Portlet Wizard.
If you use the Portlet Wizard to create a PageFlow portlet, the appropriate home jsp is not created. For example, if you create a pageflow /my/Flow.jpf, then that pageflow will point to a default JSP at /my/flow.jsp. However, the wizard will not create this JSP file.
Platform: All
Workaround: Manually create the jsp. Or, create the pageflow first, using the pageflow creation wizard, and then create the portlet from the pageflow.
JSF portlets require the Sun Reference Implementation and the 'server' STATE_SAVING_METHOD
By default, the Workshop JSF facet makes the following configuration choices:
  • Uses MyFaces as the JSF implementation
  • Configures the 'client' STATE_SAVING_METHOD in web.xml
When building JSF portlets in a Portal Web Project, the default configuration of JSF is not supported. It must be changed to use the Sun RI implementation and the 'server' STATE_SAVING_METHOD.
To select the JSF implementation:
  1. In the Project facet selection dialog, select version 1.1 from the dropdown menu for the JSF facet.
  2. Check the box for the JSF facet.
  3. Then click the Next button until the JSF library module configuration pane appears.
  4. Select the 'Use Sun RI WebLogic J2EE Library' library module, which is the Sun Reference Implementation.
To configure the 'server' STATE_SAVING_METHOD:
  1. Open web.xml. There is a context parameter named 'javax.faces.STATE_SAVING_METHOD'.
  2. Set the value of this parameter to 'server', replacing 'client'.
Platform: All
Workaround: Use the Sun RI JSF implementation and the 'server' STATE_SAVING_METHOD.

Content Management and Search

Table 7 lists known limitations and workarounds for content management and search.

Table 7 Known Limitations and Workarounds for Content Management and Search 
Problem ID
IDOL Server does not successfully delete an entry from the index when the file is removed from a directory scanned by FileSystemFetch.
Even though FileSystemFetch is configured to delete content from IDOL when an item is removed from the file system, the file is not properly removed from the IDOL Server index.
Platform: All
Workaround: Edit the FileSystemFetch configuration file (FileSystemFetch.cfg):
  1. To the [Default] section add 'QueryPort=9022' (change the port number to match the QueryPort defined in AutonomyIDOLServer.cfg).
  2. Do not use relative paths in the DirectoryPathCSVs entry in your Import job definitions. Only use fully qualified path entries.
Renaming nodes in a library services-enabled repository can cause the version name to become out of sync with the node’s name
When library services are enabled, nodes should not be renamed. This can cause incorrect search results to be returned.
Platform: All
Workaround: None.
JSR-170 JNDI provider logs misleading error messages due to improper classloading configuration
After configuring the JSR-170 JNDI content repository provider, users may encounter a misleading error message indicating that the object bound in JNDI did not implement the javax.jcr.Repository interface:
com.bea.content.RepositoryException: Object bound not of type javax.jcr.Repository: found a (org.apache.jackrabbit.jca.JCARepositoryHandle)
Platform: Jackrabbit Content Repository with JSR-170 JNDI provider
Workaround: Ensuring that the javax.jcr.Repository is visible within the same classloader as the content repository application and the JSR-170 adapter may resolve this issue.
For more information regarding application classloading, see:
Unclear exception when using CM versioned repository API
The following cryptic message is displayed:
Caused by: The operation completed successfully when running code in the versioned repository. This error message originates from the JVM, and generally means that a user is trying to pass in an InputStream which has already been consumed.
Platform: All Sun JVM
Workaround: Ensure that the InputStream being passed to content management has not already been consumed or read.
Cache rename, new cache defaults for Virtual Content Repository (VCR) searchCache and WLP repository explicitPropertyCache
Previously the Content Management VCR searchCache used default values of 100 entries, 1 hour TTL. In 10.2, more appropriate default values of 200 entries, 5 minutes TTL are used if this cache is not already configured. The new defaults apply only if the cache is not manually configured.
The Content Management WLP repository explicitPropertyCache has been renamed to repo.explicitPropertyCache to be consistent with other WLP repository-only cache names. This cache previously used default values of 100 entries, 1 hour TTL. New more appropriate default values of 50 entries, 30 minutes TTL are used if this cache is not already configured. The new defaults apply only if the cache is not manually configured.

Note: If previous explicitPropertyCache settings have been configured, you may want to update them with the new cache name.

Platform: All
Workaround: None, not required.
Full-text search wildcard queries are dependent on Autonomy configuration setting
When performing full-text search wildcard queries for a particular piece of text, finding that text is dependent on the number of occurrences of that text. The default setting is 5. To change this setting, the following needs to be added to the [Server] section of the IDOL Server configuration file (AutonomyIDOLServer.cfg):
For example, this query with the default setting:
ITextQuery tQuery = FullTextQueryFactory.getTextQuery();
ITextQueryParameter textCriteria = tQuery.buildEquals
   (new String[] {'*Propagation*'});
IFullTextSearch fullTextSearch =
   textCriteria, false);
Search search = new Search(repositoryPath, -1, null,
   fullTextSearch, true);
ISearchManager searchManager =    ContentManagerFactory.getSearchManager();
IPagedList<Node> nodes =,
would receive hits when the word “Propagation” appears in 5 documents.
If the setting:
is added, it would only need to appear in 2 documents to received hits.

Note: This setting is also used for spell checking. The Autonomy documentation specifies that “The minimum number of documents that a term has to appear in before IDOL server can use it as a spell check suggestion.” For more information, see the Autonomy documentation.

Platform: All
Workaround: Add the setting with the desired count to AutonomyIDOLServer.cfg.
Filtering on search results from is not available on the modifiedDate property
The API ISortableFilterablePagedList.getAllFilterableProperties() indicates for the result of the that the caller may filter on the modifiedDate property. This is not currently functional as a FilterCriteria or via the ISortableFilterablePagedList.reFilter() call.
Platform: All
Workaround: Specify the modifiedDate in the search expression and filter when initially executing the search.
Delegated Administration users who can publish content need DA rights to view the Default workflow to use the Bulk Update tool
A Delegated Administration (DA) user who has Publisher capabilities for a content repository will also need the View capability on the default workflow. An example of Publisher capabilities would be View, Update, and Publish capabilities on a content repository. If the DA publisher does not have View capabilities on the default workflow, users will encounter com.bea.content.AuthorizationException: “User does not have view privileges to view this workflow or its properties” when they attempt to use publish content using the bulk update in the Workspace View in the Content Management Administration tools.
Platform: All
Workaround: Assign the View capability for the default workflow. It is not required to assign the View capability for any other workflows, even if the content that is being published uses a custom workflow instead of the default workflow. The bug is around the validation code that mistakenly retrieves the default workflow, no matter what.
Autonomy full-text search using notEquals or isNull with nested properties in a query does not include “parent property does not exist” results.
All the possible nested values for a type are not indexed if they do not exist. Therefore, when searching for null or notEquals on a nested property name, the results will only contain values that are null or notEquals to the nested property name that was indexed.
For example, a node of type “planet” contains one or more instances of type “continent”. Each node of type “continent” contains one or more instances of type “country”. In this case planet Earth would have a nested property of “continent[0].country[0].name” equal to Nigeria, while planet Mars would not have any continents or countries. Subsequently there would not be any nested properties of that name indexed for Mars.
Platform: All
Workaround: Use an inverse search.
The original query would look like this:
IMetadataQuery mQuery = FullTextQueryFactory.getMetadataQuery();
IMetadataQueryParameter ftqp =
mQuery.buildNotEquals('continent[0].country[0].name', 'Nigeria');
IFullTextSearch fullTextSearch =
FullTextSearchFactory.buildFullTextSearch(ftqp, null, false);
Search search = new Search(repositoryPath, -1, null, fullTextSearch,
IPagedList<Node> nodes =, search);
That query will return no nodes.
But, if you created an inverse query like this:
IMetadataQuery mQuery = FullTextQueryFactory.getMetadataQuery();
IMetadataQueryParameter mqp1 =
mQuery.buildEquals('continent[0].country[0].name', 'Nigeria');
IMetadataQueryParameter mqp2 = mQuerymQuery.buildNotNull('continent');
IMetadataQueryParameter mqp3 = mQuery.buildIsNull('continent');
CR358426 (continued)
IMetadataQueryParameter mqp = mqp2.or(mqp3).not(mqp1);
IFullTextSearch fullTextSearch =
FullTextSearchFactory.buildFullTextSearch(mqp, null, false);
Search search = new Search(repositoryPath, -1, null, fullTextSearch, true);
IPagedList<Node> nodes =, search);
That query would return all planets except for Earth.
WebDAV users need read access to the default workflow
The WebDAV code needs access to the default workflow to perform CRUD operations on any given resource in a managed WLP repository. If the logged-in user does not have the View capability on the default workflow, it could throw a (403) error message to the client.
Platform: All
Workaround: Make sure that all users accessing content management via WebDAV have the View capability on the default workflow.
Manual removal of a repository that cannot be removed with WebLogic Portal Administration Tools
In some error conditions, it is not possible to remove a content repository configuration using the WebLogic Portal Administration tools. When this occurs, it is still possible to manually remove the Content Repository configuration.
Platform: All
Workaround: Use the following steps to manually remove a repository configuration:
  1. Write down the content repository configuration name. For example, MyRepository.
  2. Shut down WebLogic Server.
  3. Use the console to determine the plan file name and file system location. For example, if the application is called TestApp, it might be called TestAppPlan.
  4. Inside the <appName>Plan directory, back up the plan.xml file, and then open it in a text editor.
  5. Search for the repository name and for each <deployment-plan>/<variable-definition>/<variable> element in which the repository name is found, remove the <variable> element.
  6. For example, this <variable> element snippet should be fully removed:


  7. After the last <variable> section that contains the repository name, remove the immediately-following section that contains the string RepositoryProperty_MANAGEMENT_ENABLED. For example:
  8. <variable>

  9. Look in the <deployment-plan>/<module-override> section where <module-name> is your app-name. Inside that <deployment-plan>/<module-override> section, look for a <module-descriptor> section that has a <root-element> of p13n-cache-config. Inside this section, search again for the repository name.

For each <deployment-plan>/<module-override>/<module-descriptor>/<variable-assignment> element in which the repository name is found, remove the <variable-assignment> element.

For example, this <variable-assignment> element snippet should be fully removed:


  1. Look in the <deployment-plan>/<module-override> section where <module-name> is your app-name. Inside that <deployment-plan>/<module-override> section, look for a <module-descriptor> section that has a <root-element> of cache-config. Inside this section, search for the repository name. For each <deployment-plan>/<module-override>/<module-descriptor>/<variable-assignment> element in which the repository name is found, remove the <variable-assignment> element.
  2. For example, these <variable-assignment> element snippets should be fully removed:






  3. Save the plan.xml file and restart the server.
If a user sets the Autonomy setting AutoDetectLanguagesAtIndex=TRUE, and then adds content of multiple languages, only the content that is in the DefaultLanguageType will be returned within the GroupSpace searches.
Once AutoDetectLanguagesAtIndex=TRUE, the content is marked with the language that it is in. However, the GroupSpace search only uses the DefaultLanguageType to conduct its search. If content exists that is indexed under multiple languages, the GroupSpace search returns only results that match the default language type.
Platform: All
Workaround: Do not set AutoDetectLanguagesAtIndex=TRUE. The default setting is false.
CR Bridge: JCR property value constraints not visible in WebLogic Portal property choices
When using the CM JCR Bridge, JCR property value constraints are not currently exposed in WebLogic Portal property choices. This limitation is present because some property value constraints, such as regular expressions and built-in repository constraints, cannot be resolved to a specific value.
Platform: All
Workaround: If a validation exception occurs when creating or updating a JCR property value, manually consult the JCR repository’s property value constraints for the appropriate type to ensure a value meets all constraints.
Sample domains are pre-populated with ObjectClasses that do not necessarily conform to file system repository data types
When using a file system repository, ObjectClasses are limited to only a single binary property. Some of the available out-of-the-box ObjectClasses have multiple binary properties, such as book. This makes it appear that it is possible to create a node in the file system repository of that type. However, internal validation code in the file system repository prevents this.
Platform: All
Workaround: None. When using the file system repository, nodes cannot be assigned an ObjectClass having multiple binary properties.
Error retrieving empty InputStreams from Sybase
Whenever a user tries to store an empty input stream or a zero-byte file via WebDAV in content management, the code converts it into a zero-byte input stream and stores it in the database. However, when the data is retrieved, the database does not return an empty input stream, but returns a null. Content management then traps that null and throws an error to the user.
Platform: This problem has been known to occur in Sybase drivers.
Workaround: Do not store zero-byte input streams into content management or zero byte files via WebDAV in a Sybase database.
Copy/Paste not working with nested properties when library services are enabled.
Copy/Paste for a content item that has a nested property containing a file upload property value doesn't work and throws the following exception:

org.apache.beehive.netui.pageflow.UnresolvableForwardException: Unable to find a forward named 'VIEW_RENDERER' on action view in page flow /content/popupsAndButtons/PopupButtonController.jpf.

To reproduce this problem:
  1. Create a new content type.
  2. Add a nested property to the content type that contains a file upload property value.
  3. Create a new content item of that new type and upload a file.
  4. Save and check in the node.
  5. Create a new folder or use an existing one and try to copy/paste the content item to the new folder by using either right click or the context sensitive button feature.
Platform: WLP 10.2 and 10.3
Don't upload any file content in a nested property until after the node is copy/pasted or clear the nested property values and re-add them after the copy/paste operation.
To allow copy:
  1. Click on the new content node
  2. Select the properties tab.
  3. Click Checkout
  4. Select the nested property's clear value checkbox
  5. Select the Clear Values button.
  6. Warning: This will clear all your nested properties so the user must write them down or take a screenshot.

  7. Click checkin.
  8. The user is now free to copy and paste the node.
Bug 8429360
Federated search cache is now repository-specific and the federated search cache configuration needs to be updated.
To improve configurability, the CM federated search cache (named searchCache) has been changed to a set of repository-specific caches (named searchCache.<repoName>).
Platform: WLP 10.3
Workaround: If you have a META-INF/p13n-cache-config.xml file in your application, or have configured your application through the WLP Administration Console, you need to copy the appropriate cache settings from the “searchCache” cache to each repository search cache.


Table 8 lists known limitations and workarounds for federation.

Table 8 Known Limitations and Workarounds for Federation 
Problem ID
WSRP: Portlet Preference description is not passed from the producer portlet to the proxy portlet
When an administrator views portlet preferences for remote portlets, WebLogic Portal Administration Console does not provide a description of preferences.
Platform: All
Workaround: Use more descriptive names for preferences.
WSRP LocalProxy depends on client to send producer (session) cookies
When LocalProxy is enabled for WSRP, the client becomes responsible for sending cookies, especially the session cookie.
In general, this is fine except in cases where the path parameter for the cookies of the producer is not the same as or a prefix of the path parameter for the cookies of the consumer. In these cases, the client will not necessarily send the producer cookies.
Platform: All
Workaround: Ensure that the session path parameter for cookies from the producer is the same as or a prefix of the path parameter for cookies from the consumer.
Registration Properties do not contain default values
This is due to calling EntityPropertyManager.getProperties() which does not return default values.
Platform: All
Workaround: Do not use default values in registration properties. The consumer should send all values when registering.
Remote portlets' minimized title is not preferred title
When a remote portlet sets the title programmatically, WebLogic Portal will use that title in the titlebar.This functionality is not supported when the remote portlet is minimized. When a remote portlet is minimized, WebLogic Portal will not contact the producer to render the portlet, and hence loses the dynamically set title.
Platform: All
Workaround: None
WSRP Security signatures and encryptions do not work
Encryption (Confidentiality) and Signatures (Integrity) are not currently supported policy elements and are not currently supported for WSRP messages.
Platform: All
Workaround: Only use Identity elements in the policy
WSRP local proxy mode does not support default context path or context path containing slash (/)
If WSRP local proxy is enabled and the consumer accesses a producer with the default context path or a context path containing a slash (/), then the consumer request will fail.
Platform: All
  1. Do not configure producers that will be accessed via local proxy to have the default context path or a context path containing a slash (/), OR
  2. Do not enable WSRP local proxy mode if any of the producers that could be accessed with the local proxy are configured to have the default context path or a context path containing a slash (/).
WebLogic Portal does not support using Content Presenter in WSRP environments
Content Presenter and its portlet instances cannot currently be used as WSRP producers in WebLogic Portal 10.2.
Platform: All
Workaround: To access Content Presenter instances remotely, use Portlet Publishing.


Table 9 lists known limitations and workarounds for collaboration.

Table 9 Known Limitations and Workarounds for Collaboration 
Problem ID
GroupSpace does not allow “/” as context root
GroupSpace depends on having a web application name serving as the context root. The content repository cannot be initialized and populated otherwise. To use GroupSpace in your web application, the <context-root> element cannot be “/”.
Platform: All
Workaround: In your web application's web.xml, name the context root something other than “/”.
Server for a PointBase domain created via the Configuration Wizard fails to boot with - Cannot find the user “WEBLOGIC_GROUPSPACE” if “Run Scripts” is run only for p13nDataSource
When a new domain is created via the Configuration wizard with WebLogic Portal and WebLogic Portal GroupSpace Framework selected under “Generate a new domain configured automatically to support the following Oracle Products” and on the “Run Database Scripts” window the “Run Scripts” button is selected only for p13nDataSource the WebLogic Server for the resulting domain may fail to boot with Cannot find the user “WEBLOGIC_GROUPSPACE”.
Platform: All
Workaround: From the domain home directory for the server that fails to boot with Cannot find the user “WEBLOGIC_GROUPSPACE” run:create_db.cmd or for Linux/Unix ./
Admin user search results return personal and private data for other users
When executing a search in a GroupSpace community while being logged in as an Admin user the search results may contain other users personal and private data. For other users personal data it will show up in the results but you can not click on the personal data to see the full details.
Platform: All
Workaround: None. Suggestion is to only log into GroupSpace as a non-admin user. While being logged in as Admin the user experience may not be as expected.
Links to GroupSpace resources are not always automatically updated
The WYSIWYG HTML editor in GroupSpace allows the insertion of links to GroupSpace resources. However, when those resources are deleted, the links in the HTML are not automatically updated. You must manually edit the HTML to replace or remove the broken links. Also, links to GroupSpace resources in the GS Links portlet have to be manually updated when the linked item is deleted.
Platform: All
Workaround: None.
Using external utilities to populate collaboration repository data will cause metadata corruption
The collaboration portlets (Discussion, Tasks, Calendar, etc.) manage a separate database table to track contents of their containers and content repository items. This table can get out of sync when the repository is populated using external tools such as Propagation or Admin Tools.The following symptoms indicate that the table needs to become synchronized with the repository:
  • Error message that is logged to the server console: <Error> <Content Collaboration API> <BEA-000000> <[No count metadata could be found for node with id 'XXXX'.] >
  • - Discussions portlet shows inaccurate counts of items within categories and/or forums.
Platform: All
Workaround: Customers that experience this behavior will be instructed to download a supporting JSP that will synchronize the metadata table with the repository.
Accessing CM RSS feeds with the GroupSpace RSS portlet
Certain URL formats for RSS feeds are not handled properly by the GroupSpace RSS portlet. Specifically, URLs that contain single quote characters cause problems during the parsing process used by the RSS portlet. This limitation prevents the display of content management RSS feeds when using a URL format that requires the use of single quote characters.
Platform: All
Workaround: Use named Syndication Feeds. Below is an example of a URL for a content management RSS feed that will not work in the GroupSpace RSS portlet due to the use of single quote characters:
By adding a syndication feed entry named “TheFeed” to the wlp-syndication-config.xml file, which is configured with the same search query, the same data can be accessed using a URL such as:
When searching for a GroupSpace element that has multibyte characters in the name and the encoding for the GroupSpace enterprise search is not the default, search results may not be returned
If a GroupSpace element is created and has a name consisting of multibyte characters, you can search by the title of the element and receive correct results. However, if you configure the encoding for GroupSpace enterprise search other than default, the search results may not be returned.
Platform: All
Workaround: None.

Production Operations

Table 10 lists known limitations and workarounds for Production Operations.

Table 10 Known Limitations and Workarounds for Production Operations 
Problem ID
The Export/Import Utility provides limited support for localization of portlet instances at an admin level scope
Scoping a book or page with a new locale to the library level is working. When the .pinc is exported/imported in the new locale, the new locale with new title is picked up by the WebLogic Portal Administration Console and L10N tables are updated in the database. However, this is not working for localizing a portlet instance scoped to the admin level. The imported locale is not reflected in the WebLogic Portal Administration Console for the portlet, but the L10N database tables are updated.
Platform: All
Workaround: Avoid using the admin level of scoping if you want to localize portlet instances.
In the Export/Import Utility, locale resource descriptions are not being propagated to the .pinc file
The locale description of a book or page is not getting output to the .pinc file. Thus, an administrator is able to localize only the artifact's title and not it's description.
Platform: All
Workaround: Manually add the locale description after exporting/importing the book or page.
In the Export/Import Utility, new resources are not imported correctly when first importing in a foreign locale
For example, if you do not have all you resources localized to a specific locale (for example, “es”) and you export a desktop in locale “es”, then the resources that do not have a resource (title) in “es” will do a best match algorithm. That best match could be a title in “en” (English)
Upon re-import to the destination you are telling the XIP utility that everything is in “es” and therefore it erroneously added ‘en’ titles in “es”.
Platform: All
Workaround: Make sure all your resources have been localized in the locale you want to export. For example, first re-import the modified .portal file in the default en (English) locale and then import the modified .portal file again in the “es” (Spanish) locale.
A placeholder lock is propagated only for the current “page view” of the layout
The Propagation Utility can track only the placeholders of the currently selected layout from the page “view.” Due to this, only the locks (set using Entitlements) on the placeholders in the currently selected layout can be propagated. Propagation of locks on other layouts is not possible.
Platform: All
Workaround: Review propagation results and manually update any necessary placeholder locks.
WebLogic Portal Analytics reports for Desktop, Pages, and Portlets with the same title but from different web applications are indistinguishable.
Analytic reports do not identify which WebLogic Portal web application sourced a particular usage event. This means that if the same title is used in multiple web application portlets, multiple reports of that title will exist and there is no way to know which web application is associated with each report.
Platform: All
Workaround: Use unique title names.
Large Content Exports via Propagation May Throw TimeOutExceptions
When exporting content, if a parent (folder) contains a large number of children (greater than 2000), a weblogic.transaction.internal.TimedOutException can appear.
Platform: All
Workaround: Reorganize the content data so that a parent does not contain thousands of children. If that is not possible, increase the JTA timeout value from the Weblogic Console from the default 30 seconds to a higher value.
Analytic report on a selected web application that has never been accessed shows activities of other non-selected web applications
When multiple web applications in an enterprise application exist and there are activities in all the web applications except one, the Analytics report on the web application that does not have any activities shows results of the all other web applications that do have activity. After the web application is accessed, the Analytics report on the web application shows only its own activities.
Platform: All
Workaround: Make sure a web application is accessed before selecting it for the Analytics report.
ScenarioService error message observed during propagation of content management resources
While propagating content management resources, the following error message may be observed in the console or server log files:
<ScenarioService: Error getting user profile wrapper: weblogic>
This error is caused by a campaign event firing when a content management resource, such as a node or type, is saved by propagation. The scenario service attempts to fetch the profile of the current user (the propagation user) when it does not exist. Propagation of the content resource should still complete successfully. However, it is likely that the event logic is failing to complete successfully.
Platform: All
Workaround: Disable event handling during propagation.

WebLogic Portal Administration Console

Table 11 lists known limitations and workarounds for WebLogic Portal Administration Console.

Table 11 Known Limitations and Workarounds for WebLogic Portal Administration Console 
Problem ID
User profile update may not be seen by federated portlets
If an administrator updates a user's profile, the user may not see the updates until they log out and log back in. This includes properties sent via WSRP to remote producers.
Platform: All
Workaround: The user must log out and back in to see the update profile.
Changes to a User Profile in Visitor Tools are not displayed in UM Tools
Changes made outside the WebLogic Portal Administration Portal to a user profile in Visitor Tools are not displayed in the WebLogic Portal Administration Console: User Management - User Profile after a refresh. The changes are only displayed after logging out and logging back in.
Platform: All
Workaround: To see an updated user profile, log out and log back into the WebLogic Portal Administration Portal.
Content Management: Cannot clear individual values or properties for nested property types
Nested property types are properties that have the structure of another user-defined type. For nested type properties that allow multiple values, it is not possible to clear individual values (reset them to empty or default values).
Platform: All
Workaround: To clear an individual value of a multi-valued nested property you must select the multi-valued nested property for edit and then delete the individual value using the trash can icon. You should then add it again with the same name, but with all empty values.
IM editors don’t support content queries that reference user, request, and session properties
IM editors don't support content queries that reference user, request, session properties.
Platform: All
Workaround: Use the IDE to edit content queries that reference user, request, session properties.
IM editors don’t support content expression syntax
IM editors don't support content expression syntax.
Platform: All
Workaround: Use the IDE to edit content queries that use content expression syntax.
IM editors don’t support IM rules multiple actions or conditions of the same type
IM editors don't support IM rules multiple actions or conditions of the same type.
Platform: All
Workaround: Use the IDE to edit IM rules that have multiple actions or conditions.
Administration Tools do not use wsrp-consumer-security-config.xml
If you created a wsrp-consumer-security-config.xml in a consumer’s WEB-INF directory, Administration tools will not use it when adding or editing producers or when viewing or setting proxy portlet preferences. This may result in incorrectly sending SAML or the following exception:
weblogic.xml.crypto.wss.WSSecurityException: Unable to add security token.
Platform: All
Workaround: Set up your producer to work with the consumer’s default configuration.
Portal Administration Console functionality does not work in FireFox 3
Many parts of the Portal Administration Console do not function correctly with FireFox 3. This includes, but is not limited to, pagination in the browse pages and the shortcuts buttons.
An error similar to this will show in the Server console:
<Jun 25, 2008 10:20:45 AM MDT> <Error> <HTTP> <BEA-101019> <[weblogic.servlet.internal.WebAppServletContext@775b78d5 - appName:
'myApp', name: 'tools', context-path: '/myAppAdmin', spec-version: '2.5'] Servlet failed with IOException
weblogic.utils.NestedRuntimeException: Cannot parse POST parameters of request: '/myAppAdmin/xHttpReq'
Workaround: Use FireFox 2 or Internet Explorer
Platform: FireFox 3 on all platforms
WebLogic Portal Administration Console does not provide a way to re-register if InvalidRegistration is returned by a producer.
The WebLogic Portal Administration Console does not provide a way to re-register if InvalidRegistration is returned by a producer.
Platform: All
Workaround: Delete the producer using the Administration Console and then recreate the producer.
No way to modify an invalid registration from the WebLogic Portal Administration Console
If a consumer registers with a producer, and then the producer later requires additional information from the consumer, the producer will return a fault to the consumer. If you try to modify the registration properties for a producer with an invalid registration using the Administration Console, you receive an error and stack dump from whatever fault was returned by the producer.
Platform: All
Workaround: Delete the producer using the Administration Console or, manually delete the producer from the wsrp-producer-registry.xml file and then manually recreate a new producer entry.
The WebLogic Portal Administration Console displays the Add/Delete portlet preference for non-WLP producers
The Administration Console displays UI for adding and deleting portlet preferences for remote WSRP producers. However, non-WLP WSRP producers generally have no way of supporting this functionality.
Platform: All
Workaround: WLP PAT users shouldn't try to add or remove portlet preferences from non-wlp remote wsrp portlets.


Key Limitations Fixed in WebLogic Portal

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

Key Limitations Fixed for WebLogic Portal Framework and Development

Problem ID
Bug 8181860
Harmless error message logged by Lease Manager. Fixed in PSU

Key Limitations Fixed for Content Management and Search

Problem ID
CM metadata search using PointBase database and containsall operator can fail.

Key Limitations Fixed in PSU

Problem (Base Bug) ID
When the Authentication Hierarchy Service is disabled in the Portal Administration Console, the interface now allows for the retrieving of Groups that have names containing spaces.
The producer now correctly sets the user profile in the session at the necessary time upon login. A client browser refresh after login is no longer needed to retrieve user profile data.
Using the Administration Console, deleting a multi-valued nested property when additional nested property values exist no longer causes all nested values to be removed.
In the Portal Administration Console, the Add Role button on the Delegated Administration tab for a given resource is now being shown for users that are members of child DA roles.
When deleting multi-valued, nested property entries on a content item using the Portal Administration Console, the data structure displaying the saved value became corrupted. This problem is resolved.
Fixed an issue where a portal application's response time increased with the session size.
When deleting multi-valued, nested property entries on a content item that contains more than 11 nested items using the Administration Console, the data structure displayed for the saved value is no longer corrupted.
Updates to Portlet, Page, and Desktop definitions are now properly reported as being changed by Analytics based correctly on the timestamp at the time of update.
Fixed a bug preventing installation of Workshop for WebLogic plug-ins (WebLogic Portal (10.3.0) requires feature "com.m7.nitrox (1.0.20)")
Fixed an issue where validation on a select box did not always work in Async mode
Added updates to WSRP for interoperability with WebCenter-produced portlets.
Suppress innocuous exception (row already exist in index PK_LEASE on table P13N_LEASE) when multiple servers were started within a cluster.
The GroupSpace desktop did not refresh automatically when adding or removing portlets with the Visitor Tools in Internet Explorer. This issue was resolved.
The call to determine whether repository is an Oracle implementation now uses public access methods for the repository configuration.
Previous versions of the Clipper portlet did not allow a developer to directly alter the URL of the page to clip. That URL is set initially with a preference, but once a user begins browsing a clipped page, the current URL is stored in the session, and there was no way to programmatically change it. This issue has been resolved by adding a method that can be called in a backing file to reset the remote URL. The backing file has to extend the clipper portlet backing file. See Javadoc for com.bea.netuix.clipper.ClipperHelper for usage information.
Portlet Definition retrieval is now more efficient.
JSR168 form posts now correctly de-namespace parameters.
Look And Feel (LAF) with SSL and Internet Explorer 6 no longer pops up a warning about secure and insecure items for pages containing iemenu.js IFRAME.
Cookies were added with a separate call to addRequestProperty(), causing lots of cookie headers. This was resolved by aggregating cookies into one string.
There is now a Description attribute available in the IDE for both Books and Pages. The value of this attribute is used when updating desktops based on the .portal file, just like Title.
Fixed a bug where creating a content type with 100 properties of nested type causes Propagation to fail.
The cm:search tag sometimes returned a ClassCastException when versionedContent='true'. This issue has been resolved.
WLI domains were missing files after being upgraded using the Domain Upgrade Wizard, preventing log in to the WLI console. This problem has been resolved.
For Oracle Database usage with WLP, this fix allows you to increase the size of the CM_PROPERTY.TEXT_VALUE column to what the database allows. For example ORA allows 4000 bytes for a varchar column. Increasing this value will likely avoid storing partial text values in the CM_PROPERTY.TEXT_VALUE_EXT table for lengthy entries. This then avoids usage of the CM_PROPERTY_V (view), which is better for performance.
The groupid parameter was not being set consistently when using proxy portlets. This could cause inconsistent behavior when placing the session cookie in the header for getMarkup requests. This issue has been resolved.
The content tree rendering in the Administration Console was slow when there are delegated admin roles assigned to the contents nodes. This has been improved.
An enhancement to share cookies across WSRP Producers was added.
Improved performance of CMS delete statements. Along with this fix, customers using an Oracle database need to remove the constraint on CMV_NODE_VERSION_PROPERTY.
_pageLabel request parameter was not present on the consumer side URLs when specified in the templates. This problem has been resolved.
Image tags uploaded were being converted to absolute URLs after saving in pinEdit. This issue has been resolved.
Calling IInitCookieResponseContext.setResponseCookies() or adding to the list of cookies returned by IInitCookieResponseContext had no effect. This problem has been resolved.
Consumer URL rewriting was not honoring the amp entity setting. This problem has been resolved.
An Internet Explorer-specific bug in the Portal Administration Console at the Page contents editor caused the portlet panels to remain in a fixed position while scrolling the page. This issue has been resolved.
A bug was preventing Delegated Administrators from updating the properties of content Types. This issue has been resolved.
The Title and Description editor for library instances of portlets was not fully displayed nor functional. This issue has been resolved.
During upgrade of a WLP domain using a DB2 database from 8.1x, several rows of system data were lost during upgrade, preventing the creation of pages, books, and desktops in the upgraded domain. This issue has been resolved.
Database creation on DB2 v9.5 was failing with a java.sql.SQLException due to use of an invalid SQLSTATE code. This issue has been resolved.
A SQL error occurred when creating shell definitions for shells with a header only or a footer only due to an error in the TIU_PF_SHELL_DEFINITION trigger. This issue has been resolved.
Extraneous text was being inserted into JavaScript of clipped pages. This issue was resolved.
Content Selectors that had boolean conditions could not be updated in the Portal Administration Console; a ClauseUpdateException was thrown when saving the edit. This issue has been resolved.
When rendering a desktop that contains remote (WSRP) portlets, a performance improvement was made by bypassing a SQL query that occurred for each portlet.
Error messages similar to "ORA-00001: unique constraint (X.PK_LEASE) violated" are benign and will no longer be written to the server logs.

Key Limitations Fixed in PSU

Problem (Base Bug) ID
The UCM SPI will now throw an exception when asked to sort on an invalid property when searching.
Some complex full-text search expressions weren't parsing properly when searching against the UCM SPI.
UCM does not support "or" operations when executing a folder search. The UCM SPI will now detect this situation and throw an exception accordingly.
Fixed error when using expression search for cm_isContent==false.
Fixed bug when executing a date range search against the UCM SPI.
Fixed full-text search bug when specifying a search like /*/some/path which failed against the UCM SPI.
Fixed null and empty value handling when searching against the UCM SPI.
Fixed a bug in properly handling full-text searches against boolean properties in the UCM SPI.
Fixed a bug in properly handling full-text search against multi-valued properties in the UCM SPI.
The UCM SPI will now throw an exception when asked to search for an object class which doesn't exist.
The UCM SPI will now throw an exception when asked to search for a property which isn't indexed.
Fixed recursive search bug in the UCM SPI.
Fixed multi-threaded issue when searching against the UCM SPI.
Fixed bug to provide a primary property definition for folder nodes from the UCM SPI which allows them to be rendered using the ShowPropertyServlet.
Fixed binary retrieval from UCM when configured to use IDC over SSL.
UCM does not support multiple sort criteria when searching so the UCM SPI will now throw and exception when this is encountered.
Fixed issues around specifying paths and recursive search against the UCM SPI.
Fixed a scenario where browsing folders could show documents through the UCM SPI which were not marked as released on the content server.
Fixed a bug in properly exposing the weblayout rendition binary stream.
Fixed a scenario where retrieving a document's binary content could retrieve the latest version binary data instead of the currently released binary data.
Fixed a bug where text criteria couldn't be properly or'd when executing full-text searches against the UCM SPI.
Fixed a bug when executing a full-text search against the UCM SPI with an empty text criteria.
Fixed a bug in the UCM SPI if the latest version of a document is not released, you couldn't retrieve that document by path.
Fixed a bug in the VCR that would federate searched to additional configured repositories in some cases where it shouldn't.

Key Limitations Fixed in PSU

Problem (Base Bug) ID
Corrects issue where Analytics interface displayed incorrect title for a Community or GroupSpace.
When performing a search in the Discussion Forum portlet and the user refreshes the browser, an error occurred. This has been fixed.
The expand/collapse function of the Discussion Portlet list of Categories was not working properly. This has been corrected.
An “Error getting item (stub)...” exception was thrown when adding a Discussion Forum in a GroupSpace Community. This has been corrected.
Validation to detect a Discussion Topic name containing a forward slash or a backslash was bypassed when that Topic was first created in a GroupSpace Community. This has been corrected.
A validation error (“There has been an issue with creating a Topic with this name...”) occurs when adding a Discussion Topic in a GroupSpace Community. This has been corrected.
Propagating a new Content Selector to a portal application sometimes results in a commit error due to a missing dependency. This has been corrected.
With multiple authentication providers configured, if the first provider is not available the other providers will now be tried instead of just throwing an exception.
When JSR-168 portlets have preferences, propagation will fail with an error that includes org.xml.sax.SAXParseException, saying that invalid content was found starting with element netuix:preference. This has been corrected.
When more than one admin user deletes a portlet from the same page at the same time, the portlets that were not deleted appear twice on the page. This was corrected so the the second user to make the update will now receive an ObjectNotFoundException.
The contains and ends options with search expressions do not work for most providers except the SQLAuthenticator. Those options have been removed.
Improved performance of entitlements by implementing a P13n request-scoped role cache, eliminating excessive calls to getProperty(). Entitlement checks on Portal Administration Tool resources now results in a given role being evaluated only once per request; subsequent evaluations of the role during the request get the cached result.
The P13n role caching functionality was not compatible with the EntitleNet role mapping provider. This has been fixed.
An unsynchoronized WeakHashMap was identified that could potentially lead to stuck threads. This has been fixed.
WSDL lookup performance was slow. This problem has been resolved.
There is a potential issue with Async portlets where they could return entire page mark-up instead of only the affected portlet. This has been corrected.
If a user only has a WLP delegated administration role, the user can no longer perform administrative tasks in a GroupSpace application.
With many WLP DA Roles defined, managing the roles can be slow in the Portal Admin Tools web app. A cache was added to improve performance.
The lock placeholder checkbox on a desktop page, which is inherited from the library page when selected, is now disabled when the parent library page checkbox is selected. The lock placeholder checkbox on a desktop page, which is inherited from the library page when selected, was not disabled when the parent library page checkbox is selected. This has been resolved.
The EntityPropertyCache was not being used from WSRP requests. This problem has been resolved
In a JSR-168 portlet, RenderResponse.encodeURL(String) will return a secure URL when the request scheme is secure.
When using the Content Management Bulk Loader with a library services-enabled repository, the -publishfolders option will cause folders to be checked-in and their workflow status set to Published.
An IDE resource leak caused occasional crashes when content selectors were opened and closed repeatedly. This has been corrected.
The WLP customizer is not registered for ejbgen projects, and throws error when a build is run. This problem has been resolved.
Versioned Portal apps having a pageflow action failed to deploy to WLS due to a NullPointerException. This has been corrected.
Mime headers that are explicitly set now maintain character case when retrieved by the producer.
Reduced the memory consumption on the consumer when a very large number of proxy portlets are deployed.
Propagation of Desktop resources can fail when its hierarchy has diverged.
When two managed servers were deployed on the same physical machine the WSDL URL necessary to use the local proxy mode used localhost as the machine name, but pointing to a specific port would permanently pin both consumers to the same producer instance. This has been corrected. To enter a WSDL URL which will pin the consumer to the producer on the same managed server, add a URL like:
http:<lb host>:<lb port>/<producer web-app>/producer?WSDL&wsrp-forceLocalProxy=true.
A cookie parsing error (“Unable to parse the cookie string for the attribute...”) sometimes occurred using portlet publishing. This has been corrected.
An IndexOutOfBoundsException occurred when using a WSRP transport mode of attachment for a JSF Facelets consumer with a small page size. This has been corrected.
Desktop creation will fail if the existing page label is exactly 39 characters. This has been fixed.
When a streaming desktop with async mode enabled contains a JSP portlet with an anchor tag text that starts with “www.”, the anchor displays incorrectly in Internet Explorer. This has been corrected.
JNDI lookups take a relatively long time, so now more lookups are cached to improve first-use performance.
WSRP producers may at times use existing sessions for a new consumer session. This problem has been resolved.
The producer sometimes threw a warning:
“<Warning> <WSRP-Consumer> <BEA-420769> <[consumerWeb] Unable to release sessions on producer [producer_account] due to [Unknown]. Ignoring those sessions.>”.
This has been corrected.
Unexpected behavior sometimes occurred when using an asynchronous desktop with DVT and DISC enabled; symptoms included minimize operations that minimized the wrong portlet, or drag and drop operations that dropped a portlet into another portlet’s markup div instead of into a placeholder div. This has been corrected.
The WLP WSRP Struts adapter was saving request parameters from previous requests on future performBlockingInteraction requests. This has been resolved.
When moving portlets to the bottom position in a placeholder, the new placement was not correctly persisted. This has been corrected.
There is a possibility for threads to become stuck at jspmessagebundle.findincache. This has been fixed.
When using remote Struts or PageFlow portlets, the wsrp-NavigationalState could grow large due to the retaining of unnecessary parameters. This has been corrected.
The scheme for URLs generated from a secure page in JSR 168/286 portlets did not default to HTTPS. This has been fixed.
A form double-submit with a pageflow portlet under load over WSRP using local proxy could cause the form values to be reset. This has been corrected.
When using the DVT with Asynchronous mode enabled, a portlet delete operation could lead to an hourglass mouse icon that blocks further UI usage. This has been corrected.
The “>” character was not handled properly by the Content Management WYSIWYG editor. This has been corrected.
Filtering of Books was not functioning properly under certain conditions. This has been corrected.
WLP Administration Console was incorrectly showing “No Content” for children of a folder in certain situations. This has been corrected.
During the process of creating a new Book in the Portal Administration Console, the cancel button does not function properly. This has been corrected.
In certain situations, one could not create a new Book in the Portal Administration Console. This has been corrected.
When viewing Entitlement Role details, descriptions were not being displayed for users and/or groups that are contained in the Role. This has been corrected.
An exception was thrown in the Portal Administration Tool whenever a problem occurred using the cursor to read Groups, and no Groups would be displayed. This has been corrected. Problems are now logged, and whatever Groups were obtained will be displayed.
A NullPointerException was thrown in the Portal Administration Tool when viewing the delegated administrators for a content node if a role policy was not found. This has been corrected.
The visitor tools dialog window did not work in Firefox. This has been corrected.
The parent page did not refresh automatically to reflect the changes made after saving the changes in the Visitor Tools. This has been corrected.
Enable caching of null service requests.
Performance improvement to UCM SPI. Enables fine-grained locking when a user connects to UCM via the VCR.
Allows UCM SPI to appropriately report timeout errors on connectivity via the RIDC connection from the WLP VCR to the UCM server when using the UCM SPI.
Due to a rare race condition, an UnsupportedRepositoryOperationException sporadically occurred. This has been corrected. Reduces likelihood of receiving erroneous UnsupportedRepositoryOperationException when using the UCM SPI with the WLP VCR.
This is a general performance enhancement for the UCM SPI.
Improves concurrency of the UCM SPI in multi-user, high volume situations.
General performance improvements to the UCM SPI.
With library services are enabled, copying content that has a multi-valued nested binary property from one folder to another using the WYSIWYG editor resulted in an UnresolvableForwardException. This has been corrected.
Added a null check in rollback because UserTransaction might not exist.
When using an Oracle database, a “java.sql.BatchUpdateException: ORA-12899: value too large for column” exception was thrown when adding text containing multibyte characters to a content property. This has been corrected.
The UCM Cache Invalidator now has better performance through better handling of JobManagerService.
Performance was improved when displaying the node summary page for a content node that has a very large number of other nodes linked to it.
Under certain conditions, a NullPointerException could occur after deleting and then re-adding nested content. This has been corrected.
Updating a binary property in a file system repository caused the property data to become inaccessible. This has been corrected.

  Back to Top       Previous  Next