|
|
This document contains information on the following subjects:
| Note: | For updated release notes, consult the BEA documentation web site. |
BEA Workshop for WebLogic Platform™ 9.2 and WebLogic Portal™ 9.2 provide new and improved functionality for building enterprise portal applications, including:
See the supported platform documentation for information about BEA-supported hardware and software configurations.
This release of WebLogic Portal supports the following standards, see
This section describes problems that have been identified in BEA WebLogic Portal 9.2. 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 the following product areas:
Table 2 lists known limitations and workarounds for upgrading WebLogic Portal and Workshop for WebLogic.
Table 3 lists known limitations and workarounds for Workshop for WebLogic framework and development.
|
On Linux, when you create a portal, grab a portlet, and drag it onto the portal, sometimes on drop, the whole Eclipse instance will crash.
Workaround: Avoid drag-and-drop onto .portal, .book, .page, .cam, .sel, .seg, .pla, and the property set types. Use right-click in the editors or the palette view menu to insert items to the file being edited. Additionally, the motif version of Eclipse seems to not exhibit this issue, according to
https://bugs.eclipse.org/bugs/show_bug.cgi?id=74095.
|
|
|
Due to a problem in Eclipse, some JSP tags (such as <auth:login> and <portlet:actionURL>) and variables declared from JSP tags are marked as containing an error when they are actually correct. Although no error actually exists, Eclipse will not publish (deploy) the application.
Workaround: If this situation occurs, you must turn off JSP validation before publishing. Leave JSP validation on until you have fixed any problems except those caused by these tags; before deploying, select Window > Preferences, select Validation in the tree, and uncheck the JSP Syntax Validator check box.
|
|
|
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.
|
Table 4 lists known limitations and workarounds for WebLogic Portal framework and development.
Table 5 lists known limitations and workarounds for content management and search.
IDOL Server does not successfully delete an entry from the index when the file is removed from a directory scanned by FileSystemFetch.
|
|
Using a CM IPagedList or ICMPagedResult across multiple requests in conjunction with a dynamic security role
When a Content Management collection (PagedList or PagedResult) is used across multiple requests, and a security role based on request attributes is used to restrict access to the collection contents, the contents are not filtered according to the current per-request attributes. Instead, the contents are filtered based on the initial request attributes.
|
|
|
Content management's search implementation using Autonomy follows the provider's specific sorting policy. When sorting on a node's property, results are sorted by the value of that specified field. For nodes in which this specified field is empty, results are not returned.
Workaround: With IDOL Server Suir version 5.0.15, there is now a config parameter that can be set to change this behavior. (For WebLogic Portal 9.2, all platforms except for Solaris are using 5.0.15. This can be confirmed by running “content.exe -version”.) This can be set: SortReturnAllDocuments=TRUE Under the [Server] section of BEACMRepoFetch.cfg.
|
|
|
When a user removes a Repository Configuration, data is left in that repository. This also includes search index data in Autonomy when using the BEA Repository. The search database should be cleaned if a repository connection is to be reused and the backing data source has changed.
|
|
|
Paths for the BEA Repository are stored minus the “/Repository” in the database. In order for native sorting and filtering to work on the path value, the user must specify the sort and/or filter criteria with the path minus the Repository data. Typical paths on nodes retrieved from the database via the API are in the form: /BEA Repository/parent/child where “child” is the node's name, and it exists in the “BEA Repository” under the node “parent”. Native sorting and filtering and paging in general is documented in the package Javadoc for the com.bea.content.paging package.
|
|
|
One new feature in WebLogic Portal 9.2 is the ability to create nested property types, which are properties that have the structure of another user-defined type. For nested type properties that allow multiple values, it is not possible to delete individual values. It is also not possible to clear individual properties of nested type property values.
|
|
Binary properties must have filesystem valid characters in the filename to properly index with Autonomy
|
|
|
When a String Property in CM is set to “”, an empty String, it will be persisted as an empty String, not null, in the database. When retrieved from the database, via the Content Management API, it will be a Property with a null Value object.
Property objects with null Value objects are indexed in Autonomy as “_”, for example, <myProperty>_</myProperty>. Property objects w/ empty String Value objects are indexed in Autonomy like: <myProperty/>.
|
|
|
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.
|
|
|
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.
|
|
Content repository configurations created as part of content-config.xml cannot be removed by the WebLogic Portal Administration Console
|
|
|
Shift JIS characters that are used in PDF files (.pdf), Word files (.doc), or Excel files(.xls) do not get indexed at all in Autonomy. This means that if you have any files of those formats in a directory that is to be indexed by the FileSystemFetch utility provided by Autonomy, and those files contain Shift JIS characters, those characters will not be indexed.
|
|
|
If a file name contains any Shift JIS characters, Autonomy will not index them. This means that if a file with Shift JIS characters in the file name are placed in a directory to be indexed by the FileSystemFetch utility, it will not be index by Autonomy. Therefore, that file not be returned within the search results provided by the Enterprise Search portlet.
|
|
Autonomy search engine and fetch processes might not start properly on Unix platforms due to missing linked libraries
Autonomy executable files and shared libraries require certain system libraries to be installed and accessible, via the library path, in order to start properly. If your target server does not have these libraries, one or more of the following processes might not start: AutonomyDiSH.exe, AutonomyIDOLServer.exe, content.exe, category.exe, community.exe, agenstore.exe, BEACMRepoFetch.exe, FileSystemFetch.exe, HTTPFetch.exe.
|
|
|
Autonomy does not allow the following characters to be used in the DREFIELD name: Spaces, commas, and +, #, &, `, ", <, >
Therefore, if a Content Management property has any of those characters in its name, it will be escaped. The illegal characters are replaced by a dash and the last 2 characters in its ascii hex translation. This can cause unwanted results to be returned when querying on a property name (userPropertyField) using wildcards and specific characters. The specific characters are one or both of the following: “7E”, “20”, “2C”, “2B”, “23”, “26”, “60”, “22”, “3C”, “3E”. For example, searching on a wildcarded property name like “*3*”, would return any of the properties that had a greater than or less than symbol in it, because those names would have been escaped with “-3C” or “-3E”.
|
|
Encoding properties for Autonomy IDOL Server are incorrectly set for Japanese EUC and Japanese JIS languages
The encoding properties are incorrectly set for Japanese EUC and Japanese JIS language types in the AutonomyIDOLServer.cfg file. The encodings are set to UTF8 rather than EUC and JIS, respectively. This may impact the ability for Autonomy to index content created with these language encodings.
|
|
CommandFailed errors possible during server startup when Autonomy is auto-started by server start script
“Unable to create the Content FullTextSearch database associated with repository Shared Content Repository due FullTextSearch engine error.”
These messages are logged when Content Management attempts to communicate with Autonomy, if Autonomy is not fully running.
Usually the error is harmless and can be ignored. See below for additional information on how to determine if the error is meaningful.
This should only occur if Autonomy runs on the same host as the server, and the domain start script starts Autonomy. If Autonomy has been manually started, this issue should not occur. In a production environment, Autonomy should be started before WebLogic Server is started, so this issue should not occur.
Additionally, this behavior can only occur if at least one repository exists with both the search and search indexing repository properties set to true. (both default to true when a repository is created)
This behavior occurs because the default server start script starts Autonomy asynchronously, and Autonomy may not yet be fully running when App deployment begins.
WebLogic Portal waits up to 3 minutes per repository for Autonomy to be running, then will continue startup (and app deployment) without Autonomy. WebLogic Portal repeatedly attempts to communicate with Autonomy during this period. The error is logged approximately every 5 seconds, when communication is not successful.
|
|
|
<Jun 13, 2006 7:02:56 PM IST> <Error> <Search> <BEA-415611> <Unable to create the Content FullTextSearch database associated with repository Shared Content Repository due FullTextSearch engine error.
|
Table 6 lists known limitations and workarounds for federation.
|
When LocalProxy is enabled for WSRP, the client becomes responsible for sending cookies, especially the session cookie.
|
|
|
If the Beehive JSF application factory is in place, Beehive throws an exception because the request is not of the expected type.
Workaround: In order for this to work, the end developer must package the Sun JSF bridge as a library module. The library module must appear AFTER the framework library modules in the weblogic.xml.
The reason that the bridge must be packaged as a library module is due to the way in which JSF merges descriptors and plugable factories. Descriptors and plugable factories are processed in reverse
CLASSPATH order. If the Sun JSF bridge comes BEFORE the WebLogic Portal JSF adapter, the Sun JSF bridge will shadow the WebLogic Portal JSF adapter, rendering the WebLogic Portal JSF adapter non-functional.
|
|
|
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.
|
|
After registering with a producer via Workshop for WebLogic, cleaning up the database would cause the producer to be inaccessible via the consumer
|
|
|
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.
|
|
|
The most common cases this would occur is when a remote portlet uses the popup mechanism in page flows, or when a user floats a remote portlet using the float button. If the producer is setup to use consumer-supplied URL templates, WebLogic Portal producer would cache those templates in a session created on the producer. However, when multiple views of a portlet are created either through page flow popup mechanism, or through float buttons, the cached templates may not be valid for the current view.
|
|
isStrict flag in wsrp-producer-config.xml when set to true causes registration to fail only in a specific case
The isStrict flag only applies to registration properties that have a restricted set of values defined and will cause registration to fail only when:
|
|
|
Axis' WSDL2Java will fail when the WSDL-URI is a producer's WSDL (e.g http://localhost:7001/producer/producer?WSDL). Wsdl4j will also fail when processing a server's WSDL.
|
|
|
When using a sample domain (or one copied from another computer) on a computer which has never created a WebLogic Portal domain, WSRP requests may fail with the following error:
|
|
|
When using a grid control in a producer portlet, the grid state (such as pager models, sort models and filter models) which is dependent upon request parameter values must be set up in an action. In general for producer portlets, request parameter values do not propagate from the blocking interaction to markup operation.
|
|
Table 7 lists known limitations and workarounds for collaboration.
|
Workaround: When a GroupSpace is deleted, one should remove the CM content associated with that GroupSpace. To do so, access the WebLogic Portal Administration Console and browse to Content > Content Management.Then in the Virtual Content Repository browse to:
Community_Repository/GroupSpace/<portalAppName>/
|
|
After receiving an error in the Collaboration Portlets, the “Return to Portlet” link doesn't restore the view of the portlet
After receiving an error in the Collaboration Portlets, you have a link to “Return to Portlet”. Under certain error situations, you will fail to restore the view of the portlet and result in you being returned to the portlet error page. These error situations are related to portlet continuing to re-execute the same logic while trying to restore the portlet.
|
|
Within the GroupSpace Issues, GroupSpace GroupNotes, and GroupSpace Docs portlets any folder or item that has an apostrophe (') can not be deleted by clicking the 'Delete' button on it's details page
|
|
|
<WARNING> Can't find the primary instance for the portlet "/visitorTools/communities/view/viewCommunities.portlet". The portlet will be served in file mode.
|
|
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”.
|
|
In GroupSpace, you receive an exception in the portal window when clicking on item in notification center
When clicking on an item (such as a task, calendar event, mail message) in the notification center, the portal attempts to launch the appropriate Collaboration Portlet to view that item. If that item has been deleted prior to clicking on the item in the notification center, you receive an error in the portal window because the item cannot be found.
|
|
Searching by keyword in the Discussion Forums portlet does not handle multiple search keywords correctly
When searching forums and topics in the Discussion Forums portlet, if you enter multiple words in the keywords search field, the words are used as a single search term. Expected behavior would be to parse the keywords and matched or against the forums and topics keywords field, not as a single keyword search.
|
|
A stack trace beginning “javax.servlet.ServletException: No community context” is seen if 'Manage Saved Searches' is pressed while the 'Add Related Items' dialog is opened
If the Add Related Items dialog is opened and the Manage Saved Searches button is clicked, a stack trace will show in the dialog that starts out “javax.servlet.ServletException: No community context” and the saves searches do not show up and can not be managed. Either close this dialog or click the Done button to return the dialog to a regular state.
|
|
Receive a “Resource Key Not Found” error in the WL console when unable to load the Mail Retrieval Timer
|
|
When a GroupNote is placed in Display Mode, links to related GroupNotes within the GroupNote are not honored
|
|
|
When adding/editing a topic in the Discussion Forum portlet, if the body property is left blank, an exception is thrown when trying to view the topic. At this point, you will be unable to view or edit the topic without the exception being thrown, causing you to log out and back into the portal to clear the exception.
|
|
|
Invalid mail messages create multiple entries in the content repository and can eventually fill up the Autonomy database
Workaround: Without the patch: in the portal admin tools, navigate to the Community Templates node and to the template you will use to create your GroupSpace instances. This could be one you create yourself from groupspace.ctmeta, or the GroupSpaceCommunityTemplate. Navigate to the Main Outer Book > Communicate > Communicate Book > Mail node. Tab to the edit contents page and delete the Mail page. Do the same for the Contacts page as well. Better yet, install the patch and use as designed.
|
|
|
In any of the Collaboration Portlets, (Discussion, Mail, Address Book, Tasks, Calendar), if the user enters a value for any text field that is more than 254 characters, they will receive an unrecoverable SQL exception.
|
|
Table 8 lists known limitations and workarounds for Production Operations.
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.
|
|
In the Export/Import Utility, locale resource descriptions are not being propagated to the .pinc file
|
|
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)
|
|
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.
|
|
|
The Propagation Utility uses definition labels and instance labels in order to identify differences between source and destination systems. If a user modifies the definition label of a page instance in the desktop, errors might occur upon the first import containing the modified definition label. However, it does appear that the user can continue to make updates to the artifact with the changed definition label successfully on subsequent imports.
|
|
|
If the user creates and propagates a user role and a policy, and then updates the role and propagates, an error occurs during propagation but the propagation completes successfully. The first portion of the error message is:
<Apr 27, 2005 12:21:08 PM MDT> <Error> <Entitlements> <BEA-402722> <Attempt to perform policy operation failed due to unrecognized error. Operating on resource at "type=<wlp>, EntApp=ent_app_name, Webapp=portal_app_name, Resource=, Capability=" with associated policy “role_name” failed. weblogic.entitlement.data.EnFinderException: Attempt to modify unknown role
|
|
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
When importing a desktop that contains a resource (such as a portlet) that references a markup resource that exists on the source but not on the destination, the server throws an ObjectNotFoundException.
An exception is thrown on the server console. Only the portal node is created correctly on the destination server; the desktop is not created.
|
|
Table 9 lists known limitations and workarounds for WebLogic Portal Administration Console.
The Version History page for a content item throws a RepositoryRuntimeException for folders containing no content items
A folder item which contains no nested content items will throw a RepositoryRuntimeException upon accessing its Version History page. Folders are unique in that they are content items, but have no version history. In previous releases, the WebLogic Portal Administration Console would instead tell the user that “This item has no versions”.
|
|
Content Management: Adding property definitions to a type that has been instantiated may result in problems editing content of that type
A content type can be modified with additional property definitions after content has been instantiated using that type. However, a content item cannot be assigned property values for properties that were added to the type after the content item was created. Attempting to edit the added properties will result in an exception. Also, adding property definitions to the type that are marked as required will result in an exception the next time existing content is saved. For these reasons, it is not recommended to add property definitions to a type that has been instantiated.
|
|
MissingResourceException occurs when using a JSR168 portlet that was created, by duplication, in the WebLogic Portal Administration Console
A MissingResourceException will occur when a JSR168 portlet that was created in the WebLogic Portal Administration Console is used in a streaming portal. That is a JSR168 portlet that is created in the WebLogic Portal Administration Console’s library by duplicating a JSR168 portlet that was created from a .portlet file imported to the WebLogic Portal database by the server from the filesystem. The exception is caused by the fact that the new (duplicated) portlet gets a new unique definition label when it is created but there is no descriptor entry created in the portlet.xml file with a <portlet-name> matching that new definition label.
Workaround: Create entries in the application’s portlet.xml file for each administration tool created JSR168 portlet. Do this by copying the entry for the portlet from which the administration tool copy was created and modify the <portlet-name> value to match the definition label of the corresponding copied portlet. Do this for each copied portlet and redeploy the application.
|
|
|
If a user uploads a content item into the repository via the WebLogic Portal Administration Console which contains a space in its filename (for example, “My Content Item.jpg”), the Preview and Download functionality for that item will truncate the filename after the first space character (for example, “My”).
Workaround: The binary representation of the item is unaffected -- for instance, a JPEG file can still be viewed in a browser. Upon download, the user may wish to rename the file manually and reinsert the spaces and extension. Or, to avoid this issue altogether, users may wish to remove any spaces from filenames prior to uploading them into the content management system via the WebLogic Portal Administration Console.
|
|
WebLogic Portal Administration Console tools context-sensitive help is not available if browser does not contain en_US as an available locale
PAT On-line Help System: admin tools context sensitive help is not available if browser locale is “English [en]”.
|
|
|
The Service Administration section of the WebLogic Portal Administration Console provides the ability to manage (and flush) cache configurations which are used by the WebLogic Portal runtime. However, several caches must be added to the configuration before they can be managed or flushed via this tool.
Workaround: The cache can be added manually via the Service Administration by selecting that tool and clicking on the Cache Manager entry in the tree. Then click the Add Cache button on the resulting page. Enter the name of the cache which should be made manageable. The name of the cache must entered exactly as it is named in the related documentation for the feature to which the cache applies (For example, the Interaction Management documentation references the adServiceCache cache. To make this cache manageable, add the adServiceCache exactly as written.)
|
|
Content repositories created via the WebLogic Portal Administration Console do not appear to be deleted and exceptions are thrown to the console
|
|
Table 10 lists known limitations and workarounds for WebLogic Portal Security.
Delegated Administrators of content must be given explicit access to nested content types and workflows
When a user is given Delegated Administration rights to a particular piece of content of type, he/she must also be explicitly be given rights to any nested types or workflows related to that content. If not, the user will be prevented from modifying the content type with an error message similar to, “User does not have view privileges to view this type or its properties”. In the case of Workflows, the user will be unable to conduct a search on the Version History of the content item.
|
Table 11 lists known limitations and workarounds for third-party tools associated with WebLogic Portal.
|
When using Internet Explorer, the hyperlinks to communities in the View My Communities dialog and the Community Wizard may not work correctly. Clicking the link may have no effect.
Workaround: End-users can use a browser other than Internet Explorer to access their communities using these dialogs. Also, users can access the list of available GroupSpaces by going to
http://{domain}/{webapp}/groupspace.jsp. Otherwise, they will need to keep track of the URLs of their communities from the corresponding invitations. Administrators can view the URLs and link to communities through the WebLogic Portal Administration Console.
|
|
|
Autonomy ODBC Fetch license shipped along with WebLogic Portal 9.2 and 9.2.x returns an error at the startup as the license has expired.
|
This section lists limitations that were fixed in BEA WebLogic Portal 9.2 MP3. The resolved limitations are grouped by the following topics:
Review the security advisory information at
http://dev2dev.bea.com/pub/advisory/264.
|
|
Initial WSRP custom data transfer requests were not working between WebLogic Portal consumer and WebLogic Server producers. For example, after launching the consumer portal and logging into the application, the user ID that was transferred from the local portlet to the remote was not being displayed. Only the subsequent requests such as logout and login were working.
|
|
When the library was updated by choosing the option Keep Portal Resources already in the Library or Replace markup with Template version, an error message was displayed. This problem occurred when the library was updated by creating a new desktop with an updated page that was modified by renaming the page using Visitor Tools and by adding a book to the renamed page using Workshop.
|
|
Review the security advisory information at
http://dev2dev.bea.com/pub/advisory/232.
|
This section lists limitations that were fixed in BEA WebLogic Portal 9.2 MP2. The resolved limitations are grouped by the following topics:
|
The propagation tool verifies whether the database and LDAP are in sync before starting the
onlineDownload and onlineCommit operations. If the tool detects a synchronization issue, the propagation session will halt. However, the session can be restarted using a modifier, continueOnValidationError, in the ant task.
|
|
The following types of JavaScript errors used to occur on an OOTB Links portlet in a GroupSpace application:
|
|
When a desktop was imported to a new environment after changing the default order of portlets and pages in which they appear on a Web page, the modified order for portlets and pages was not retained during propagation. Instead of retaining the modified order, portlets and pages used to default to the original order in the .portal file.
|
|
This section lists limitations that were fixed in BEA WebLogic Portal 9.2 MP1. The resolved limitations are grouped by the following topics:
When redirecting within a pageflow's begin or redirect action, a warning message was being displayed in the WebLogic Server console, because redirects are not supported in these actions in case the portlet is to become a WebLogic Server Remote Portlet producer. However, there are two warning messages for each redirect in one of the above actions.
|
|
Moving a portlet from one page to another used to corrupt the database. When changes were made at the admin or desktop level and were propagated down to user desktops (that is, to users who have customized their desktops), the wrong instance of the portlet was being placed on the user's desktop. This problem did not occur when WebLogic Portal Administration Tools were used; it used to occur sometimes when the Propagation or XIP tools were used to propagate administration level changes. The problem could also occur with custom code that used the Portal persistence API to move portlets.
|
|
|