Release Notes

BEA WebLogic Portal 8.1 Service Pack 5 Release Notes

This document contains information on the following subjects:

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

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

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 5 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 5

This section describes problems that have been identified in the Service Pack (SP) 5 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:

WebLogic Workshop Portal Extensions
Administration Portal
Portal Framework
Search
Third-Party Tools
Database
Compatibility Mode

Note: Because Compatibility Domain is no longer supported, remaining issues are not applicable but are listed for reference purposes.

WebLogic Workshop Portal Extensions

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

Table 1 Known Limitations in WebLogic Workshop Portal Extensions

Problem ID	Description
CR099156	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:
CR103681	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. Or From outside WebLogic Workshop, edit the `META-INF/application.xml` of the application.
CR106758	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.
CR110749	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">` with `<netui:html>`
CR121314	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.
CR188234	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 = PortletBackingContext.getPortletBackingContext(getRequest()); if (ctx != null) ctx.setupStateChangeEvent(WindowCapabilities.NORMAL.getName());` 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 2 lists the known limitations and workarounds stemming from issues involving the Administration Portal.

Table 2 Known Limitations in WebLogic Administration Portal

Problem ID	Description
CR109982	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 http://download.oracle.com/docs/cd/E13218_01/wlp/docs81/adminportal/help/CM_CreateNewRepository.html.
CR123835	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.
CR128661	Portal Content Management Administration Portal running on HP-UX 11i requires HP JVM 1.4.1.06 or higher. The character sets used by the Portal Content Management Administration Portal are not available in earlier versions of HP's JVM. Platform: HP-UX11i with JVM 1.4.1.06. Workaround: Use HP JVM 1.4.1.06.
CR132734	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://http://download.oracle.com/docs/cd/E13218_01/wlp/docs81/ipcguide/index.html.
CR135018	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.
CR181374	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: `com.bea.p13n.delegation.management.DelegationHierarchyPersistenceException` 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.
CR185013	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."
CR201669	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.
CR205262	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.
CR205284	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.
CR208553	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 [weblogic.security.internal.encryption.EncryptionServiceException - 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.bea.wsrp.consumer.management.portlet.ProxyPortletRemoveListener]. 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: http://download.oracle.com/docs/cd/E13218_01/wlp/docs81/wsrp/security.html#1003625
CR218852	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.
CR239352	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 3 lists the known limitations and workarounds stemming from issues involving the WebLogic Portal Framework.

Table 3 Known Limitations in WebLogic Portal Framework

Problem ID	Description
CR125007	Credential MBean does not have a tool for editing. The C`redentialMBean` 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" Credential="password"` `Username="uid=SomeUserWithReadPermission,ou=people,dc=beasys,dc=com"/>`
CR177926	"<" 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 "<" for "<" and ">" for ">". If you do this, your title will appear in the tools as, for example, "<Title>", but it will display in the browser as "<Title>".
CR178588	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.
CR179773	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"/>`
CR180105	Receive java.io.FileNotFoundException: 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 `java.io.FileNotFoundException: 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.
CR180784	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
CR181801	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 `java.io.PrintWriter 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.
CR183399	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.
CR192513	LdapPropertyManager throws ConfigurableEntitySystemException when credentialMBeanName is uncommented. When configuring the Unified User Profile for LDAP, the LdapPropertyManager throws the following exception: `"com.bea.p13n.property.ConfigurableEntitySystemException: 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-name>config/credentialMBeanName</env-entry-name> <env-entry-type>java.lang.String</env-entry-type> <env-entry-value>LdapPropertyManager</env-entry-value> < /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: `<Credential Name="LdapPropertyManager" Credential="password" Username="uid=ldapadministrator,ou=people,dc=beasys,dc=com"/>`
CR196690	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.
CR197762	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.
CR198438	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.
CR198827	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@http://www.bea.com/servers/netuix/xsd/portal/support/1.0.0: document element namespace mismatch expected` `"http://www.bea.com/servers/netuix/xsd/portal/support/1.0.0";; got "http://www.bea.com/servers/netuix/xsd/jsp/support/1.0.0";;.>` Platform: All Workaround: None. This message can be ignored.
CR199861	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) request.getAttribute(MarkupRequestState.KEY); String url = (String) state.getParameter("my_url"); %> <a href="<%=my_url%>">Click</a>`
CR203087	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 com.bea.wsrp.consumer.management.producer.ProducerManager. This API provides methods to obtain and update producer information.
CR203935	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/web/netui-adapter.jar` `<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/wsrp-producer.jar` `<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.
CR204478	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.
CR206920	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: file Provides the same behavior as in previous versions. The preferences in the file system always take precedence. To preserve existing behavior, select this value. database 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. both 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`: `<customization>` `<enable>true</enable>` `<propagate-preferences-on-deploy propagate-to-instances="true" master="both"/> <reload-database-on-redeploy reload="false"/> </customization>`
CR218066	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.
CR223724	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="http://www.bea.com/servers/campaign/xsd/campaign/1.1.1";> </ca:ad-id> 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
CR224987	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. Platform: All Workaround: Issue-1: On production systems, always specify proxy server port numbers on `url-templates-config.xml`. There are no reliable ways for WebLogic Portal to determine the port numbers used by the proxy server. Issue-2: Save the dynamically generated WSDL to a file, and update it with the port numbers used by the proxy. There are no reliable ways for the producer to determine the port numbers used by the proxy server.
CR225885	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.
CR226791	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 `"-Dcm.default.search.path="` 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.
CR227092	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 track.unlimited.discount.usage=false to turn off tracking of usage counts for discounts whose usage limit is "UNLIMITED".
CR228941	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 <initial-beans-in-free-pool>0</initial-beans-in-free-pool> to <initial-beans-in-free-pool>1</initial-beans-in-free-pool> This will cause the Rules repository to initialize at server startup.
CR230071	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 http://download.oracle.com/docs/cd/E13218_01/wlp/docs81/javadoc/index.html.
CR235701	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
CR235832	"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: <context-param> <param-name>oamDataFilesystemPath</param-name> <param-value>c:/propagation/81xDomain/inventories</param-value> <description>Base folder path for runtime data, such as inventory exports.</description> </context-param> On a UNIX system, it could be changed such as: <context-param> <param-name>oamDataFilesystemPath</param-name> <param-value>/opt/propagation/81xDomain/inventories</param-value> <description>Base folder path for runtime data, such as inventory exports.</description> </context-param>
CR236023	<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="http://www.bea.com/servers/p13n/xsd/expression/expressions/2.1.1" xmlns:collection="http://www.bea.com/servers/p13n/xsd/expression/collection/1.0.1" xmlns:cq="http://www.bea.com/servers/p13n/xsd/content/query/1.1.1" xmlns:cr="http://www.bea.com/servers/p13n/xsd/rules/core/2.1.1" xmlns:math="http://www.bea.com/servers/p13n/xsd/expression/math/1.0.1" xmlns:ss="http://www.bea.com/servers/p13n/xsd/expression/schema-support/2.1.1" xmlns:string="http://www.bea.com/servers/p13n/xsd/expression/string/1.0.1" xmlns:lit="http://www.bea.com/servers/p13n/xsd/expression/literal/1.0.1" xmlns:wlcs="http://www.bea.com/servers/p13n/xsd/rules/extensions/2.1.1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.bea.com/servers/p13n/xsd/rules/core/2.1.1 rules-core-2_1_1.xsd http://www.bea.com/servers/p13n/xsd/rules/extensions/2.1.1 rules-extensions-2_1_1.xsd"> <cr:name>test</cr:name> <cr:description />
CR236023 (Continued)	<cr:conditions> <multi-and> <greater-than> <wlcs:literal> <wlcs:now /> </wlcs:literal> <wlcs:literal> <wlcs:time-instant>1970-01-01T00:00:00-07:00</wlcs:time-instant> </wlcs:literal> </greater-than> </multi-and> </cr:conditions> <cr:actions> <wlcs:add-catalog-query-object> <wlcs:expression>price > 50</wlcs:expression> <wlcs:max-results>100</wlcs:max-results> <wlcs:catalog-manager-name>portalApp.BEA_commerce.CatalogManager</wlcs:catalog-manager-name> </wlcs:add-catalog-query-object> </cr:actions> </cr:rule>
CR239172	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.
CR254122	JAR file manifests for WLP 8.1 SP5 wrongly say SP4 The `Manifest.mf` 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.

Search

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

Table 4 Known Limitations in WebLogic Portal Search Engine

Problem ID	Description
CR135840	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`

Problem ID

Description

CR135840

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 5 lists the known limitations and workarounds stemming from issues involving third-party tools.

Table 5 Known Limitations in WebLogic Portal Third-Party Tools

Problem ID	Description
CR128531	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.
CR130020	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.
CR135360	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.
CR176498	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): http://bugzilla.mozilla.org/show_bug.cgi?id=217476 http://bugzilla.mozilla.org/show_bug.cgi?id=225307. 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: `<tr>` `<td width=30%> </td>` `<td width=70%> </td>` `</tr>` `<tr>` `<td><!-- Actual Content --></td>` `<td><!-- Actual Content --></td>` `</tr>.`

Database

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

Table 6 Known Limitations in WebLogic Portal Database Interactions

Problem ID	Description
CR106235	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: `SQL> revoke SELECT ANY TABLE from WEBLOGIC 2`
CR107746	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 8.1.7.4 you need to obtain the 8.1.7.4 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 9.2.0.4. For Oracle databases in a Windows environment, Oracle version 8.1.7.4.9 or higher is recommended.
CR108193	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.
CR124126	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.
CR125832	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
CR136171	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: `ToDoAclTable ToDoAclOwnerTable AppointmentAclTable AppointmentAclOwnerTable UniqueIDGeneratorEJBTable ForumAclTable ForumAclOwnerTable TopicSubTable MessageFileTable TopicFileTable DiscussionUserTable ContactAclTable ContactAclOwnerTable Pop3Folders Pop3Messages Pop3Attachments Pop3MessageHeaders Pop3Preferences` 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`.
CR203632	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.
CR235573	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.
CR237251	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 7 lists the known limitations and workarounds stemming from issues involving Compatibility Mode. Support for Compatibility Mode exists only through the SP2 release of WebLogic Portal; this limitation description is shown for reference purposes.

Table 7 Known Limitations in WebLogic Portal Compatibility Mode

Problem ID	Description
CR127580	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

Problem ID

Description

CR127580

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 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	Description
116909	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.
174636	Page flow portlet refreshAction not invoked on nested page flows.
187596	Webflow Portlets Refresh event not being processed in preRender Administration Portal

Limitations Fixed for Portal Framework

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

Limitations Fixed for Database

CR Number	Description
174613	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	Description
110697	Non-portal web applications using p13n_controls will see many generated EJBs in the `config.xml` file.
112171	WebLogic Workshop does not merge application configuration files or deployment descriptors upon application or project import.
120301	Cannot create an entitlement using the CONTAINS operator with a user profile property.
124038	Some custom layouts might not be displayed correctly in the WebLogic Workshop portal builder.
129070	Portal will not start up in a cluster with Domain Administration Port enabled.
181148	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.
183554	Configuration needed for a non-portal project to serve as a WSRP producer.
183650	Using WSRP producer portlets in a non-portal web app.

Limitations Fixed for Administration Portal

CR Number	Description
110422	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.
111461	Cannot add Document Manager or Document Connection Pool Service via the Administration Portal.
120390	Cannot login to the sample Avitek portal.
173371	Console SocketException in the Administration Portal, Portal Management page when viewing a disassembled portal node.
180492	Single quote character for user/group property values is not supported in the online tools.
181726	Newly created Delegated Administration Role is missing from Administration Portal.
187817	Portlet title should be shown as read-only in the Administration Portal.

Limitations Fixed for Portal Framework

CR Number	Description
126625	Potential case sensitivity differences between Entitlements, User Profiles and Authentication Providers.
127941	LDAP UUP does not allow for LDAP-S.
175321	Renaming the web application context causes a ServletException.
175730	JdbcSequencer lock contention occurs in a cluster, causing transaction rollback.
177374	An error occurs when SERVER_NAME is specified in the start script for a managed node.
179773	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 5.
182459	Unused attribute on `ugm:createUser` tag.
186863	unifiedProfileTypeCache needs to be renamed in `<APPLICATION>/META-INF/ application-config.xml`.

Limitations Fixed for Search

CR Number	Description
107379	AutoIndexer exits when a directory name that doesn't exist is specified.
107382	Portal search engine administration tools do not display an error if a process doesn't start.
108840	Portal search engine does not remove content when a search is deleted.
187006	Portal search engine fails to run on certain operating systems.

Limitations Fixed for Database

CR Number	Description
182875	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	Description
112717	Page Flow Portlet behavior changed so that default action (begin) is not called at page refresh.
112841	The 'taxonomy' parameter is no longer required for UserInfoQuery portal control.
122325	URL rewriting for PageFlow Portlets has changed so that portletInstanceLabel_actionOverride=/modulePath/action instead of just portletInstanceLabel_actionOverride=action.
124687	Standalone page flows do not honor the {url:securePort} token within url-template-config.xml.
126885	Microsoft SQL Server 2000 case-sensitive settings may affect Content Management queries.
127365	The mailmanager script has incorrect username and password.
129432	load_cm_data.cmd displays a NoClassDefFoundError when the CLASSPATH environment variable is too long.
129434	User or group creation appears to fail in a cluster with Default Authentication Provider.

Limitations Fixed for Administration Portal

CR Number	Description
101788	Tree Framework error in large trees.
109665	Exceptions with content preview for nonexistent user.

Limitations Fixed for Portal Framework

CR Number	Description
107125	HTML entity references not supported.
108453	"Input Line Too Long" errors on starting WebLogic Server.
109791	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.
110846	P13N request wrapper implements getRemoteAddr(), getRemoteHost().
112873	Password of the principal in LDAPPropertyManager configuration needs to be encrypted.
123269	Sample NT service script for WebLogic Portal.
124296	Portal pages rendered by Netscape 7.0 have oversized width for column.
126027	DRE port number incorrectly specified in ODBCFetch file.
126180	JavaPortlet container throws NullPointerExceptions when weblogic-portal is present in a portal web app.
126841	The `visible` property for an editable book may not reflect the accurate value.

Limitations Fixed for Search

CR Number	Description
099268	Portal search engine is not able to index some languages.

Limitations Fixed for Third-Party Tools

CR Number	Description
109446	A change of language is not detected if a user is logged in.

Limitations Fixed for Database

CR Number	Description
120519	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	Description
106765	When using the directory restriction feature of the My Content sample portlet, content nodes do not appear.
109773	Portal drag and drop: unsupported drop actions cause portlets and books to disappear in portal design view.
110356	When using the Tracked Anonymous User capability, the `<um:createUser>` JSP tag and createUserControl require the attribute `"doPostProcess"` to be set to "true."
110740	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.
110743	Using browse to set values for selected, rollover, and unselected image properties may result in inaccurate URI.
110746	WebLogic Workshop becomes inoperable and gets WebLogic Server errors when using the Install Portal option from WebLogic Workshop while the server is running.
110753	Unexpected error dialog appears when dragging from calendar picker in campaign, property set, placeholder, segment, discount, and content selector editors.
110830	Receive errors in the WebLogic Workshop Portal Designer when setting "Navigation" and "Editable" properties on a book.
111043	Portal Designer "inverting" unselected and selected page/book images.
111419	Leaving the Rollover Image property blank causes undesirable browser rendering behavior.

Limitations Fixed for Administration Portal

CR Number	Description
108228	Role definitions not updated when users or user groups are deleted.
108918	Unable to create a desktop from a portal template (`.portal` file) that contains a book that holds no pages.
109457	User-group associations with entitlements and delegated administration roles cannot be reformed once deleted.
110201	`UserManagementException` is thrown when updating group properties.
110399	Console error received when modifying a campaign via the WebLogic Administration Portal in an application deployed in enterprise archive (`.ear`) format
110572	Entitlements roles with titles that include apostrophes are not associable.
110716	Delegated administration and entitlement roles cannot be predicated on a User Property Set property of type "Date/Time".
111091	Unable to update clauses based on a "visitor's characteristic" that is based upon a Restricted Date/Time property.
111092	Occasional problems moving page/book order in books in library.
111766	Error when changing the theme of a book instance in a Desktop that has already been changed.

Limitations Fixed for Portal Framework

CR Number	Description
108063	Context root change may cause servlet deployment error.
108349	Startup problems when installing into directory names with spaces.
109937	Deployment of a new portal application may fail when the server is already running.
110091	Changing placement of books/pages/portlets may not cascade.
110476	Tutorial portal: portlet preferences page editing problems.
111175	Cascading style sheets require correct mime-type for Netscape/Mozilla browsers.
111362	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	Description
103202	Yahoo Integration: JavaScript function required to be present for Yahoo! Content.
111161	Collaboration portlets setup instructions incomplete in WebLogic Workshop.