CR Number

Description

106765

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

109773

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

110356

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

110740

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

110743

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

110746

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

110753

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

110830

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

111043

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

111419

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

BUG37616

Intermittent deployment error when building/deploying a portal application from in WebLogic Workshop to a running server

Description

When using WebLogic Workshop to build/deploy a portal application with a server running, an intermittent deployment error can occur. The symptom is one or more dialogs that say "Error Communicating with Server." This message is usually harmless, and the deployment succeeds. In some cases, a ClassCastException is also dumped in the server Administration Console log, and the deployment does not succeed. In the WebLogic Server Administration Console, the application may be listed in state "inactive" and the application deployment/removal task may be stuck in state "Running" as shown in the WebLogic Workshop status bar.

Platform

All.

Workaround

If no exception is logged in the server Administration Console, then there is no problem. The deployment is successful, and the error dialog can be safely ignored. If a ClassCastException is logged in the server console, you may need to restart the server and possibly WebLogic Workshop.

CR099156

Make data type terminology consistent throughout the BEA WebLogic Workshop Platform Edition and the Administration Portal

Description

Data types are named differently in BEA WebLogic Workshop Platform Edition and the Virtual Content Repository in the Administration Portal.

Platform

All

Workaround

Please use the following comparison for guidance:

CR103681

Administration portal URL is not updated automatically if the application is renamed.

Description

By default, the standard portal web modules adminPortal.war, wps-toolSupport.war (or toolSupport.war if commerce is installed in the application), and datasync.war use a naming convention for their context paths that is based upon the application name.

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

Platform

All

Workaround

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

1. In WebLogic Workshop, right-click the module

2. Select Edit Context Path.

or,

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

CR106758

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

Description

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

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

Once the segment or selector is opened in WebLogic Workshop, Workshop will update data inside the duplicate file and the parse exception will not occur again nor cause any problems. This is caused by the <cr:name> attribute in the file not getting updated to match the file name for the duplicate file during file duplication.

Platform

All.

Workaround

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

CR109495

A default locale must be configured on all machines running WebLogic

Server

Description

If a default locale is not configured on a machine, and the user running WebLogic server also does not have a default locale configured, the getmessage JSP extension tag will throw this error: a variant cannot be provided without a country, and a country cannot be provided without a language

Platform

Solaris, Linux.

Workaround

Make sure that a default locale is set on the machine(s) running WebLogic Server.

CR110697

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

Description

Portal controls are application-scoped. The controls are packaged and behave correctly for a Portal web application. However, for non-portal web applications, the user will see the individual EJBs deployed (eg, many entries in config.xml) for each portal control.

Platform

All.

Workaround

Workaround: to use Portal controls, do one of two things:

1. Create a Portal web application (recommended)

2. Create a non-Portal web application, and copy the wlw-config.xml file from sampleportal ($BEA_HOME/weblogic/samples/portal/portalApp/sampleportal/WEB-INF) into your web application's WEB-INF folder.

CR110749

Portlets containing Page Flows that were created with the Page Flow Wizard may affect the look and feel of a portal when the page on which the portlet is displayed is selected.

Description

Page Flows which are generated with the Page Flow Wizard create conflicting style sheet settings. These style sheets are loaded by the <netui:template> tags in the generated JSP files associated with the Page Flow. These conflicts can cause the portal to render in unintended fashion.

Platform

All.

Workaround

Edit the JSP files that were generated by the Page Flow Wizard by replacing the following lines

<netui-template:template templatePage="/resources/jsp/template.jsp">

<netui-template:setAttribute value="Index" name="title"/> <netui-template:section name="bodySection">

with

<netui:html>

CR112171

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

Description

When importing an existing portal application into WebLogic Workshop, the WebLogic Workshop will back up the old application configuration files (application.xml and weblogic-application.xml) and create new ones.

The same issue occurs when you import existing Web applications (web.xml and weblogic.xml are backed up and new files are created).

There creation of new application configuration files and deployment descriptors causes two problems:

• The new files do not include entries and modification from the backed up files.

• The new weblogic-application.xml may not have the required <application-classloader> entries.

Platform

All.

Workaround

1. Manually edit the new *.xml files and add the entries that had existed in the old *.xml files.

2. Add <application-classloader> tags around individual modules in the weblogic-application.xml file.

CR112717

PageFlow Portlet behavior changed so that default action (i.e. begin) is not called at page refresh.

Description

In 8.1 GA prior to the fix for CR112717, a portlet's pageflow state was not being persisted, so that when one portlet was being acted upon, all other pageflow portlets would return to their default action. This refresh bug only happened if there was no titlebar on the portlet.

Platform

All.

Workaround

This behavior has been fixed in 8.1 SP2, so any code that was created to work around this issue, might need to be changed.

CR112841

'Taxonomy' parameter no longer required for UserInfoQuery portal control

Description

The taxonomy parameter for the UserInfoQuery portal control has been changed from required to optional.

Platform

All.

Workaround

None. The parameter can safely be removed from the calling code.

CR116909

java.sql.SQLException: Data exception -- string data right truncation on PF_MARKUP_DEFINITION DB table

Description

In WebLogic Workshop, adding portlet preferences to a portlet beyond a certain number causes an XML truncation error

(java.sql.SQLException: Data exception -- string data right truncation)

Platform

All.

Workaround

If you receive this exception:

[javax.transaction.TransactionRolledbackException: EJB Exception: :

javax.ejb.EJBException: SQL Error while trying to UpdateMarkupDefinition on

8002: SQL [update PF_MARKUP_DEFINITION set MARKUP_TYPE = ?, MARKUP_NAME = ?,

WEBAPP_NAME = ?, MARKUP_FILE = ?, BEGIN_XML = ?, END_XML = ? where MARKUP_DEFINITION_ID = ?] database error code [25,201] SQL state [22001] .; nested exception is: java.sql.SQLException: Data exception -- string data right truncation.

Either add these preferences to the portlet via the portal Adminsitration Portal or alter the varchar size of 2 columns (begin_xml/end_xml) in the following table:

CREATE TABLE PF_MARKUP_DEFINITION (

MARKUP_DEFINITION_ID INTEGER NOT NULL,

CREATION_DATE TIMESTAMP DEFAULT CURRENT_TIMESTAMP NOT NULL,

MODIFIED_DATE TIMESTAMP DEFAULT CURRENT_TIMESTAMP NOT NULL,

MARKUP_NAME VARCHAR(255) NOT NULL,

MARKUP_TYPE VARCHAR(20) NOT NULL,

BEGIN_XML VARCHAR(2000) NOT NULL,

END_XML VARCHAR(2000) NULL,

MARKUP_FILE VARCHAR(255) NULL,

WEBAPP_NAME VARCHAR(80) NULL

);

to something larger, for example:

CREATE TABLE PF_MARKUP_DEFINITION (

MARKUP_DEFINITION_ID INTEGER NOT NULL,

CREATION_DATE TIMESTAMP DEFAULT CURRENT_TIMESTAMP NOT NULL,

MODIFIED_DATE TIMESTAMP DEFAULT CURRENT_TIMESTAMP NOT NULL,

MARKUP_NAME VARCHAR(255) NOT NULL,

MARKUP_TYPE VARCHAR(20) NOT NULL,

BEGIN_XML VARCHAR(4000) NOT NULL,

END_XML VARCHAR(4000) NULL,

MARKUP_FILE VARCHAR(255) NULL,

WEBAPP_NAME VARCHAR(80) NULL

CR120301

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

Description

An ExpressionException will be thrown if an entitlement is created with the form:

myUserProfileProperty CONTAINS "sample"

Platform

All.

Workaround

Specifying a default value for the user profile property in Workshop will avoid this issue.

CR122213

Search support for Asian locales is not included in the 8.1 distribution

Description

The "WebLogic Portal Search Support for Asian Locales" package is not included with the 8.1 distribution because of its size.

Platform

Sun Solaris on SPARC, Microsoft Windows on Intel, RedHat Linux on Intel (no support for Japanese).

Workaround

Download the Asian locale package from http://dev2dev.bea.com/codelibrary/code/portal_asian.jsp. The files in this distribution enable Chinese, Japanese, Thai, and Korean to be indexed by the WebLogic Portal 8.1 search engine.

CR122325

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

Description

URLs look like the following:

http://localhost:7001/MyWebApplication/my.portal?_nfpb=true&;myPortletId_actionOverride=/portlets/myPageflow/myAction

Note: Before 8.1 sp2, the URL looked like:
http://localhost:7001/MyWebApplication/my.portal?_nfpb=true&;myPortletId_actionOverride=myAction

Platform

All.

Workaround

If you are manually rewriting the URL (i.e. in a backing file), you will need to add the module path before the action name, to follow the new URL rewriting pattern.

CR123128

Rules expressions will continue to accept 'role' even though it's been deprecated

Description

The rules manager is able to recognize 'special' objects because those have been defined in 'parser-mapping-type.properties' in the expressions package. For example, the ruleset can refer to 'role', which represents the class com.bea.p13n.entitlements.common.Role. But that class has been deprecated.

The Role class is useful to the rules engine because it allows a specific object type (Role) to be identified and inspected, rather than just a String called "PortalSystemAdministrator", for example. This class will likely remain 'undeprecated' and in the public API so the rules authors could use it.

There is no other class available to use at this time.

Platform

All.

Workaround

Ignore the 'deprecated' attribute for the class and continue to use it until a replacement is available.

CR124687

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

Description

https://{url:domain}:{url:secur-Port}/{url:path}?{url:queryString}url:securePort is not understood by Pageflows.

Platform

All.

Workaround

The workaround for standalone pageflows within portal for SP2 is that you can hard code the ports in url-template-config.xml instead of using the token {url:securePort}.

CR126885

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

Description

Microsoft SQL Server 2000 allows users to configure case-sensitive settings for the database server or for each database instance. By default, it is set to case-insensitive.

If you switch to case-sensitive, this may cause unexpected results with Content Management search where queries are written for a specific case setting. Also, wlcs_create_fkeys.sql will require updating of table names to upper case.

Platform

Any Microsoft SQL Server 2000 database.

Workaround

If you change SQL Server 2000 case-sensitivity, check any Content Management search queries and verify that such a change will not alter your application. Update wlcs_create_fkeys.sql by changing table names to upper case.

CR127365

Mailmanager script has incorrect username and password

Description

In <BEAHOME>/weblogic81/portal/bin, the mailmanager.bat and/or mailmanager.sh scripts have the username password to the server set to 'system' or 'weblogic'.

To send email batches with this script, you will need to update the script to have the correct username and password of an Admin or SystemAdministrator user in your system.

This will generally be the system user you specified when you created the domain, or weblogic/weblogic for the sample domain.

Platform

All.

Workaround

Update the script. In mailmanager.bat, update the lines that read:

SET USER=system
SET PASS=weblogic

In mailmanager.sh, update the lines that read:

USER=weblogic
PASS=weblogic

CR129070

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

Description

The cluster communications used by Portal for MBeans and Datasync do not
support use of the Domain Administration Port.

A message such as the following, followed by several stack traces, will be
seen when deploying a portal application to a cluster with the Domain
Administration Port enabled:

####<Nov 25, 2003 10:43:32 AM MST> <Error> <DataSync> <myhost> <server1>
<main> <<anonymous>> <> <BEA-400618> <Creation of the Master Data Repository failed. Application data will not be available to services. Correct the problem and redeploy the application.
java.lang.SecurityException: User <anonymous> does not have access to the administrator port.

Platform

Cluster

Workaround

Do not enable the Domain Administration Port when using Portal.

CR129432

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

Description

load_cm_data.cmd adds several jars to the CLASSPATH environment variable. If CLASSPATH is already set, this could result in a NoClassDefFoundError because the length of the environment variable is too long and the jars containing classes for the BulkLoader cannot be located.

Platform

Windows.

Workaround

Users may need to shorten their CLASSPATH entry or remove the %CLASSPATH% reference from load_cm_data.cmd.

CR129434

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

Description

There is a timing problem with the Default Authentication Provider in a cluster. When a new user or group is created, it takes some time for the provider to update all the cluster members. If an "exists" test is performed during this window, it will show that the user or group does not exist.

Creating a user or group via portal user management (Administration Portal, API, and um taglib) makes such an existence test while looking up the newly created user or group's profile. This causes the creation to report a failure, when actually the user or group and their profile were successfully created.

Note that this condition does not occur with user or group creation; given 10 consecutive user or group creations, all 10 may succeed, all 10 may show a failure, or any number in between may show a failure. This condition is likely to be sporadic and intermittent.

Platform

Windows.

Workaround

If you see an exception when creating a user or a group in a cluster, it may be that the create was actually successful. The symptoms will be:

From the UserManager or GroupManager API - An EJBException eventually caused by a ProfileNotFoundException will be thrown. After a short delay, a userExists or groupExists test will show the user or group does truly exist.

From the um taglib - The result will return CREATE_USER_FAILED or CREATE_GROUP_FAILED, and an EJBException caused by a ProfileNotFoundException will be reported in the server logs. After a short delay, a userExists or groupExists test will show the user or group does truly exist. Note that if you are using the tag to create a group and specify a parent, the group will be created but not added to the parent - it will be a top-level group with no parent. You must re-parent the group to the correct parent.

Administration Portal - Will report the user or group creation not successful, but you can search for the user or refresh the group tree and they will exist. However, if the group you created was to have a parent other than "everyone", or the user was to belong to a group other than "everyone", this group parentage/membership will not be as desired. Groups created that indicate failure will only have "everyone" as a parent, and users created that indicate failure will only belong to "everyone". You will need to manually change this to match your original intent.

CR101788

Tree framework error in large trees.

Description

When displaying a tree in Administration Portal which have a large number of nodes (~ 500) an error message is thrown to the user saying "Script is too long."

Platform

All.

Workaround

The error message: "A script on this page is causing internet explorer to run slowly. Do you want to abort?" is a known issue in Internet Explorer: http://support.microsoft.com/default.aspx?scid=kb;en-us;Q175500.

Press "No" and let the script continue.

CR109665

Exceptions with content preview for non-existing user

Description

If you perform a content preview in the Administration Portal for a non-existent user (for example you misspell the username) you will see a UserManagerException logged to the server log.

These exceptions are harmless and the tools still function properly (you will see no content for this user).

Platform

All.

Workaround

Use valid usernames or ignore the exceptions.

CR109982

Content Repository cannot be modified if the application is deployed as an enterprise archive (.ear).

Description

Users are not able to add, edit, or remove a Content Repository using the WebLogic Administration Portal when the application is deployed as an enterprise archive (.ear).

Platform

All.

Workaround

Deploy the application in an exploded format using a directory-based URI or shut down your server and manually edit the application-config.xml file in the enterprise archive (.ear).

CR110422

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

Description

When you create a new user in the top-level node of the Browse User-Groups tree, the user is created successfully. However, the resulting page offers a new username link to let you edit the newly created user. The link contains an error, and the result is that the link does not work. A JavaScript error is reported by the browser.

Platform

All.

Workaround

To immediately edit the newly created user, follow these steps:

1. Select the "everyone (All Users)" group.

2. Select the Edit Users page.

3. Search for the newly created user.

4. Click the name of the newly created user.

CR111461

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

Description

When attempting to enable the Document Manager and/or the Document Connection Pool service via the Service Administration section of the Weblogic Portal Administration Portal, the services are not added and no indication is given of failure.

Platform

All.

Workaround

The Service Administration section of the Weblogic Administration Portal is a UI for managing the contents of the application-config.xml file found in the META-INF directory of your WebLogic Portal Enterprise Application. To enable the Document Manager service and/or the Document Connection Pool service for your application, you may follow this procedure:

1. Undeploy your application via the Weblogic Server Console

2. Add the following to the application-config.xml file in the META-INF
directory of your application, replacing the values as appropriate for your application:

For the Document Manager service:
<DocumentManager
Name="default"
DocumentConnectionPoolName="default"
PropertyCase="none"
MetadataCaching="true"
MetadataCacheName="documentMetadataCache"
UserIdInCacheKey="false"
ContentCaching="true"
ContentCacheName="documentContentCache"
MaxCachedContentSize="32768"
/>

For the Document Connection Pool service:

<DocumentConnectionPool
Name="default"
DriverName="com.bea.p13n.content.document.jdbc.Driver"
URL="jdbc:beasys:docmgmt:com.bea.p13n.content.document.ref.RefDocumentProvider"

Properties="jdbc.dataSource=weblogic.jdbc.jts.commercePool;schemaXML=./dmsBase/doc-schemas;docBase=./dmsBase"
InitialCapacity="20"
MaxCapacity="20"
CapacityIncrement="0"
/>

3. Redeploy your application.

At this point, you will be able to manage these services via the Weblogic Administration Portal Service Administration section.

CR123835

In Administration Portal deployed as an ear, the placeholder preview does not use the correct tools webapp name, and therefore the images do not show up correctly.

Description

The Placeholder preview under Interaction Management in the Administration Portal does not use the right webapp name for image previews. It appears to use the deployed app name + "Tools".

This works fine when you're running the application exploded, but if the application is deployed as an .ear to an application name other than the original name, the image preview link uses the wrong application name, and the image is not found.

Platform

All.

Workaround

By dropping the .ear in a running server, the Application Name is generated, and is different from the name of the .ear file, one would imagine different from the desired application name.

You can resolve this by doing the following:

Open the WebLogic Server console

Remove the application that was just generated and deployed (should be something like '_appsdir_earFileName_ear')

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

This will give the application the same name as the tools application, and the preview will then start working.

CR127580

Options not visible in Compatibility Mode Administration Portal.

Description

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

Platform

All.

Workaround

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

CR128661

Portal Content Management Administration Portal running on HP-UX 11i requires HP JVM 1.4.1.06 or higher

Description

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

Platform

HP-UX11i with JVM 1.4.1.06.

Workaround

Use HP JVM 1.4.1.06.

CR107125

HTML Entity References are not supported.

Description

SAX parser exceptions are visible in the console if HTML entity references are put into .portal/.portion/.pinc/.portlet files.

Platform

All.

Workaround

Remove the HTML entity references, replacing them with either XML character escape sequences or the UTF-8 encoded version of the character directly in the file. If neither of these is possible, the entity reference can in most cases be put into either the .jsp referenced by the control's content URI, or in a skeleton .jsp.

Note: .portal/.portion/.pinc/.portlet files are NOT HTML files, but rather just an XML format specified by the referenced schemas in the root portal element. Since these files are schema validated in certain parts of the portal framework, HTML entity references are not allowed.

CR108453

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

Description

An "Input Line Too Long" error can occur from the startWebLogic.cmd scripts, depending on which products the domain/server includes, if 1) the installation path for the product is too long, or 2) too many additional entries are added to the server CLASSPATH. This is a limitation in the Windows command processor. An installation directory with a name of 18 characters or less works fine for unmodified scripts for a platform domain (which includes WebLogic Server, WebLogic Portal, and WebLogic Integration CLASSPATH entries).

Platform

Windows.

Workaround

Install to a shorter directory name. Trim the number of additional server CLASSPATH entries by combining JARs or using Manifest Class-Path entries in a single JAR file.

CR109791

When using Internet Explorer and uploading a file of zero bytes to the Virtual Content Repository in the Weblogic Administration Portal, you receive a warning message that the page has expired.

Description

It is possible to upload a zero-byte file into the Virtual Content Repository in one of two ways: the file itself may exist and be empty; or the file specified to upload does not exist.

If the file does not exist, browsers automatically create and upload an empty new file. Under either scenario, PointBase currently has a bug with zero byte BLOBs, yielding a forward to an error page. However, Internet Explorer will display a message that the page has expired and must be refreshed rather than displaying the appropriate error page.

Platform

All, using PointBase as the database and Internet Explorer as the Weblogic Administration Portal client.

Workaround

None. If you refresh the page, as indicated by Internet Explorer, you will be returned to the previous page rather than have the error message displayed. This behavior is benign.

CR110846

P13N request wrapper implements getRemoteAddr(), getRemoteHost()

Description

Instantiation of a com.bea.p13n.http.Request can be slow when a reverse DNS lookup on the client's network is slow.

Platform

All.

Workaround

As of 8.1 SP2, a p13n-request.properties file has been created to allow a developer to disable the loading of the results of HttpServletRequest.getRemoteAddr() and HttpServletRequest.getRemoteHost() into the p13n request. The default configuration is to disable both of these methods by using p13n-request.properties in p13n_ejb.jar.

The ability to disable the loading of getRemoteAddr() was included in this change because it has the potential to open a socket to the client's machine under some circumstances. If you disable getRemoteAddr() and/or getRemoteHost() then you cannot write rules that use these request properties.

CR112873

Password of the principal in LDAPPropertyManager configuration needs to be Encrypted

Description

The principal credential used by the LdapPropertyManager to bind to an external LDAP server for the retrieval of user properties is stored in an unencrypted form in ejb-jar.xml (in p13n_ejb.jar).

Platform

All.

Workaround

As of 8.1 SP2, the CredentialMBean can be used to store the password in an encrypted form in META-INF/application-config.xml. The encryption of the credential works the same as encryption of credentials in your domain's config.xml (for JDBC connection pools, LDAP authentication providers, etc.). If you were to enter an unencrypted value for the attribute by hand and then save application-config.xml then the value would be encrypted the next time application-config.xml was persisted by the ApplicationConfigurationMBean. The encrypted value is prepended with a string that identifies the encryption algorithm, like this: {3DES}. When the CredentialMBean is read from the file, the Credential attribute is automatically decrypted for you.

The CredentialMBean can be used by any service that requires an unencrypted password (but you want to store it on the filesystem in an encrypted form). Be aware that the key used for encryption/decryption is part of SerializedSystemIni.dat, so the encrypted value is NOT transferable from one domain to another. When migrating your application from one domain to another (staging to production, for example), you would have to enter an unencrypted value for the Credential attribute in application-config.xml and save the file before copying it to the other domain.

For example:

<Credential Name="LdapPropertyManager"

Credential="password"

Username="uid=SomeUserWithReadPermission,ou=people,dc=beasys,dc=com"/>

The name, LdapPropertyManager, is used by the LdapPropertyManager to find this CredentialMBean instance. See the env-entries in ejb-jar.xml in p13n_ejb.jar for instructions to specify this MBean name. The first time that the ApplicationConfigurationMBean is persisted then the Credential attribute will be encrypted. Until a tool is added to the WebLogic Administration Portal for this MBean you can force persistence of the ApplicationConfigurationMBean with the Portal admin tool by making a change to some other MBean that does have a tool, such as a CacheMBean.

CR120851

getPlaceholderGrid().length results have been decremented by one.

Description

The int result of

"GridLayoutPresentationContext.getGridLayoutPresentationContext(request).getPlaceholderGrid().length" has been decremented by one. The results returned by WebLogic Portal 8.1 GA were incorrect.

Platform

All.

Workaround

Appropriate changes may be necessary anywhere getPlaceholderGrid() is used.

CR123269

Sample NT service script for Portal

Description

A portal domain includes a installService.cmd which is used to create a Windows service for starting your server. As documented at http://download.oracle.com/docs/cd/E13222_01/wls/docs81/adminguide/winservice.html it is required that the classpath and Java options be set before calling this script. A working sample for setting the variables for the installService.cmd script for a portal domain is not provided.

Platform

Windows

Workaround

You can use the sample startWebLogic scripts to guide you in creating the proper classpath and java options for starting a portal server. A working sample can be obtained from support by referencing this CR.

Note: Commands larger than 2K are not allowed by Windows so the script uses a beasvc.exe workaround to put the CLASSPATH in a text file. This is documented in the sample script and in the WebLogic Server docs at http://download.oracle.com/docs/cd/E13222_01/wls/docs81/adminguide/winservice.html

CR124296

Portal pages rendered by Netscape 7.1 have oversized width for column 1

Description

Portal pages rendered by Netscape 7.1 have oversized width for column 1 of a two-column layout in that column 1 is portrayed on the page with a width of about 90-95% of the browser width whereas it should 30% according to the layout for the out-of-the-box two-column layout (twocolumn.html.txt).

Platform

All.

Workaround

Set the width to auto in the layout.css. In the skins/skin name (classic, avitek, etc)/css directory open the layout.css file in an editor and change the first width entry to "auto". Change:

.bea-portal-layout, .bea-portal-layout-grid, .bea-portal-layout-border,

.bea-portal-layout-flow

{

width: 100%;

padding: 0px;

margin: 0px;

}

to:

.bea-portal-layout, .bea-portal-layout-grid, .bea-portal-layout-border,

.bea-portal-layout-flow

{

width: auto;

padding: 0px;

margin: 0px;

}

This change has been made in SP2 to the classic and default skins in the portal WebLogic Workshop template, but did not make it into the avitek skin. If you use the classic of default skin you will find the change described above.

CR125007

Credential MBean does not have a tool for editing

Description

In CR112873 CredentialMBean was added to application-config.xml so that services that require a plain-text password do not have to store the password on the file system in an unencrypted form.

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

Platform

All.

Workaround

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

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

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

3. Change the value back to what it was.

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

The MBean looks like this:

<Credential Name="LdapPropertyManager"

Credential="password"

Username="uid=SomeUserWithReadPermission,ou=people,dc=beasys,dc=com"/>

CR126027

DRE port number incorrectly specified in ODBCFetch configuration file.

Description

The port number for the DRE is incorrectly specified in the ODBCFetch configuration file (PortalSearchODBCFetch.cfg). This prevents ODBCFetch from indexing data to the DRE. ODBCFetch reports the error "Index: Failure [Couldn't retrieve results.]" in the log file.

Platform

Microsoft Windows (2000 and XP) with MS/SQL. This is the only platform supported by BEA with ODBCFetch.

Workaround

In the ODBCFetch configuration file, installed by default in

%BEA_HOME%\portal\thirdparty\search\windows\ODBCFetch, modify PortalSearchODBCFetch.cfg and change the line

DREIndexPort=2001
to be
DREIndexPort=9001


If ODBCFetch is running it will have to be stopped and restarted to pick up the change.

CR126180

Java Portlet container throws NullPointerExceptions when weblogic-portlet.xml is not present in a portal webapp.

Description

The weblogic-portlet.xml file is an optional deployment descriptor that extends portlet.xml for Java portlets. When a portal webapp is deployed without the weblogic-portlet.xml file, the portlet container throws a NullPointerException. This issue applies only to portal web applications created without using WebLogic Workshop.

Platform

All.

Workaround

Ensure that the webapp contains a weblogic-portlet.xml file under

WEB-INF directory with the following contents

<?xml version="1.0" encoding="UTF-8"?>
<weblogic-portlet-app
version="1.0"

xmlns="http://www.bea.com/servers/portal/weblogic-portlet/8.0";

xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="http://www.bea.com/servers/portal/weblogic-portlet/8.0

weblogic-portlet.xsd">

</weblogic-portlet-app>

CR126841

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

Description

When you select a book and make it editable through the menu, the 'visible' property indicates that the edit mode is not visible (visible=false). The default behavior of the mode; however, to be visible (visible=true).

Platform

All.

Workaround

Follow the steps below if you want to make the book edit mode not visible or you want the 'visible' property to accurately reflect its value.

1. Select the book in the design view or document structure.

2. Set the 'visible' property to be 'true'.

3. Set the 'visible' property to be 'false'.

4. Save the portal document.

CR128531

IE6 Limitation on Number of CSS files.

Keywords: CSS, IE, portal display, skin.

Description

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

Platform

All and IE6.0SP1

Workaround

If there are more than 35 CSS files, the contents of all CSS files can be organized into one or more but less than 35 files.

If the contents are merged into one or more files please make sure that CSS class names are unique across all CSS files within a webApp, this is IE requirement.

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

CR133767

Binary content properties are not displayed when the <cm:getProperty> tag is used.

Description

When you use the <cm:getProperty> JSP tag to display the value of a binary content property (such as an ASCII file or an image), the property value is not displayed.

Platform

All.

Workaround

Use the transactionTimeout attribute on the <cm:getProperty> tag, and set it to a non-null positive value such as 300. For example:

<cm:getProperty node="<%=html_document>" name="demographic" transactionTimeout="300" default="No content node found."/>

CR099268

Portal search engine is not able to index some languages.

Description

Chinese, Thai, Japanese, and Korean content cannot be indexed by the portal search engine.

Platform

All.

Workaround

A download is available from http://dev2dev.bea.com/ that enables these languages for all platforms. The one exception is that there is currently no support for Japanese on Linux.

CR105694

Portal search engine creates a new DOS window when starting the Dynamic Reasoning Engine (DRE).

Description

The portal search engine creates a new DOS window when starting the DRE portion of the portal search engine.

Platform

Microsoft Windows.

Workaround

The DOS window disappears when the process is stopped. It must not be closed while the portal search engine is running.

This window is not created during the initial start of the search engine. It is only created if the DRE is started through the Administration Portal.

CR107379

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

Description

When creating a job for the AutoIndexer, if the user specifies a directory that doesn't exist, the AutoIndexer exits.

Platform

All.

Workaround

You should specify a valid directory for the AutoIndexer to index. However, you can edit the PortalSearchAutoIndexer.cfg file in the <WEBLOGIC_HOME>\portal\thirdparty\search\<platform>\AutoIndexer to remove the invalid job entry.

CR107382

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

Description

The portal search engine gives no user feedback if one of the search process fails to start when started via the portal administration tool.

Platform

All.

Workaround

There is currently no workaround for this issue. The Administration Portal correctly display that the process did not start but the user must look directly at the log files for the portal search engine processes to determine why a process could not be started.

CR108840

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

Description

The portal search engine does not remove data related to a particular search job (for example, an HTTPFetch job) from the DRE database when that fetch job is deleted.

Platform

All.

Workaround

There is currently no workaround for this issue. If the user does not want the data from the deleted search job in the DRE database then they must manually remove the data from the DRE database.

Instructions for removing this data is included in the DRE documentation, available in $BEA_HOME/weblogic81b/portal/thirdparty/search/common/DRE (Unix) or %BEA_HOME%\weblogic81b\portal\thirdparty\search\common\DRE (Windows) in the Platform installation.

CR102538

Yahoo Integration: Support of default_locale preference on Yahoo portlets.

Description

Some of the Yahoo! portlets, (e.g. Annual Reports), do not return content if that portlet doesn't support the language chosen by the user. Other portlets will return content in the default locale, en-US.

Platform

All

Workaround

1. In WebLogic Workshop, add a portlet preference called 'default_locale.'

2. Set it's value to the locale you want the portlet to default to.

Note: This locale must be a valid locale as defined in locale.properties and must be fully resolved (i.e. 'fr' is not valid, 'fr-FR' is valid).
This locale is used when the users preferred locale is not supported for that module according to the myee metadata defined in yes_modules_xml.
If the metadata specifies that the default locale is not supported then we fall back on 'en-US'. If 'en-US' is not supported, no content will be returned.

CR103917

Yahoo Integration: A new window should not be launched if linking is disabled.

Description

Users who have enterprise accounts that restrict linking through the 'First Time Activation' deployment setting have no way of turning off redirection to Yahoo! from the portal on a user's first login.

Platform

All.

Workaround

There is not a workaround. Any time a user logs in for the first time, they are redirected to the Yahoo! linking page. If the enterprise account is configured in 'First Time Activation' to 'Skip this page flow', the user will be immediately redirected back to the portal.

CR109446

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

Description

If a user logs in with one language and, while they are logged in, they switch to another language, the Yahoo! portlets keep using the original language that the user logged in with.

Platform

All.

Workaround

A user must log out and back in if they update their language setting once they are logged in.

CR109460

Anonymous user does not see Yahoo! content

Description

After a portal with Yahoo! content has been configured (i.e. set up with portlets, Deployment name/key set up, logged in to set up anonymous user), the Yahoo! content does not show up for the anonymous user on subsequent log ins. Yahoo! content also does not show up for users who are not logged in.

Platform

All.

Workaround

As of this release, Yahoo! content is not available through the portal for anonymous users (users who are not logged in). There is currently no workaround to get content to anonymous users.

As a Best Practice, these portlets should be configured via entitlements to not show up unless a user is logged in so anonymous users will not see an empty Yahoo! portlet.

CR110666

On logout of sampleportal the has Yahoo! content, the user gets four pop-up dialogs saying they are being redirected to secure, then non-secure, then secure, then non-secure

Description

The Yahoo! logout feature is being called twice.

Platform

All.

Workaround

When building a custom portal that is has Yahoo! content, on login and logout there needs to be specific Yahoo parameters passed along with the login/logout (the params are yahoo_login and yahoo_logout.).

Remove the hidden parameters 'yahoo_login' and 'yahoo_logout' from the sampleportal/portlets/login.jsp file. To eliminate when building a custom portal, make sure this parameters are only passed once on login/logout.

CR111328

My Yahoo! Enterprise Edition setup instructions are incomplete in WebLogic Workshop help system

Description

End users of the My Yahoo! Enterprise Edition portlets may experience login and other issues if only the steps in the WebLogic Workshop help system are followed.

Platform

All.

Workaround

After completing the steps in the Setting up My Yahoo! Enterprise Edition topic in the WebLogic Workshop help system, perform the following steps to complete the setup:

1. Make sure your server is running. With your portal application open in WebLogic Workshop, choose Tools-->WebLogic Server-->Start WebLogic Server.

2. Add entries to <PORTAL_APP>\<PROJECT>\WEB-INF\web.xml.

a. Open <PORTAL_APP>\<PROJECT>\WEB-INF\web.xml.

b. Open <BEA_HOME>\<WEBLOGIC_HOME>\samples\
portal\portalApp\sampleportal\WEB-INF\web.xml.

c. From the sampleportal web.xml file, copy the sections commented as <!-- Yahoo Integration * --> and paste them into your web.xml file in the appropriate locations.

You will be copying/pasting the following types of XML blocks:

<filter>, <filter-mapping>, <listener>, <servlet>, and <servlet-mapping>

Note: In following the previous step, for the initial block called <!-- Yahoo Integration: Filter to handle login -->, copy the entire block, which includes <filter>, <filter-mapping>, and <listener> elements, down to (but not including) the <!-- Portal Services: Listener to fire off session begin and end events for behavior tracking -->.

d. Save and close your web.xml file.

3. Create a portal in your portal Web project.

4. Add the Login to Portal portlet to your portal. See the WebLogic Workshop help system "Login to Portal Portlet" topic for instructions.

5. In the Data Palette window, drag one of the My Yahoo! Enterprise Edition portlets into the portal. For example, "Company News."

6. Open the portal. In the WebLogic Workshop menu, choose Portal-->Open Current Portal.

7. When the portal desktop appears, log in as yahooadmin/yahooadmin.

8. When prompted to link your portal account with a Yahoo! account, click OK.

9. On the Yahoo! Web page that appears, click Return to portal without linking. The Yahoo! Web page disappears.

10. In the browser containing the portal desktop, click the Refresh button. The My Yahoo! content appears.

CR124342

Yahoo! mail portlet takes a long time to deliver new Yahoo! mail messages.

Description

The Yahoo! mail portlet can take a long time to display new Yahoo! mail messages. This is in part because the Update link is broken and cannot be used (see, CR124387.)

Platform

All.

Workaround

Log out of WebLogic Portal and log back in.

CR124346

Yahoo! annual reports portlet displays no content in en_US locales.

Description

The Yahoo! annual reports portlet displays no content unless the user has set their locale to one of en_GB, fr_FR, or de_DE.

Platform

All.

Workaround

This is a Yahoo! issue. The only workaround is to use one of the locales that Yahoo! supports for this module.

CR124350

Yahoo! business publications portlet inconsistently displays custom content

Description

The Yahoo! business publications portlet inconsistently displays custom content when used in WebLogic Portal. A message from Yahoo! is displayed that says:

"You do not have permission to view this premium content from more than 800 business publications. Please click the X button to remove module. If you're interested in viewing this content, please contact your portal

administrator."

This occurs even if the content is enabled. If the user logs out and back in the content is sometimes displayed but may not be.

Platform

All.

Workaround

This is a Yahoo! issue and there is currently no workaround.

CR124387

Update link in Yahoo! mail portlet generates a 404 (page not found error)

Description

When using the Yahoo! mail portlet a hyperlink is generated to allow the user to manually update the list of messages in the users Yahoo! inbox. This hyperlink contains an invalid URL that generates a 404 (page not found) error when selected.

Platform

All.

Workaround

This is a Yahoo! issue and there is no workaround for this problem.

CR125461

Yahoo! subsytem can report "ERROR: 1001" when Yahoo! account is down.

Description

The Yahoo! integration in WebLogic Portal will display an "ERROR: 1001" when Yahoo! has disabled the deployment ID used by WebLogic Portal. This is a problem on the Yahoo! servers and is not related to an issue with WebLogic Portal.

Platform

All.

Workaround

The customer must contact Yahoo! support to determine when the failure will be corrected.

CR130020

Problems with character sets in the Compoze Portal.

Description

When using the Compoze My Mail portlet with Chinese character sets, the subject text in Chinese for some email messages are shown correctly, but others are not correct. Also, when viewing the content of email, all messages that are in Chinese are not shown correctly, that is, the text is garbled. The Win2000 machine where the problem is occurring has a language setting of simplified-chinese. This problem occurs when using pop3 mail protocol.

Platform

All.

Workaround

Patch available from Compoze.

CR106235

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

Description

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

Error Text Example:

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

Platform

All.

Workaround

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

SQL> revoke SELECT ANY TABLE from WEBLOGIC 2

CR107746

Integrity constraint errors may be encountered when adding content management nodes

Description

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

Platform

Any with an Oracle 8.1.7 database

Workaround

Check the version number of your Oracle database instance. If the version of your database is lower than 8.1.7.4 you will need to obtain the 8.1.7.4 patch set from Oracle and upgrade your database to this patch set. For Oracle databases in a Windows environment Oracle version 8.1.7.4.9 is recommended.

CR108193

ORA-22866 may occur when creating database tables

Description

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

Platform

Any with Oracle 8.1.7

Workaround

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

CR120519

Database Page Size Needs to be 8K

Description

During database schema creation, row size warnings have been generated similar to the following: Row size (2186 bytes) could exceed row size limit, which is 1962 bytes.

Platform

All.

Workaround

WebLogic Portal needs 8K page size for all platforms. Since some of the supported databases default to a smaller page size than 8k it is very important to verify the database into which WebLogic Portal will be installed has been created with 8k pages.

CR124126

Need to set configuration to send campaign emails with Sybase.

Description

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

Platform

Sybase.

Workaround

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

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

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

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

CR125832

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

Description

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

Platform

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

Workaround

Install the Oracle thin driver

CR134802

DB2 Configuration Parameters Minimum Settings

Description

To ensure the Portal application can successfully run on UDB 8.1 there are some minimum configuration parameters that need to be set. Without the minimum settings, heavy Portal activity may exceed database capacity.

Platform

Any UDB 8.1 database.

Workaround

Configure you DB2 database with the following parameters as guidelines for minimums:

• Dynamic Sections --> 17,500

• applheapsz --> 12,500

• pckcachesz --> 2500