BEA WebLogic Portal 10.2 Release Notes

Table 1 Java Standards
Standard	Version
JSF - Sun Reference Implementation	1.1, 1.2
Struts	1.1, 1.2
Beehive	1.0.1
JSR 170 and JSR 170-compliant repositories	1.0 Level 1 and Level 2 (excluding optional features)
JSP	2.0
JSTL	1.1, 1.2

Table 2 Known Limitations and Workarounds for Installation
Problem ID	Description
CR357639	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.

Table 3 Known Limitations and Workarounds for WebLogic Portal and Workshop (WorkSpace Studio)
Problem ID	Description
CR275922	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 com.bea.p13n.org.jdom.* 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 com.bea.p13n.org.jdom.*.
CR341128	Potential java.io.InvalidClassException 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: `java.io.InvalidClassException: javax.xml.namespace.QName; local class incompatible: stream classdesc serialVersionUID = 4418622981026545151, local class serialVersionUID = -9120448754896609940` 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: `com.sun.xml.namespace.QName.useCompatibleSerialVersionUID= 1.0` 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= 1.0`
CR348307	Fatal error when upgrading domain with RDBMS Authenticator Since WebLogic Portal 10.0MP1, the security provider configurations can only be upgraded when the provider is located in a particular directory. The domain upgrader issues a fatal error when a custom security provider is used in a domain where the upgrade framework cannot find the provider implementation. The P13N RDBMS authentication provider has been deprecated since WebLogic Portal 9.2 and is no longer installed to WebLogic security provider directory. This fatal error occurs when upgrading a WebLogic Portal domain that still uses RDBMS authentication provider. Platform: All Workaround: Copy the `<BEA_HOME>/wlserver_10.0/common/p13n/lib/deprecated/rdbmsAtnProvider.jar` to `<BEA_HOME>/wlserver_10.0/lib/mbeantypes` before running the domain upgrader.
CR361207	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.
CR362719	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".
CR363547	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.

Table 4 Known Limitations and Workarounds for Workshop Framework and Development
Problem ID	Description
CR275545	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.
CR278318	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.
CR337772	Portal domain's version in config.xml is 10.0.1.0 The `<configuration-version>` element in a new Portal domain's config.xml refers to version 10.0.1.0 rather than 10.2. Platform: All Workaround: None, works as designed.
CR351036	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: [BEA][DB2 JDBC Driver][DB2]USER1 DOES NOT HAVE PRIVILEGE TO PERFORM OPERATION SELECT ON THIS OBJECT SYSIBM.SYSDUMMY1 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;
CR357922	Some Workshop 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'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 property sheet. Validation warnings for referencing non-existent actions are suppressed. Workshop does not support the Ctrl+hover gesture used to click-through to navigation cases in faces-config.xml. Platform: All Workaround: None.

Problem ID

Description

CR221434

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.

CR270564

KeyBootstrap class failed to generate keys

Because of incompatible use of domain-scoped start up classes, commerce applications built using BEA commerce functionality do not support the use of application-scoped JDBC pool.

Platform: All

Workaround: None

CR270742

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

CR270887

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

Workaround:

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.
Assign all proxy portlets to a different group. The downside of this option is that remote portlets that wish to share state cannot.
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.

CR271035

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);
redirectURL.setDomain("www.yahoo.com");
redirectURL.setPort(80);
redirectURL.setPath("/compressedUrl/index.html");
redirectURL.setTemplate("no_compression_template");

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.

CR275621

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.

CR280098

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:

CR287496

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.

CR309678

Limitations of Portal 10.0 Look & Feel files related to Netscape 7.1

The Portal 10.0 look and feel files are generally considered to be incompatible with Netscape 7.1 due to an incomplete implementation of modern standards for web-based applications, such as CSS. Because the Portal 10.0 look and feels are based on these modern standards, users of Netscape 7.1 can expect to encounter problems with many aspects of these look and feels. Problem areas include: layouts, multilevel menus and image rollovers.

Platform: Netscape web browser version 7.1

Workaround: Upgrading to Netscape 7.2 should resolve many of these issues, and upgrading to Netscape 8.x should resolve ALL of these issues. Alternatively, the "legacy" look and feel can be used as it was designed specifically for older browsers.

CR309719

Deprecated versions of the Look and Feels (for example, Classic) do not support the 10.0 AJAX portlet implementation

The behavior of the 10.0 AJAX implementation is nondeterministic when used with the deprecated Look and Feels.

Platform: All

Workaround: Use disabled or compat_9_2 mode. See Javadoc for com.bea.netuix.application.definition.DesktopDefinition.setAsyncMode.

CR318064

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.

CR322670

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.

CR339012

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 com.bea.wlp.rest.command.MethodPermission to perform custom access checking and configuring via rest-config.xml.

CR339021

Default polling changed from 3 to 5 seconds

The default polling interval has been increased. This interval is set in the system property:

-Dcom.bea.p13n.management.ApplicationFilePoller.sleepInterval

Platform: All

Workaround: None.

CR340097

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:

Platform: All

Workaround: Remove any spaces in the Portal EAR project name.

CR342124

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.

CR342843

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.

CR344368

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:

<jsp:scriptlet>
   javax.faces.context.FacesContext.getCurrentInstance().get
      Application().
   getVariableResolver().resolveVariable(javax.faces.context
      .FacesContext.
   getCurrentInstance(), 'myVar');
 </jsp:scriptlet>

CR344822

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.

CR344835

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

CR348667

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.

CR358125

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.

CR359073

Harmless error message logged by Lease Manager

The following error message is logged by Lease Manager, which is harmless and can be ignored.

<BEA-403302> <An unexpected SQL exception occurred java.sql.SQLException: Data exception -- row already exist in index PK_LEASE on table P13N_LEASE.

The error is logged only in cluster environment when two or more nodes are concurrently trying to acquire the same lease.

Platform: All, in a clustered environment.

Workaround: None, not required.

CR359274

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.

Problem ID

Description

CR252817

It is now possible to distinguish null or empty values from values containing "_" in Autonomy

This release no longer uses "_" to distinguish null or empty values, it uses "_WLP_CM_NO_VALUE_". This fixes an issue in which application property values of "_" were incorrectly considered as having no value.

Platform: All

Workaround: Users must re-index their content to take advantage of this feature. Until content is re-indexed, queries created via IMetadataQuery.buildIsNull and IMetadataQuery.buildIsNotNull will return incorrect results.

CR271236

Metadata search returns incorrect results for '' or NULL queries in some databases

In Oracle, the blank character is considered the same as NULL, which means that customers will not be able to differentiate between them if they are using Oracle. However other databases do make that differentiation correctly. In 8.1 all instances of '' were converted to null for every database. BEA has changed that in 9.2 where WebLogic Portal does make that conversion, but it is left up to the database to decide whether that will work or not.

Platform: All

Workaround: None

CR271818

Size of binary node in BEA Content Repository depends on length of timeout set on the system

When adding a binary node to the BEA Content Repository, the maximum supported binary size will depend on the transaction timeout set on the server. The default is 30 seconds but should be set higher if binary sizes larger than 20MB (although this size will depend on many factors including: database vendor, type of binary, speed of machine, OS, etc.) will be used.

Platform: All

Workaround: Set the system timeout to a value larger than 30 seconds.

CR288830

Using CM Full Text search on Windows 2000 requires PsKill to be installed and available in the PATH

On a Windows 2000 host, Content Management Full Text Search requires the PsKill utility to be installed and available in the PATH. This is used on a development host to properly shut down the Full-Text Search processes when the domain is shut down. The PsKill utility can be found at: http://www.microsoft.com/technet/sysinternals/ProcessesAndThreads/PsKill.mspx After installing it, run the pskill command once to accept the license. Make sure it exists on your system PATH, and then restart the server. The scripts can now properly shut down the Full Text Search processes.

Platform: Windows 2000 only.

Workaround: Manually kill the Full Text Search processes.

CR295027

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.

CR305342

CM metadata search using PointBase database and containsall operator can fail

With PointBase, CM metadata searches using the containsall operator, such as color containsall('red','blue') may result in a javax.transaction.HeuristicMixedException wrapping a connection failure java.io.EOFException, due to an underlying PointBase issue.

Platform: Any using PointBase.

Workaround: Use another database, or run multiple 'contains' queries, one per value, and combine results in-memory to produce the same behavior as the 'containsall' operator.

CR321652

Workflow status is not preserved for propagated content items in a managed repository

During propagation the workflow state of the content nodes that were published on the source appear as "Draft" on the destination.

Platform: All

Workaround: Manually go into the destination nodes and publish each of them individually.

CR341954

The not (!) operator with a contains clause does not work for a multi-valued property

Content management metadata search does not support the (!) operator with a multi-valued property when used in conjunction with a contains clause. For example the expression !(tags contains 'gorilla') will return incorrect results if tags is a multi-valued property.

Platform: All

Workaround: In some cases you may be able to use a containsall, such as !(tags containsall ('tiger','gorilla')), which returns all nodes whose tags property does not contain the term "tiger" or "gorilla".

CR342794

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:

CR344651

Unclear exception when using CM versioned repository API

The following cryptic message is displayed:

Caused by: java.io.IOException: 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.

CR350495

Cache rename, new cache defaults for Virtual Content Repository (VCR) searchCache and BEA 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 BEA repository explicitPropertyCache has been renamed to repo.explicitPropertyCache to be consistent with other BEA 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.

CR352246

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

SpellCheckCorrectMinDocOccs=1

For example, this query with the default setting:

ITextQuery tQuery = FullTextQueryFactory.getTextQuery(); 
ITextQueryParameter textCriteria = tQuery.buildEquals
   (new String[] {'*Propagation*'}); 
IFullTextSearch fullTextSearch =  
   FullTextSearchFactory.buildFullTextSearch(null,
   textCriteria, false); 
Search search = new Search(repositoryPath, -1, null,
   fullTextSearch, true); 
ISearchManager searchManager =    ContentManagerFactory.getSearchManager(); 
IPagedList<Node> nodes = searchManager.search(context,
   search);

would receive hits when the word "Propagation" appears in 5 documents.

If the setting:

SpellCheckCorrectMinDocOccs=2

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.

CR353875

Filtering on search results from IVersionManager.search() is not available on the modifiedDate property

The API ISortableFilterablePagedList.getAllFilterableProperties() indicates for the result of the IVersionManager.search() 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.

CR355982

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.

CR358426

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');
ftqp.setMultiplicity(IMetadataQuery.Multiplicity.multiValued);
IFullTextSearch fullTextSearch =
FullTextSearchFactory.buildFullTextSearch(ftqp, null, false);
Search search = new Search(repositoryPath, -1, null, fullTextSearch,
true);
IPagedList<Node> nodes = searchManager.search(context, 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');
mqp1.setMultiplicity(IMetadataQuery.Multiplicity.multiValued);
IMetadataQueryParameter mqp2 = mQuerymQuery.buildNotNull('continent');
mqp1.setMultiplicity(IMetadataQuery.Multiplicity.multiValued);
IMetadataQueryParameter mqp3 = mQuery.buildIsNull('continent');
mqp1.setMultiplicity(IMetadataQuery.Multiplicity.multiValued);

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 = searchManager.search(context, search);

That query would return all planets except for Earth.

CR358475

WevDAV 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 BEA 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.

CR358592

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:

Write down the content repository configuration name. For example, MyRepository.
Shut down WebLogic Server.
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.
Inside the <appName>Plan directory, back up the plan.xml file, and then open it in a text editor.
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.

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

<variable> <name>ContentStore_MyRepository_Name_11484959786870 </name> <value>dctmRepo</value> </variable>

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

<variable> <name>RepositoryProperty_MANAGEMENT_ENABLED_Value_ 114849632622617</name> <value>false</value> </variable>

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.

CR358592
(continued)

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:

<variable-assignment> <name>Cache_nodeCache.MyRepository_Name_11484959788274 </name> <xpath>/p13n-cache-config/cache/[name='nodeCache. MyRepository']/name</xpath> <origin>planbased</origin> </variable-assignment>

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.

For example, these <variable-assignment> element snippets should be fully removed:

<variable-assignment> <name>ContentStore_MyRepository_Name_11484959786870 </name> <xpath>/content-config/content-store/[name=' MyRepository']/name</xpath> <origin>planbased</origin> </variable-assignment>

<variable-assignment> <name>RepositoryProperty_MANAGEMENT_ENABLED_Value_ 114849632622617</name>

<xpath>/content-config/content-store/[name=' MyRepository']/repository-property/[name= 'MANAGEMENT_ENABLED']/value</xpath>

<origin>planbased</origin>

</variable-assignment>

Save the plan.xml file and restart the server.

CR358593

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.

CR358596

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.

CR359853

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.

CR361658

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.

Table 7 Known Limitations and Workarounds for Federation
Problem ID	Description
CR174886	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.
CR252633	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.
CR263920	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.
CR266570	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
CR269002	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
CR272806	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 Workaround: 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 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 (/).
CR334689	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 8 Known Limitations and Workarounds for Collaboration
Problem ID	Description
CR254490	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 "/".
CR273554	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 BEA 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 -database.properties=groupspace_database.properties or for Linux/Unix ./create_db.sh -database.properties=groupspace_database.properties
CR277955	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.
CR288239	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.
CR290182	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.
CR326774	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: http://serverName:7001/appName/SyndicationProducer?searchQuery=cm_createdBy='weblogic'&syndicationStyleName=rss. 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: http://serverName:7001/appName/SyndicationProducer?feedName=TheFeed&syndicationStyleName=rss.
CR359340	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.

Table 9 Known Limitations and Workarounds for Production Operations
Problem ID	Description
CR217697	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.
CR217712	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.
CR217766	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.
CR222321	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.
CR315040	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.
CR315099	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.
CR315916	Customized and non-customized portlet, page and desktop Titles are not visible when viewing Analytics reports. When creating a portlet or page in Workshop, by default the resource's Definition Label will be used in Analytic reports. If a resource's Title is subsequently customized by the Portal Admin Console, that customization should instead appear in Analytic reports after running the Analytics sync script but it doesn't. Platform: All supported WLP databases except Pointbase. Workaround: An Analytics customer can note the original Definition Label assigned to the resource and thereby recognize it in a report.
CR339598	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.
CR345394	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.
CR355824	Error message regarding the export of WSRP portlet instance data is observed when propagating WSRP portlets between consumers that share a common producer When propagating WSRP proxy portlets from one consumer to another, where both consumers share a common producer, an error message similar to the following may be observed on the server console or in the server logs: <Error> <InventoryServices> <BEA-000000> <The WSRP portlet instance data for portlet instance [title: SomePortlet, instance label: T200270341201049234306] could not be retrieved from the producer [handle: SomeProducer]. Reason [com.bea.p13n.entitlements.common.EntitlementsException].> Platform: All Workaround: This message can be ignored provided that both the source and destination WSRP consumers share the same producer.

Table 10 Known Limitations and Workarounds for WebLogic Portal Administration Console
Problem ID	Description
CR259272	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.
CR261581	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.
CR264147	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.
CR288357	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.
CR288516	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.
CR297475	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.
CR360040	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.

Problem ID	Description
CR281901	Multi-value portlet preferences without a value become irretrievable
CR287734	Exception thrown when changing the join type of a DA role expression
CR292404	Content Management searches from the "Search Repository" page will not return results for multi-byte characters
CR304972	Artifacts created with the Portal Administration Tool cannot contain quotes
CR306657	Portal Administration Tool tree node selection links rely on the presence of a tree portlet
CR307191	Changing the "Items per page" on the Delegated Admin. tab may result in a garbled page
CR310577	AJAX requests after session timeout do not redirect to a login page
CR310734	Locale entered without a country code will cause a new locale to be created when updated
CR311066	DA pagination results do not maintain proper state
CR316065	Localization of the title of a group of custom editors in the Portal Administration Console causes MissingResourceException

Problem ID	Description
CR273414	JSP tag variables cannot be resolved in Workshop for JSP

Problem ID	Description
CR267771	8.1.x producer unable to process attachments sent from a 9.2 consumer
CR278336	URL Template Errors logged during deployment of a GroupSpace application
CR309448	If a Content Presenter portlet is configured to point to a template group defined within wlp-template-config.xml, and that template group is then removed from the config file, the user may see a tag error within the portlet
CR279084	Postback URLs used within floated or async portlets will cause loss of state
CR307972	"[ERROR] IdentifierToken" warning message appears in console
CR309704-1	For an Ajax-enabled Desktop (Enable Asynchronous Updates - Enabled), the Cancel button in the Content Presenter Configuration Wizard does not work
CR309704-2	Redirects in Ajax enabled desktops (asyncMode=enabled)
CR313823	MySQL Database CREATION_DATE columns are erroneously updated when UPDATEs occur
CR316435	AJAX requests are not handled properly
CR271244	Cannot disable IFRAME-based asynchronous portlet content rendering

Problem ID	Description
CR248155	Using a CM IPagedList or ICMPagedResult across multiple requests in conjunction with
CR274902-1	Shift JIS characters do not get indexed by Autonomy for certain file formats
CR274902-2	Any files that have Shift JIS characters in the file name will not be indexed by Autonomy.
CR274902-3	Any files that have Shift JIS characters in the file name will not be downloadable due to Autonomy validation
CR249703	Error occurs when a content selector query tries to retrieve a deleted node
CD313904	CM FileSystemRepository does not support Workflow transitions using Bulkloader tool
CR306427	Non-UTF8 Japanese Multi-byte character search keywords in Content Management Full Text Search may not return expected results
CR309852	Intermittent Full Text Search Content Indexing Issue with MySql Server DB
CR311742	Sybase does not return any rows (or an error) with a LIKE value >254 characters
CR313904	CM FileSystemRepository does not support Workflow transitions using Bulkloader tool
CR317024	Binary content without a specified character set may fail to render in the Portal Administration Console or using the Content Presenter portlet

Problem ID	Description
CR270791	Header Search fails for an Admin user
CR277863	Searching by keyword in the Discussion Forums portlet does not handle multiple search keywords correctly
CR315072	The .portlet files in library modules are not picked up automatically by the file poller
CR320034	Creating a GroupSpace Community documentation is incorrect

Problem ID	Description
CR224526	In the Propagation Utility and Export/Import Utility, an error occurs if the user imports a desktop referencing markup that doesn't exist on the destination

Release Notes

BEA WebLogic Portal 10.2 Release Notes

What's New in BEA WebLogic Portal 10.2

Supported Platform Information

Supported Standards

Known Limitations and Workarounds in BEA WebLogic Portal 10.2

Installation

WebLogic Portal and Workshop Upgrade

Workshop Framework and Development

WebLogic Portal Framework and Development

Content Management and Search

Federation

Collaboration

Production Operations

WebLogic Portal Administration Console

Key Limitations Fixed in BEA WebLogic Portal 10.2

Key Limitations Fixed for WebLogic Portal Administration Console

Key Limitations Fixed for Workshop Framework

Key Limitations Fixed for WebLogic Portal Framework

Key Limitations Fixed for Content Management and Search

Key Limitations Fixed for Collaboration

Key Limitations Fixed for Product Operations