Release Notes: Release 4.0 with Service Pack 3

 

Release Notes Version 4.0 Service Pack 3
Date: May 21, 2003

WebLogic Portal 4.0 is a product suite that enables you to build high-performance, scalable, personalized Web applications. You can create customized Web-based portals, marketing campaigns, and e-commerce sites, and deliver personalized content to users of your applications.

Throughout the product documentation, WebLogic Portal is used as a product suite name that refers to all portal, campaign, commerce, and personalization features. If you purchased the full WebLogic Portal license, you can use all the features of the product suite. If you purchased the WebLogic Personalization Server license, you can use only the personalization features. The common installation procedure installs all the product software.

In this document, the variable BEA_HOME is used to represent a parent directory, into which BEA products and related software are installed. The variable PORTAL_HOME is used to represent the installation directory for WebLogic Portal. The variable WEBLOGIC_HOME is used to represent the WebLogic Server installation directory. The variable EBCC_HOME is used to represent the E-Business Control Center directory.

This section contains the following information:

• Migration Information for Service Pack 3

• Migration Information for Service Pack 2

• WebLogic Server SP Versions

• What's New in This Release?

• Cloudscape

• Required Database Configuration Changes

• Disclaimer Regarding Use of Integrations

• Location of Supported Platform Information

• Limitations Fixed

• Known Limitations and Workarounds

• Miscellaneous Notes

• Product Documentation

• Contacting BEA Customer Support

 

---

Migration Information for Service Pack 3

There are no migration issues from Service Pack 2 to Service Pack 3. If you are upgrading from a version earlier than Service Pack 2, see the following migration sections.

If you developed applications using a prior version of the product, consult Appendix Service Pack 3 Text File Changes. You can also consult the Migration Guide for information on making your previous data and customization available to the release 4.0 installation.

 

---

Migration Information for Service Pack 2

Warning: Before you install any part of Service Pack 2, see the "ALERT: Migrating Your Enterprise and Web Applications from WebLogic Portal 4.0 GA and Service Pack 1 to Service Pack 2" section in the Installation Guide.

If you developed applications using a prior version of the product, consult Appendix Service Pack 2 Text File Changes. You can also consult the Migration Guide for information on making your previous data and customization available to the release 4.0 installation.

Saving Customizations

If you would like to save customizations you've made to the product, you should be aware that the installer will replace key files during installation of Service Pack 2.

To save your customizations:

1. Copy your customized files to a new location.

2. Follow the instructions for installing Service Pack 2.

3. Find and replace the new files with your customized files.

4. Edit the customized files text to comply with the Service Pack 2 updates. See Service Pack 2 Text File Changes to view the changes you must make to your customized files.

Service Pack 2 and Existing Applications

Warning: Before you install any part of Service Pack 2, see the "ALERT: Migrating Your Enterprise and Web Applications from WebLogic Portal 4.0 GA and Service Pack 1 to Service Pack 2" section in the Installation Guide.

WebLogic Portal 4.0 with Service Pack 2 also requires the stipulation of a JDBCHelperDelegate class for each application. Applications installed on WebLogic Portal 4.0 (prior to Service Pack 2), including Petflow and Avitek 1.1, require alteration to satisfy this requirement.

For detailed instructions on modifying existing applications, consult the Deployment Guide.

 

---

WebLogic Server SP Versions

The initial release of WebLogic Portal 4.0 was certified to run on WebLogic Server 6.1 with Service Pack 1. The subsequent release of WebLogic Portal 4.0, with Service Pack 1 was supported on WebLogic Server 6.1 with Service Pack 1 and Service Pack 2. WebLogic Portal 4.0, with Service Pack 2 is certified to run on WebLogic Server 6.1 with Service Pack 3. WebLogic Portal 4.0, with Service Pack 3 is certified to run on WebLogic Server 6.1, with Service Pack 4. WebLogic Portal 4.0, with Service Pack 3 and Rolling Patch 1 is certified to run on WebLogic Server 6.1, with Service Pack 5.

Service Pack 2 on Previously Installed SQLServer2000 (CR066040)

If you installed the files for SQL Server 2000 for WLPortal 4.0 prior to the release of Service Pack 2, the file permissions for <beahome>\wlportal4.0\db\sql_server\2000\readme.txt are set to "Read only", causing the Service Pack 2 upgrade installer for Service Pack 2 to fail silently. (Exceptions are thrown if the install is performed in Debug mode.)

To prevent this failure, remove the READ ONLY setting from the file properties for <beahome>\wlportal4.0\db\sql_server\2000\readme.txt. After this change is made, the installer will be successful. This problem is noted under BEA CR 66040.

Service Pack 1 Migration Information

Information for migrating from WebLogic Portal 4.0 GA to WebLogic Portal 4.0 with Service Pack 1 can be found in the Installation Guide, section " Installing Service Pack 1"
(http://download.oracle.com/docs/cd/E13218_01/wlp/docs40/install/instservicepack.htm#1062452).

 

---

What's New in This Release?

For up-to-date information about new features, please see the What's New page on the BEA E-docs site for WebLogic Portal 4.0. The URL for this release's What's New page is http://download.oracle.com/docs/cd/E13218_01/wlp/docs40/interm/whatsnew.htm.

 

---

Cloudscape

The Cloudscape 3.5.1 database that ships with the product is for demonstration purposes only. The demonstration version of Cloudscape allows only one database connection, hence is not suitable for production.

To improve the response time of the bundled example portals, and experience WebLogic Portal performance at production standards, switch from the default Cloudscape database to other RDBMS systems that WebLogic Portal 4.0 supports. For information on supported systems, see the Supported Platforms chapter in the Installation Guide.

Instructions for switching from Cloudscape to other supported database types are in the Deployment Guide.

 

---

Required Database Configuration Changes

Two database configuration actions are required for this release:

• Triggers and Behavior Tracking Fix (CR 64670)

• JDBC Helper Service Fix for CLOB Data (CRs 65221, 65247, 67935, 61496)

And one is required for Sybase users:

• Sybase-Specific Trigger Fix - Service Pack 2 Only (CR 64777)

Triggers and Behavior Tracking Fix (CR 64670)

The triggers that update the MODIFIED_DATE column to the current data and time are not being added correctly to the database via create_all. MODIFIED_DATE is only used by Behavior Tracking.

Add one of the following steps to the process of applying the upgrade:

• Before you run the create_all script during installation, add create_triggers to the end of the following line in create_all.sh or create_all.bat:

  set CREATE_ACTIONS=create_tables create_fkeys create_indexes create_views

• If you have already run the create_all script, or if you have applied Service Pack 2 using the Upgrade Installer, manually run the p13n_create_triggers.sql, portal_create_triggers.sql, and sample_portal_create_triggers.sql DDL from the appropriate database directory. This will add the triggers to an existing database.

JDBC Helper Service Fix for CLOB Data (CRs 65221, 65247, 67935, 61496)

IMPORTANT: After applying Service Pack 2 to a deployed WebLogic Portal 4.0 instance with existing data, the following configuration steps are required to avoid application failures and other errors. This procedure is meant to address problems with CLOB data.

This change also applies to fresh installs of WebLogic Portal 4.0 with Service Pack 2.

The JDBC Helper service must be set for each deployed application that uses JDBC. To set the JDBC Helper service, take the following steps:

1. Navigate to the WebLogic Server Administration Console: http://<hostname>:7501/console

2. In the left pane of the Console, click:

   Deployments > MyApplication > Service Configuration > JDBC Helper Service

3. Enter the Delegate Class Name:

   com.bea.p13n.util.jdbc.internal.OracleJDriverJdbcHelperDelegate

   or

   com.bea.p13n.util.jdbc.internal.GenericJdbcHelperDelegate

4. Click apply to save your changes.

Note: For details on configuring the JDBC Helper Service, consult the Deployment Guide, Add Extensions to the WebLogic Server Administration Console. This will tell you how to deploy the application that provides the extension to the WebLogic Server console for configuring the JDBC Helper Service. After you have deployed the console extension then you can configure the JDBC Helper Service using the instructions in the Deployment Guide in the section entitled " Configure the JDBC Helper Service".

No Delegate Class Name is required for Cloudscape databases.

Sybase-Specific Trigger Fix - Service Pack 2 Only (CR 64777)

Following application of Service Pack 2, two scripts need to be edited in order to correct problems with TU_ENTL_RULESET, TU_RESOURCE_GROUP_ADMIN and TU_P13N_LAYOUT Sybase triggers:

1. In p13n_create_triggers.sql, make the following modifications:

    create trigger TU_ENTL_RULESET

        on ENTITLEMENT_RULESET for UPDATE as

        begin

Replace This:

declare @id1 int, @id2 int

With This:

declare @id1 varchar, @id2 varchar

    select @id1 = APPLICATION_NAME, @id2 = RULESET_URI from inserted

   update ENTITLEMENT_RULESET 

   set ENTITLEMENT_RULESET.MODIFIED_DATE = getdate() 

   where

    ENTITLEMENT_RULESET.APPLICATION_NAME = @id1 and

    ENTITLEMENT_RULESET.RULESET_URI = @id2

   end

   go

1. In portal_create_triggers.sql, make the following modifications:

              create trigger TU_RESOURCE_GROUP_ADMIN

              on RESOURCE_GROUP_ADMIN for UPDATE as

              begin

Replace this

declare @id1 int

With This

declare @id1 varchar, @id2 varchar

        select @id1 = RESOURCE_GROUP_TAXONOMY,

        @id2 = DELEGATED_TO_USER_NAME

        from inserted

        update RESOURCE_GROUP_ADMIN

        set RESOURCE_GROUP_ADMIN.MODIFIED_DATE = getdate()

        where

    RESOURCE_GROUP_ADMIN.RESOURCE_GROUP_TAXONOMY = @id1 and

    RESOURCE_GROUP_ADMIN.DELEGATED_TO_USER_NAME = @id2

        end

        go

         create trigger TU_P13N_LAYOUT

         on PORTAL_P13N_LAYOUT for UPDATE as

         begin

Replace this

declare @id1 int

With This

declare @id1 int, @id2 int

       select @id1 = LAYOUT_ID,

       @id2 = PORTAL_P13N_ID from inserted

       update PORTAL_P13N_LAYOUT

     set PORTAL_P13N_LAYOUT.MODIFIED_DATE = getdate()

         where

       PORTAL_P13N_LAYOUT.LAYOUT_ID = @id1 and

       PORTAL_P13N_LAYOUT.PORTAL_P13N_ID = @id1

   end

   go

 

---

Disclaimer Regarding Use of Integrations

Use of WebLogic Portal in connection to and operation of third-party software, services, and applications is entirely at the user's risk. BEA Systems, Inc. disclaims all liability and responsibility for the operation, accuracy, and results of such software, services, and applications.

 

---

Location of Supported Platform Information

Information about the supported hardware and software platforms, and related certifications, is available in the "Supported Platforms" chapter of the Installation Guide. This information is updated as new platform certifications are completed. Please check the following URL for updates: http://download.oracle.com/docs/cd/E13218_01/wlp/docs40/install/platforms.htm. Refresh your browser cache to ensure you are viewing the latest content. The date of the platforms.htm file's last update is shown in the browser window's title bar.

 

---

Limitations Fixed

This section lists limitations that were fixed in the 4.0 release and in subsequent service packs.

Note: If you are experiencing a problem that you cannot find in the Known Limitations and Workarounds section, look in the Workaround for 84487 section.

Limitations Fixed in Service Pack 3

The following limitations that existed in the initial release of WebLogic Portal 4.0 were fixed in Service Pack 3:

• CR 35483 and CR 35481: Shopping Cart contents are lost in cluster environment when the user logs in for the first time.

• CR 64192: .scc files created by Visual Source Safe were not ignored, especially by validation.

• CR 65042, CR 65223, and CR 63919: No "floatable" attribute is available for a portlet in the Portal Administration Tools.

• CR 71557: There was a performance problem with RDBMSDelegate getUser() and getGroupMembers().

• CR 72316: Servlet filters throw a "java.lang.IllegalStateException: Unable to extract ServletContext from Request."

• CR 75212: The webflow:validatedForm tag needs extra parameters.

• CR 76471: Concurrent portal cache access causes java.lang.NullPointerException.

• CR 73940: Root cause of ServletException java.lang.NullPointerException.

• CR 77358: A NullPointerException is thrown in the browser when a user edits entitlement segments in new Group Portal in Portal Tools.

Limitations Fixed in Service Pack 2

The following limitations that existed in the initial release of WebLogic Portal 4.0 were fixed in Service Pack 2:

• CR 62217: An IllegalArgumentException was thrown while using new layouts in portalTools.

• CR 64897: Hot deploy of input processors did not work.

• CR 65781: Multibyte characters filename created malformed data in the database.

• CR 66025: A webapp[null] exception message would display periodically and require redeployment.

• CR 66776 and 65370: A user in more than one group caused java.lang.ClassCastException during login to stockportal.

Limitations Fixed in Service Pack 1

The following limitations that existed in the initial release of WebLogic Portal 4.0 were fixed in Service Pack 1:

• CR 56318: The E-Business Control Center did not change edit restrictions, icons, and status messages when the status of a file changed from writable to read-only (and vice versa).

• CR59442: In the E-Business Control Center, the character limits for several description fields did not function as expected.

• CR59781: The E-Business Control Center did not allow the Connection Settings credential to be edited.

• CR64429: WebLogic Server MS SQL Server Classes were incorrectly set. The set-environment script was modified to correct the problem.

• CR64817: The set-environment.sh script for WebLogic Portal 4.0 on Linux did not include i686 subdirectory for the BEA_OD_DIRNAME variable.

Limitations Fixed in the Initial Release

The following limitations that existed in the BEA Campaign Manager for WebLogic 1.1, WebLogic Commerce Server 3.5, and WebLogic Personalization Server 3.5 release were fixed in the initial release of WebLogic Portal 4.0:

• CR 35571: Hot deploy did not work for the EJBs because the *Impl.class files were also included in the weblogic.class.path classpath.

• CRs 44675 and 47334: E-mail with double-byte characters were jumbled, and inserted content type of text/plain caused HTML e-mail to be rendered as plain text.

• CR 45782: Previewing a placeholder with no descriptor information in the E-Business Control Center's Ad Search window resulted in an error message. The Preview button is now disabled when there are no descriptors specified.

• CR 47033: PipelineSession request-scoped attributes did not work with HTML frames and they did not work if a client has two browsers accessing the same WLCS application. This problem has been fixed in the new Webflow implementation. The methods PipelineSession.getRequestScopedAttribute and PipelineSesison.setRequestScopedAttribute now take a requestContext that keeps separate the multiple request-scoped attributes.

• CRs 47061 and 49144: *.html files could not be portlets in the sample portal.

 

---

Known Limitations and Workarounds

Table 1 describes limitations in the WebLogic Portal 4.0 release and applies to the portal, campaign, commerce, and personalization features. Where possible, suggested workarounds are provided.

Please contact BEA Customer Support for assistance in tracking any unresolved problems. For contact information, see Contacting BEA Customer Support.

Table 1 Known Limitations and Workarounds

CR 33972	es:transposeArray tag throws "ClassCastException".
Problem	es:transposeArray tag throws ClassCastException and does not output expected content from body of tag.
Platform	All.
Workaround	Do all of the following: Use only the "no body" form of the tag. For example: <es:transposeArray id="colrowPortlets" array="<%=allMyPortlets%>" type="Object"/> Use only "Object" as the value for the 'type' attribute as shown in the previous list item. Use class casting where appropriate. For example: if ( ((Portlet)colrowPortlets[minColumn][minRow]).isMinimizeable() ) {}
CR 34401	Successive attempts at running the DBLoader on Cloudscape fail.
Problem	Successive attempts at running the DBLoader on Solaris with the Cloudscape database fail with the error message: WARNING: Cloudscape (instance XXX) is attempting to boot the database /db/data/Commerce even though Cloudscape (instance XXX) may still be active. Only one instance of Cloudscape should boot at database at a time. Severe and non-recoverable corruption can result and may have already occurred.
Platform	Solaris
Workaround	Delete the db.lck file in the WL_COMMERCE_HOME/db/data directory and run the DBLoader again.
CR 35555	If the document management XML schema files are changed, the E-Business Control Center does not display the changes.
Problem	In the reference document repository, which obtains schema information from XML files on the file system, if you change the XML schema files, the E-Business Control Center does not display the changes. The XML schema files might change when you run the BulkLoader, loaddocs, or loadads against content that has new metadata properties.
Platform	All.
Workaround	Restart the server. Then use the WebLogic Server Console (http://localhost:7501/console) to restart the connection pool.
CR 44788	Need to modify proxy server's plug-in settings to account for unique cookie names per Webapp.
Problem	The sample applications for WebLogic Portal are shipped with unique cookie names configured for each Web application in the weblogic.xml descriptor, because these sample applications do not use or require the single-user sign-on feature. In this configuration, if you are using a proxy server, you will need to modify its plug-in's settings because they are normally only aware of a single cookie.
Platform	All.
Workaround	Configure the plug-ins to do proxy by path. For example: ppath=*/webapp1/* => set CookieName="foo" ppath=*/webapp2/* => set CookieName="bar" Currently, you can do this in the NSAPI plug-in easily by defining multiple objects. In ISAPI you can achieve this by defining virtual directories and pointing them to different iisproxy.ini files having different CookieNames. Currently you cannot do this in Apache because it does not allow you to overwrite CookieNames.
CR 44871	Must set CookieDomain in weblogic.xml, to allow commerce templates to work correctly in Netscape with cookies enabled.
Problem	The sample commerce templates do not work with cookies enabled for Netscape 4.5 and higher. This problem does not occur with Microsoft Internet Explorer.
Platform	All, when using Netscape 4.5 and higher.
Workaround	A session parameter was added in the wlcs Web application's weblogic.xml. This weblogic.xml file is in the PORTAL_HOME\applications\wlcsApp\wlcs\WEB-INF directory. <session-param> <param-name>CookieDomain</param-name> <param-value>mycompany.com</param-value> </session-param> Before using the wlcs Web application in Netscape, uncomment these tags and change the CookieDomain parameter value in from mycompany.com to the company domain name.
CR 47792	Creating users with missing required property values in the admin tool causes template errors at login.
Problem	When creating a user with the WebLogic Portal Administration Tools, if you do not fill in values for all required properties, you receive errors in the template when you log in with that user.
Platform	All.
Workaround	Create users by logging into the templates using registration rather than using the administration tools. If you prefer to use the administration tools, enter values for all required user properties (fields marked with an asterisk *).
CR 60341	ORA-01461 error with Oracle jDriver and UTF8 character set.
Problem	The following exception may occur while loading data using the WLCS data loading scripts: java.sql.SQLException: ORA-01461: can bind a LONG value only for insert into a LONG column .
Platform	All.
Workaround	Make the following configuration changes: Set weblogic.oci.codeset_width=0 AND Set either the NLS_LANG environment variable (e.g. set NLS_LANG=AMERICAN_AMERICA.UTF8), or the weblogic.codeset connection pool property. Note: Setting the weblogic.codeset supersedes the NLS_LANG environment variable.
CR 52709	Web.xml file P13N_STATIC_ROOT parameter server value is hard coded.
Problem	The (JSP-based) Administration Tools and PetFlow web applications do not resolve images because the server name is hard coded into the web.xml file.
Platform	All.
Workaround	Edit the web.xml file for the Administration Tools and Petflow web applications. Change localhost to the actual machine name. For example, change localhost in the following: <!-- The P13N URL root to be used by createStaticResourceURL() to build urls to static resources that exist on a proxy server. --> <context-param> <param-name>P13N_STATIC_ROOT</param-name> <param-value>http://localhost:7501/petflow</param-value> </context-param>
CR056612	Possible security risk: Users can access wlcsAppCatalogTool using their browser.
Problem	Users can access the wlcsAppCatalog Tool from their browser, creating a security risk.
Platform	All.
Workaround	Contact BEA support for fix information if you are making this tool available on the Internet. Be sure to provide them with this CR number, so they may help you more efficiently.
CR 58376 and CR 60145	Cannot deploy multiple instances of an application in a single domain.
Problem	The welcome-file list in web.xml does not work if the context root for a Web application (which is declared in application.xml) is different from the name of the Web application's root directory. To deploy multiple instances of an application in a single domain you make a copy of the application directory and remap the context root of the applications. In addition, many sample applications hard code URLs to resources so that renaming the context root of an application invalidates the URLs.
Platform	All.
Workaround	Do not use the welcome-file list for your own applications. Instead, if the context root for a Web application is different from the name of the root directory, URLs for the Web application's default page must specify the pathname to a JSP. For example, instead of http://localhost:7501/p13nAppTools, specify http://localhost:7501/p13nAppTools/index.jsp In addition, do not deploy multiple instances of a sample application in a single domain.
CR 58616	Behavior Tracking data does include the application name from which an event is generated.
Problem	WebLogic Portal does not store information about a Behavior Tracking event that identifies the application from which it was generated. If you have deployed multiple applications in a single domain, you cannot identify which application generated the event.
Platform	All.
Workaround	Archive your existing event database, drop the existing tables, and re-create with the new structures.
CR 58726	WebLogic Portal does not work with WebLogic Server LDAP Realm v2.
Problem	The WebLogic Server v2 LDAP realm does not support certain operations required by WebLogic Portal.
Platform	All.
Workaround	Please contact WebLogic Server Support for the workaround. Be sure to provide them with the CR number for this note (58726).
CR 58782	T3 client provides a connection to the database without requiring a login.
Problem	By default, the WebLogic Portal sample applications enable the guest user. This allows a T3 client to get a connection to the database without having to log in. If you attempt to disable the guest user by setting GuestDisabled=true in a domain's config.xml file, WebLogic Portal throws an exception.
Platform	All.
Workaround	There are two workarounds for this issue: Create a connection filter. (See Installing a Connection Filter in the Managing Security document on the BEA e-docs website. Use standard network security measures to protect your server. For example, you can create and maintain a firewall.
CR 58836	There is a 32K data size limitation on discounts2.xml and cannot handle Japanese text.
Problem	When the size of discounts2.xml is larger than 32K and has Japanese text, loading discounts2.xml fails by running loadsampledata.bat.
Platform	All.
Workaround	Please contact BEA Support for a product patch to fix this problem. There is a patch that addresses the problem of failures while reading or writing large CLOBs when getting or setting rulesets and discounts on multibyte character-set databases. Be sure to provide BEA Support with the CR number associated with this problem.
CRs 59581 and 59879	Exception handling not working in a WebLogic Server cluster.
Problem	In a WebLogic Server cluster environment, WebLogic Portal is unable to log messages with embedded exceptions to the administration server's wl-domain.log file. Messages without embedded exceptions can be logged successfully. The administration server will throw an UnmarshalException because the exception classes are not in its system classpath and the managed node will throw a ClassNotFound exception.
Platform	All.
Workaround	Your custom exceptions should extend com.bea.p13n.exceptions.ApplicationException or com.bea.p13n.exceptions.SystemException.
CR 59959	The field length of the amount off and fixed price should be lengthened to accommodate 17 characters.
Problem	Currently, the fields displays 11 characters until the user has to use the arrow keys (or home/end keys) to scroll across the field.
Platform	All.
Workaround	Since the maximum field length of the amount off and fixed price fields allow 17 characters, the field length in the Specify Discount Value window should be lengthened to accommodate that many characters.
CR 60276	Synchronizing deleted or modified discounts can lead to race conditions.
Problem	When data-syncing discounts (via the EBCC) which have been previously synced, it appears that the discounts are redeployed to the discount DB table because they end up with new discount IDs.
Platform	All.
Workaround	If you delete or modify discounts, do not synchronize to an application that has instantiated shopping cart objects.
CR 60291	The E-Business Control Center accepts badly formed email addresses.
Problem	In the E-Business Control Center, on the "Enter E-Mail Information" dialog box, if you enter a badly formed email address in the text field "Sender's e-mail address," the E-Business Control Center does not warn you of the badly formed address. When the server tries to send the email, it throws an exception.
Platform	All.
Workaround	Make sure that you enter well-formed email address in the E-Business Control Center.
CR 60301 and 67282	Ad Service: Display Flush Size not applied to server until server is restarted
Problem	The AD_COUNT is not incremented by 1. There is no change until nine more campaign hits are fired.
Platform	All.
Workaround	Restart the server.
CR 60432	You cannot configure the size of the RDBMSRealm delegate pool through the WebLogic Server Administration Console.
Problem	The RDBMSRealm does not read the size of the delegate pool from an MBean.
Platform	All.
Workaround	Create a properties file named realm.properties that contains the following string delegatePool.size=number where number specifies the number of threads in the delegate pool. Save realm.properties in com.bea.p13n.security.realm.
CR 60459	In the E-Business Control Center, the Discount Editor does not support long lists of SKUs.
Problem	In the E-Business Control Center, lists of SKU and product category IDs in the Discount Triggers and Targets window can cause layout problems in the Discount Editor. If the number of SKUs or Product Category IDs is long, the Discount Wizard button will disappear and other fields will be compressed.
Platform	All.
Workaround	If you need to access the Discount Wizard button under these circumstances, edit the Target or trigger that is causing the problem and either change it to a different type or remove the SKUs or IDs. After you remove the problem Trigger or Target, the display will refresh and lay out correctly.
CR 60774	Attempting to access the Personalization Server Example WebApp returns 404 error when server started for p13nDomain.
Problem	If you run PORTAL_HOME\config\p13nDomain\startP13N.bat from the command line and then try the use the Personalization Server Examples shortcut created in the Start Menu item for WebLogic Portal 4.0, a 404 error is returned by the browser. The shortcut attempts to open http://localhost:7501/p13n. The same error occurs on Solaris if you run startP13N.sh and navigate to http://localhost:7501/p13n.
Platform	All.
Workaround	The p13n Web application URI conflicts with the default Web application for the server. This problem can be fixed by creating a new default Web application for the server, as you would for the Portal domain server.
CR 62205	Pipeline Session CommerceInputProcessor.getPipelineSession() No Longer Provided.
Problem	In Release 3.5 of Campaign Manager for WebLogic, WebLogic Commerce Server, and WebLogic Personalization Server, there is no way to detect when the HttpSession timed out while trying to get the PipelineSession Input Processor.
Platform	All.
Workaround	Add the following scriptlet to your JSPs: HttpSession session = request.getSession(false); if (session.isNew()) throw new InvalidSessionStateException(..);
CR 63019	The E-Business Control Center on Solaris does not display the portlet sample files.
Problem	The E-Business Control Center installer installs the portlet sample files in a directory named Portlet; however, it expects to find the sample files in a directory named portlet.
Platform	Solaris
Workaround	After you install the E-Business Control Center, Rename: EBCC_HOME/applications/portal/application-sync/Portlets To: EBCC_HOME/applications/portal/application-sync/portlets
CR063049	CLOB database inserts/update do not work with Oracle thin driver and Delegates
Problem	create_all (the dbloader - insert bootstrap sample data step) produces errors when using the Oracle Thin driver. This failure occurs when attempting to insert data into the ENTITLEMENT_RULESET table, which is the only table that create_all loads with a CLOB column. These errors are the result of a CLOB write being done via the thin driver without a delegate.
Platform	All
Workaround	Use jDriver for the dbloader.
CR 63334	There are difficulties using DB2 7.1, JIT when creating a customer profile.
Problem	If you use a DB2 7.1 database as the WebLogic Portal data repository, and if you use a JIT compiler, the JVM dumps core when you create a customer profile.
Platform	JDK 1.3.0 Classic VM (build 1.3.0, J2RE 1.3.0 IBM build ca130-20010615a (JIT enabled: jitc)).
Workaround	If you want to use the JIT, you must define the following system environment variable and values: JITC_COMPILEOPT=NALL{com/bea/p13n/property/internal/EntityPropertyManagerImpl}{getProperties}:$JITC_COMPILEOPT
CR 64221	CTRL-M is added to multi-line properties in non-Windows Operating System.
Problem	When making a change to a service whose console extension has one or more multi-line properties (i.e. Behavior Tracking Service's Persisted Event Types) on a non-Windows Operating System, those properties are updated in the application-config.xml file appended with CTRL-M characters.
Platform	Non-Windows.
Workaround	Edit the application-config.xml file in $PORTAL_HOME/applications/$APPNAME/META-INF/, removing the ^M characters. For example, change this: <CampaignService EmailBrowseBaseDir="campaigns/emails" EmailURIExtensions="jsp^M,html^M,htm^M,txt^M" GoalCheckTime="0" Name="portal" > to this: <CampaignService EmailBrowseBaseDir="campaigns/emails" EmailURIExtensions="jsp,html,htm,txt" GoalCheckTime="0" Name="portal" > Note: Services with multi-line properties, such as the following, are susceptible to this problem: Behavior Tracking Service Document Connection Pool Service Campaign Service Scenario Service
CR 64821	Changing a portal's minimizable/maximizable attribute can cause an exception.
Problem	If a visitor authenticates into one browser session and changes the minimizable attribute of a portlet from true to false, and an administrative user logs into a concurrent browser session and changes the same attribute between when the visitor's browser displays and refreshes the same portlet, an error will result. This is becausethe refresh causes a request for an attribute which is no longer available. The problems appears only if the minimize/maximize attribute is changed within a single session of a logged in user.
Platform	All.
Workaround	This error ocurs when a user essentially bookmarks an action on the portlet (unminimize) which subsequently becomes unavailable.
CR 64895	UNIX install files have hard-coded path for commerce server home in db.install files.
Problem	For UNIX, the following scripts have hardcoded paths for set-environment.sh that should be variable-based: loadbootstrap.sh loadsample.sh deletesample.sh As a result, these scripts will fail to run set-environment.sh.
Platform	UNIX
Workaround	This workaround applies to WebLogic Portal Service Pack 2. In each of these files, the following change is required: Replace BEA_HOME/dev/nbuild/main/bin/unix/set-environment.sh with BEA_WEBLOGIC_COMMERCE_SERVER_HOME_FORWARD_SLASH@/bin/unix/ set-environment.sh
CR 65026	The CustomerService portlet will throw an exception against an Oracle database.
Problem	The CustomerService portlet will throw an exception against an Oracle database because the path to the set-environment.bat file is hardcoded
Platform	Oracle.
Workaround	Create a text file called .ant.properties in your bea\<portal_home> directory that contains the following line: p13n.dir=C:\bea\wlportal4.0 Change the path, if you installed it in a different directory.
CR 65054	Using Petflow sample, runtime error occurs when completing an order.
Problem	This problem involves a Sun java class.
Platform	DB2 and Solaris
Workaround	This workaround applies to WebLogic Portal Service Pack 2. Use an Oracle, Cloudscape, or SQL Server database.
CRs 65440 and 67935	Console error when StartPortal fails after synchronizing data from EBCC
Problem	When the E-Business Control Center is used to edit application data files stored in the \<BEA_HOME>\ebcc4.0\applications\<your_application>\application-sync directory, syncing can result in malformed xml in the CLOB. This malformed xml also causes errors in the WLS Console, and usually happens when elements are removed from the xml, making the file smaller.
Platform	All platforms with Oracle database.
Workaround	Two workarounds are possible: Request and install the following patch from BEA support: patch_CR067935.zip OR Do a full synchronization by taking the following steps: In the E-Business Control Center, choose Tools > Synchronization Settings In the Synchronization Settings window, select "Update all files in the application." Click OK, then click Synchronize.
CR 65566	Problems after deleting customers when using discounts
Problem	Problems can occur if you delete customers and use the discount service. If a deleted customer's order contains a reference to a discount you may see the following errors: Users cannot add to the shopping cart, nor check out. The browser error message is: "ebusiness-order:create.priceservice.remote.exception". When discounts are datasync'd during startup, a "violation of foreign key constraint" error appears.
Platform	All.
Workaround	If you delete a customer and you use the BEA discount system, you must purge or archive the order history for that customer. If a deleted customer's order contains a reference to a discount, you will receive exceptions during datasync.
CR 65858 and 79688	Deleting a portlet in the E-Business Control Center does not remove it from the portal configuration.
Problem	Problem - Deleting a portlet from your file system outside the E-Business Control center or the explorer pane within the E-Business Control Center, does not update any open portal editor windows in the E-Business Control Center that contain the deleted portlet.
Platform	All.
Workaround	Close the portal editor window and reopen it for that portal to view the updated portal definition. It will no longer show the deleted portlet as part of the portal.
CR066963	No way to configure Helper Delegate when migrating an existing application
Problem	The "Service Configuration" extension is not set up automatically. Therefore, through the console you cannot set up the JDBC Helper Delegate (which is required for anything other than Cloudscape) by going into the Service Configuration folder. The customer, by default, does not have the "Service Configuration" folder in the Console when migrating an existing enterprise application.
Platform	All
Workaround	This workaround configures the JDBC Helper Delegate for the jDriver for Oracle, but it will not create the Service Configuration folder in the console. In WLP_HOME/config/config.xml, this entry needs to be made within the <application> tag. <ApplicationConfiguration Name="<YourAppName>" Targets="<yourappServername>" URI="META-INF/application-config.xml"/> Create an "application-config.xml" file under "WLP_HOME/applications/<YourAppName>/META-INF/" In the application-config.xml file, input the following: <ApplicationConfiguration> <JdbcHelper JdbcHelperDelegate="com.bea.p13n.util.jdbc.internal.OracleJDriverJdbcHelperDelegate" MaxRetries="-1" MaxWaitTime="-1" Name="JdbcHelper" /> <ApplicationConfiguration/> Note: This will set up the Helper Delegate. It will not create the "Service Configuration" folder in the WebLogic Server Console.
CR 67640	There is a need for a way to set the httpsInd attribute default value to something other than CALCULATE.
Problem	A way was needed to set the httpsInd attribute default value to something other than CALCULATE, unless overridden by the web.xml parameter. The web.xml is not updated to include the commented out parameter necessary to acheive this.
Platform	All.
Workaround	Open the web.xml file in a text editor. Add the following parameter template: <!-- The default method for WebflowJSPHelper and the createWebflowURL tags to compute whether HTTP or HTTPS should be used. See the javadoc for WebflowJSPHelper for more information. Possible values: HTTP, HTTPS, or CALCULATE If this parameter is not specified, CALCULATE is used. --> <context-param> <param-name>HTTPSIND_DEFAULT_VALUE</param-name> <param-value>CALCULATE</param-value> </context-param> Use this template to make the necessary changes.
CR 67696	Evaluation License Issue Only: EBBC explorer does not work
Problem	When your evaluation license expires, the EBCC will start without error but also without functionality and without providing error messages in the user interface. You can check error messages in the tools.log file in your EBCC installation directory. These messages indicate this license issue has occurred: [WARNING] 000010: Not installing Catalog functionality. Did not find valid Personalization Server license. Core Server: license has expired on <date>! [ERROR] Core Server: license has expired on <date>!
Platform	All
Workaround	Download a new evaluation copy of the software at http://support.bea.com.
CRs 69636 and 64149	Hot deploy of input processors breaks the webapp until it is redeployed.
Problem	Hot deploy of input processors does not work for 4.0 and 4.0 SP1. Changes to input processors in a webapp's WEB-INF/classes directory seem to either be ignored or breaks the webapp until it is redeployed via the WebLogic Server console. With WebLogic Server, a change to a class under a Webapp's WEB-INF/classes directory is immediately picked up, without the need to redeploy the WebApp. Before the fix, if a change is made to an input processor (in the WEB-INF/classes directory) the WebApp does not seem to work until the webapp is redeployed. Either the new class is ignored or a ClassCastException is thrown.
Platform	All.
Workaround	Follow these instructions for hot-deploying IPs: Step 1: Increase the File System Check Time From Console, navigate to Deployments ? Applications ? <appname> ? <webappname>. Select the Configuration tab. Select the Files tab. Change the reload period default from 300 seconds to 0 seconds. Step 2: Disable the Inputprocessor Cache Navigate to your application's meta-inf directory (applications\wlcsApp\META-INF) Open the application-config.xml file for edit. Add a new child element under the CacheManager element. For example: <Cache MaxEntries="500" Enabled="false" Name="wlcs-interface-cache" TimeToLive="600000" /> The name of the cache must be the name of the webapp, plus "-interface-cache". The above example is for the "wlcs" webapp. Administer the cache. From Console navigate to Deployments > Applications > <appname> > Service Configuration > Caches > <cache name>. Select the cache name. Deselect the Enabled checkbox.This cache should be disabled during development so that hot deploy will work. Note: The alternative to disabling the cache is to flush the cache with the console each time a new version of an IP is loaded.
CR064640	Browser Back button problem occurs with webflow form tag.
Problem	An error appears when you use the browser back and forward buttons in the portal and browse to a previously seen page that was generated by a form submission that had a method = "POST".
Platform	All.
Workaround	Change the HTTP 1.1 Cache-Control header in portal.jsp to private (meaning that the page is cacheable by the browser, but not by proxy servers).
CR072174 and 74480	Need to add Thin settings to set-environment and databaseload.properties
Problem	create_all and loadSampleData cannot be run with Thin Driver.
Platform	All
Workaround	Switch to jDriver from Thin Driver, run the bat files, and switch back to Thin Driver. To fix this problem: Switch to the jDriver. Navigate to <WebLogicPortal_HOME>/db Depending on your configuration, run one of the following files: t create_all.bat t create_all.sh Navigate to <WebLogicPortal_HOME>/bin/<OS> Depending on your configuration, run one of the following files: t loadSampleData.bat t loadSampleData.sh Switch back to Thin Driver.
CR072965	Sybase12.0/NT: character set conversion using text data.
Problem	For Sybase, there are several TEXT type fields defined in the DDL. If the character set of the client and the server are different and the data size changes in converting from the server to the client character set, there will be a problem while retrieving the data.
Platform	NT
Workaround	This workaround applies to WebLogic Portal Service Pack 2. Use either of the following: Turn off character set conversion, and perform the conversion of the text data on the client side. You can either turn character set conversion off completely or only for SELECTs on text fields. Use a client with the same character set as the server to access the data. With a Unicode-enabled server, that means using a client that is using Unicode as its character set.
CR 73932	Sybase 12 jConnect5.2/Segment Integration problem.
Problem	Integration of segments fail without a Sybase patch
Platform	Sybase 12/jConnect 5.2
Workaround	This workaround applies to WebLogic Portal Service Pack 2. Apply the patch for jConnect 5.2 (EBF_10105.tgz ) as listed in the Supported Platforms section of the WebLogic Portal 4.0 with Service Pack 2 Installation Guide.
CR 75335	File path reference in resourceURL.inc is incorrect, causes skins to not display
Problem	The jsFile setting in the resourceURL.inc file is incorrect and prevents skins from displaying.
Platform	All.
Workaround	Open the resourceURL.inc file at the following location: wlportal4.0\applications\portal\stockportal\framework. Make the following changes to the jsFile setting: Change: jsFile = "/framework/js/"; To: jsFile = "/framework/tools/js/"
CR 75747, 75135, and 75266	AIX 4.3.3-DB2 7.2 Native/Stockportal has problems with user creation.
Problem	The IBM JAAS files that come with JDK 1.3.1 cause various exceptions.
Platform	IBM PowerPC
Workaround	This workaround applies to WebLogic Portal Service Pack 2. Remove the IBM JAAS files that come with JDK 1.3.1. To remove them: Navigate to the following directory: BEA_HOME/jdk131/jre/lib/ext Remove the jaas.jar and jaas_lm.jar files. Warning: Do not rename the files. You must delete them or move them to a different location.
CR 76191	Campaign validation claims complete campaigns are incomplete in Service Pack 2
Problem	Some campaigns that synchronize in Service Pack 1 might show incomplete exceptions when synced in Service Pack 2.
Platform	All.
Workaround	Add the "is-complete" tag to the rules and scenario sections and sync again.
CR 76577	Ad Service: Display Flush Size not applied to server
Problem	The display flush size is not applied to the server.
Platform	All.
Workaround	Restart the server to apply a change in flush size.
CR 76667	Linux 7.2-Sybase 1192/java.lang.OutOfMemory Exception problem
Problem	The file descriptors, sockets, or thread level memory allocation create server exceptions based on Virtual Memory (VM) allocation.
Platform	Linux
Workaround	This workaround applies to WebLogic Portal Service Pack 2. Use the client VM. To fix this problem: Navigate to BEA_HOME/wlportal4.0/bin/unix Open the set-environment.sh file. Find te Linux section of the file. In the Linux section only, Replace: JAVA_VM_OPTIONS=" -server -Xms128m -Xmx128m" With: JAVA_VM_OPTIONS="-ms160m -mx300m -XX:MaxNewSize=100m -XX:NewSize=100m -XX:MaxPermSize=128m"
CR 76825	Unable to target ApplicationConfiguration from the console
Problem	There is no way to target ApplicationConfiguration data from within the console.
Platform	All.
Workaround	Stop the server Open config.xml under the portal Domain directory (i.e. portalDomain). Find the myApplication element. Add the following information: <ApplicationConfiguration Name="<myApplication>" Targets="<myTarget>" URI="META-INF/application-config.xml"/> Restart the server.
CR 76978	The Master Data Repository construction fails when starting the server.
Problem	Your campaign tour examples can cause a Master Data Repository error when you try to start the server.
Platform	All.
Workaround	Select the Update all Files option to automatically clear the tables prior to synchronization. Note: If you clear all the data, you may effect applications other than the one you are attempting to sync.
CR 77374	The <cm:printDoc> tag incorrectly streams some UTF8 files.
Problem	The <cm:printDoc> tag ignores the encoding of the input file being printed when converting the byte array, so UTF8 files are not properly streamed.
Platform	All.
Workaround	To correctly display UTF8 content use the following code: Document document = (Document)content; byte[] b = document.getContent(); String s = new String(b, "UTF-8");
CR79545	ClassCastExceptions using entitlements with LDAP
Problem	Prior to Service Pack 3, a problem existed with multi-valued properties from LDAP that are obtained with the UUP provided in ldapprofile.jar (the LdapPropertyManager EJB). An attribute that is defined as multi-valued in the LDAP schema was stored in memory as a single value property by the LdapPropertyManager. This could cause problems in the rules engine when this situation was encountered: A multi-valued LDAP property had a single value. A rule was created in WebLogic Portal that used the property as a multi-valued property. The rules engine expects the property to be a java.util.Collection because it is multi-valued, but it was not, because the LdapPropertyManager saw it as single value and stored it that way.
Platform	All.
Workaround	A change included in Service Pack 3 allows a developer to configure the ejb-jar.xml deployment descriptor for the LdapPropertyManager EJB to specify that the LDAP schema be used to determine if a property is single value or multi-value. See comments in the deployment descriptor for details. It is not recommended that this change be enabled via the deployment descriptor unless you are going to write rules that use multi-valued LDAP attributes that have a single value. Using config/detectSingleValueFromSchema = true adds the overhead of checking the LDAP schema for each attribute instead of the default behavior (config/detectSingleValueFromSchema = false), which only stores an attribute as multi-valued (in a Collection) if it has more than one value.
CR 79799	Always use latest Oracle thin driver.
Problem	Oracle recommends that customers always use the latest version of the Oracle thin driver, regardless of the database version
Platform	All.
Workaround	WebLogic Server ships thin drivers for multiple versions of Oracle. According to Oracle Corporation, customers should be using the latest thin driver version regardless of the customer's database version. Thus it is recommended by Oracle that the newest 9i thin driver be used with Oracle 8.1.7 or Oracle 9i.
CR 84384	The Data_Sync_Item table is inaccessible and an ORA-03120 error occurs.
Problem	When using Oracle 8.1.7, the Data_Sync_Item table becomes inaccessible. When retrieving LOB fields in external tools such as SQL*Plus, you may receive the Oracle error: "ORA-03120: two-task conversion routine: integer overflow".
Platform	Oracle 8.1.7
Workaround	This problem is caused by Oracle bug 1130746, which has been fixed in Oracle 8.1.7.1. Contact Oracle Corporation to obtain the patch for this problem.
CR 84487	Maximize button is unavailable to anonymous users in stockportal.
Problem	When no user is logged in to stockportal, the maximize button is not available on any portlets.
Platform	All.
Workaround	For a detailed workaround, see Workaround for 84487.
CR 88553	Enhancement request for multi-valued CM properties.
Problem	The content management framework does not support an IN comparator for content queries. You cannot write a content selector like this: CONTENT.author is in MYPROPERTYSET.myMultiValuedProperty.
Platform	All.
Workaround	If you write the query using 'equals,' then the framework compares the content property to only the first value in the collection constituting the multivalue property it is being compared to. If you would rather have the 'equals' query compare the content property to all values in the Collection, then request the patch for CR088553 from support and you can simulate an 'IN' query. This patch constructs a series of 'or' statements to simulate an 'IN' query.
CR 89552 and CR 88431	The "everyone" entitlement is not always deleted.
Problem	The "everyone" entitlement is not deleted when you delete a portlet or portal page, nor is it reset to the default values. Therefore, if you delete and re-create a portlet or portal page, the "everyone" entitlement will have the same values set on it that were set on the previous incarnation of the portlet or portal page.
Platform	All.
Workaround	Manually delete the "everyone" entitlement for the portlet or portal page.
CR 90377	RefDocumentProvider: make setTransactionIsolation optional and only available for direct driver connections
Problem	In some cases the RefDocumentProvider component of the reference implementation of the content management system was not handling transactions correctly (ORA-01453 SQLExceptions thrown to the console are a possible symptom of this if you are using Oracle). To correct this issue, it is no longer possible to specify a transaction isolation level if you are connecting to a DataSource. The connection property jdbc.isolationLevel for the DocumentConnectionPool will only be used in the case where you have provided a JDBC driver (jdbc.driver and jdbc.url). If you have specified a DataSource using jdbc.dataSource, any jdbc.isolationLevel property that is also specified will be ignored.
Platform	All.
Workaround	If you need to specify a transaction isolation level for some reason you will have to use a JDBC driver and not a DataSource.
CR 91980	Portal Personalization Cache in a cluster
Problem	The Portal personalization cache is not correctly cluster-aware and does not alert other nodes that a Portal personalization has been altered. When a Portal personalization is modified on two different nodes, the changes are not properly propagated to other nodes that have already loaded that Portal personalization into their caches. This will most likely be seen when the WebLogic Portal Administration Tools are deployed to multiple nodes and accessed simultaneously. Changes made on one node may not be seen on another.
Platform	All.
Workaround	Please contact BEA Support to receive a patch for this problem. Provide Support with the CR number (CR091980) associated with this problem.
CR 92134	Uninstall problems
Problem	Some problems have been reported with the product uninstallers.
Platform	All.
Workaround	If you cannot get the uninstaller to run, first make sure you have a JDK installed and included as part of your executable PATH. If that fails to correct the issue, you will need to uninstall the product manually. In the case of upgrade installers, you can find backups of files modified by the service pack installation in the directory <PORTAL_HOME>/servicepacks/sp3/backup. In addition, you can restore your backups of the product which you should have made prior to the installation of the service pack.

 

Workaround for 84487

The is the default behavior for stockportal, but you can modify this behavior by following these steps:

1. Extract the following classes from <portal-home>\applications\portal\stockportal\WEB-INF\lib\ portal_servlet.jar and place them in your web applications WEB-INF\lib directory:
   com.bea.portal.appflow.processor.MaximizeProcessorAnonymous.class
   com.bea.portal.appflow.processor.UnmaximizeProcessorAnonymous.class

2. Edit your webflows to change all occurrences of "MaximizeProcessor" to "MaximizeProcessorAnonymous", and change all occurrences of "UnmaximizeProcessor" to "UnmaximizeProcessorAnonymous". In the stockportal web application these changes would be made portal.wf in ebcc4.0\applications\portal\application-sync\webapps\stockportal and ebcc4.0\applications\portal\default\portal.

3. Modify framework/titlebar.jsp as follows:

Change this:

  if (request.getRemoteUser() != null)
  {
    if (PortletRenderHelper.isMaximized(request))
    {
%>
        <%@ include file="maximize_titlebar.inc"%>
<%
    }
    if (PortletRenderHelper.isInEditMode(request))
    {

To this:

  if (PortletRenderHelper.isMaximized(request))
  {
%>
        <%@ include file="maximize_titlebar.inc"%>
<%
  }
  else if (request.getRemoteUser() != null)
  {
        if (PortletRenderHelper.isInEditMode(request))
  {

1. Modify framework/normal_titlebar.jsp as follows:

   1. In the following code:

   Change this:

   if (request.getUserPrincipal() != null)
   {

   To this:

   <statement removed (actually moved further down in the file, see b.>

   1. In the following code:

   Change this:

   if (PortletRenderHelper.isEditable(request))
   {

   To this:

   if (request.getUserPrincipal() != null)
   {
   if (PortletRenderHelper.isEditable(request))
   {  
   

 

---

Miscellaneous Notes

The following list describes miscellaneous notes for this release. The list includes:

• Clarifications on the behavior of WebLogic Portal 4.0 features

• Clarifications on the behavior of other related products

• Limitations in other related products

1. DB2 Database Schemas and LOB data types. Service Pack 2 Only (CR 62937)

   DB2 databases require the specification of maximum sizes for LOB columns at table creation time. These maximum sizes are not noted in our Database Schema documentation because they are not required by other database systems. The following LOB column maximum sizes are imposed at DB2 database creation and/or migration time:

   Table	Column	LOB	Type	Size
   Personalization	SAMPLE_UUP_INFO	USER_INFO	CLOB	8K
   	DATA_SYNC_ITEM	XML_DEFINITION	CLOB	500K
   	AD_BUCKET	AD_QUERY	CLOB	25K
   	MAIL_MESSAGE	MESSAGE_TEXT	CLOB	25K
   	PLACEHOLDER_PREVIEW	XML_DEFINITION	CLOB	25K
   	ENTITLEMENT_RULESET	RULESET_DOCUMENT	CLOB	256K
   	CATALOG_PROPERTY_VALUE	BLOB_VALUE	BLOB	8K
   	PROPERTY_VALUE	BLOB_VALUE	BLOB	10K
   Commerce	DISCOUNT	DISCOUNT_RULE	CLOB	8K
   Event/Behavior Tracking	EVENT	XML_DEFINITION	CLOB	200K

2. Bulkloader Flags (CR 43378)

   If you have data that is longer than the column it is stored in, you can truncate the data or increase the column size.

   Truncate the data to match the column size

   Two Bulkloader flags are available, -truncate and -ignoreErrors. To set them to true, edit the loaddocs.bat or loaddocs.sh file and add them to the line that points to the Bulkloader utility. The files reside in PORTAL_HOME/bin/<platform>/.

   Increase column size to match the data

   Update the field in the database. Then edit the loader.properties file and increase the size of the appropriate column and table. The loader.properties file is packaged in the document.jar file in PORTAL_HOME\lib\p13n\ejb. The path to loader.properties is com\bea\p13n\content\document\ref\loader.

   Make your updates in loader.properties, then jar the document.jar file again.

3. Data size validation limitations. (CR 33436)

   Through the User Management administration tools, it is possible to set Customer Properties on a user. Because the tools were designed with generic text properties in mind, there is a length limit of 255 characters. However, Customer Properties have different size limits in the database and any property value that exceeds the database limit for that property will throw an exception and not be set. The workaround is to limit the length of Customer Properties to the size of the columns in the database. See the schema definitions for WLCS_CUSTOMER and WLCS_SHIPPING_ADDRESS.

4. The BulkLoader/Document Management Component does not correctly indicate whether a file has been deleted, modified, or renamed. (CR 35566)

   While using the BulkLoader to update the reference document repository, if you delete a file from the dmsBase directory, it still shows up when you search for documents or use content selector rules. Additionally:

   • If you modify a file in the dmsBase, sometimes that change is not reflected in the run-time system, or you, receive bad data (in the case of binary files like images).

   • If you rename a file in the dmsBase and run the BulkLoader, the previous name is still there (that is, it looks like duplicate entries).

   The workaround is to do any of the following, depending on whether you have modified, deleted, or renamed a file:

   • After modifying the contents of a file that is in the document repository, run the BulkLoader application as usual and include the -cleanup argument. This updates the entries already in the database according to what is currently in the dmsBase. The -cleanup argument cleans up the data that is already in the database and prevents BulkLoader from loading new files or changed metadata.

   After deleting or renaming a file on the filesystem that is in the document repository, do the following:

   • Run the BulkLoader application as usual and include both the -cleanup and the -delete arguments. This deletes entries in the database, if the corresponding file is not in the dmsBase directory.

   • If you renamed a file, you will also need to run the BulkLoader as normal to insert that file's entry into the database.

5. Catalog Administration pages limit the number of category levels you can add. (CR 35248)

   Using the Web-based administration pages for the product catalog, you must limit the hierarchy of categories to 25 levels deep. This is a limitation of the Web browser (not a limitation of the commerce catalog components) and may vary from versions of Netscape and Internet Explorer.

6. Browser cache settings for Administration Tools. (CR 40263)

   For the Administration tools, your browser cache setting should be set to "Every visit to the page" for Microsoft Internet Explorer and to "Every time" for Netscape. Intermittently, you could get pages back from cache when sending requests a second time in a session if the Never or Automatic cache settings are in use. For example, if you use Never or Automatic, a problem could occur in the following scenario:

   1. Create a property set

   2. Attempt to create the property set again; the message states that it could not be created

   3. Delete that property set; the message states that it has been deleted

   4. Create the same property set again; the message states that it could not be created, but it really has been created; the browser gave you the page from your last request again.

   In the Netscape browser, the Never Check Cache option does not work with the portal framework. Information will be lost. You can find this option in the Netscape browser under: Edit —> Preferences —> Advanced —> Cache —> Document in cache is compared to document on network. When using Netscape, use the "Every time" option.

   In the Internet Explorer browser, the Never check cache option does not work with the portal framework correctly. You can find this option on the Internet Explorer browser under Tools —> Internet Options —> General tab —> Temporary Internet files —> Settings —> Check for newer versions of stored pages. When using Internet Explorer, use the "Every visit to the page" option.

7. Missing HTTP headers in the default Request Property Set.

   The default request property set does not contain properties representing HTTP request headers. As a result, rules cannot be written on HTTP request headers. The software intentionally does not contain these properties because not all browsers support the same set of HTTP request headers.

   Using the Property Set Administration Tools, you can add HTTP request header properties to the Request Property Set named 'DefaultRequestPropertySet'.

   Some common HTTP request header names and types (all type Text) are: User-Agent, Connection, Host, Accept, Accept-Encoding, Accept-Language, Accept-Charset.

   To determine the exact HTTP request headers sent by the browser to the server, and what headers are supported by the Web server, you can run the 'snoop' servlet that comes with WebLogic Server or insert the following JSP code in a test JSP page:

   Enumeration names = request.getHeaderNames();
   while(names.hasMoreElements())
   {
   name = (String)names.nextElement();
   System.out.println("header : " + name + " : " +
   request.getHeader(name));
   }

8. User Management security realm support verification.

   The User Management system's realm support has been tested against the following realms:

   • The User Management out-of-the-box security realm.

   • The WebLogic LDAPRealm (weblogic.security.ldaprealmv1.LDAPRealm) against iPlanet 5.0 Directory Server.

   Although this is the extent of the realm verification, the User Management system is written in a general manner which should support any realm following the specification in the User Management documentation, with the exception of the WebLogic NT Realm, which has not been verified.

9. If in the WebLogic Server Console you change the port numbers from which WebLogic Server listens, you must also make corresponding changes in several files in PORTAL_HOME

   To resolve this issue, find all instances of the port number in configuration files (*.xml, *.bat, *.cmd, *.sh) and change them to the new port number.

10. If you change the WebLogic Server system password, you must also make a corresponding change in PORTAL_HOME/bin/<platform>/LoaderDriverProperties.xml.

    To resolve this issue, find all instances of the password in configuration files (*.xml, *.bat, *.cmd, *.sh) and change them to the new password.

11. While using the Administration Tools, browsers must accept cookies. (CR 35576)

    The JSP-based Administration tool requires the browser to accept cookies.

12. Trailing Spaces in WebLogic Server Console input field will cause errors at server startup.

    Note that the WebLogic Server Console treats spaces at the end of each line as valid characters and does not parse the spaces out.

    For example, if you copy and paste the string "weblogic.jdbc.oci.Driver " to the WebLogic Server Console's commercePool Driver Classname input field, the following error is reported at server startup time:

    <Date...> <Error> <JDBC Connection Pool> <Cannot startup connection on pool "commercePool"> Cannot load driver class:
    weblogic.jdbc.oci.Driver

    Keep this limitation in mind if you entered the correct input in the WebLogic Server Console but are seeing errors at server startup.

13. Differences in Ctrl-C Behavior on Windows 2000, and its effect on server shutdown. (CR 44098)

    Windows 2000 handles Ctrl-C differently than Windows NT. This affects what happens if you enter Ctrl-C in the server console window when you shut down the server. On Windows 2000, Ctrl-C stops the currently running step in the batch, but then prompts you to terminate the batch job. If you enter Yes, the batch job stops there and does not execute anything else. This can result in unintentionally leaving java executables processes running on your system. The solution is to answer No in response to the prompt on Windows 2000.

    Note: The recommended way (on any platform) to shut down the server is to run the StopPortal.bat/sh procedure in PORTAL_HOME.

14. On UNIX, cannot use spaces in path to license file with UpdateLicense.sh. Service Pack 2 Only (CR 44099)

    The UpdateLicense.sh procedure in the BEA_HOME directory on UNIX systems does not accept spaces in the path to the input license file.

15. Warning messages about EJB redeployment in Commerce Services (CR 44825)

    During startup, messages similar to the following are thrown:

    <Oct 27, 2001 1:00:43 PM MST> <Warning> <EJB> <EJB Deployment: com.beasys.commerce.ebusiness.catalog.CatalogManager cannot be redeployed while the server is running. com.beasys.commerce.ebusiness.catalog.CatalogManagerImpl is located in the server's classpath.> 

    This is because the product's EJBs are not hot deployable. Note that these warning messages are not displayed on the server console in the default configuration. These messages will only show in the console if you set the logging level to Warning or Info.

16. Error opening campaigns when the EBCC is not started in the \bin directory. (CR 44851)

    If you start the E-Business Control Center by running ebccw.exe in a directory other than the one in which the executable directly resides, you will see the following error message:

    Default campaign template is not valid, unable to create campaign. The selected item cannot be opened because of an error in its content.

    This only happens when you are in a command window and not in the correct \bin subdirectory. It does not happen when you:

    • Start the E-Business Control Center from the Start menu:
      Start —> Programs —>BEA WebLogic E-Business Platform —> BEA E-Business Control Center 4.0 —> E-Business Control Center.

    • Double-click the ebccw.exe executable file from Windows Explorer.

    • cd into the EBCC_HOME\bin directory to run ebccw.exe .

17. When making a change in WebLogic Portal that has a relationship to database information, you may also need to make a corresponding change in your database. (CR 44999)

    For example, if you remove a user with the User Management tool, you must also purge, obsolete, or archive that user's order history in your database. If this is not done, a user with the same name will have the previous user's order history. We recommend that you and your Database Administrator develop a policy for ensuring correspondence between databases and servers.

18. You can lose profile data if you switch domains while using the same database server for the RDBMSRealm. (CR 59065)

    WebLogic Portal supports a configuration in which different domains can use different file realms while using the same RDBMS repository. Under this configuration, different domains might have different realm data because of the file realm, even if they are both configured to use the RDBMSRealm pointed at the same database.

    For example:

    1. Create a domain "DomainA", with a filerealm.properties that defines a group "SpecialUsers" and an RDBMSRealm that points to Database1.

    2. Start the server with this domain.

    3. Set some properties for the "SpecialUsers" group.

    4. Shut down the server.

    5. Create a domain "DomainB", with a filerealm.properties that does not contain a "SpecialUsers" group and with an RDBMSRealm that points to Database1.

    6. Start the server with DomainB.

    7. The realm clean-up tool informs you that there is one misconfigured group because it sees a profile for SpecialUsers but it does not see the profile in the realm. If you click the clean-up button at this point, the clean-up tool will delete the SpecialUsers profile.

    8. When you restart the server with "DomainA" you will be able to see the "SpecialUsers" group again, but it won't have any profile data.

19. QuickEdit Mode in a DOS shell can lock up the WebLogic Portal server process. (CR 59100)

    On Microsoft Windows systems, the WebLogic Portal server process runs in a DOS shell. Some releases of Windows activate the QuickEdit Mode by default. With this mode activated, if you click and drag the mouse pointer in the DOS window, the console will lock up until you press a key.

20. Users of type WLCS_Customer cannot inherit default values from the CustomerProperties property set. (CR 59684)

    Because properties in the CustomerProperties property set cannot be set to null for a user of type WLCS_Customer, this type of user cannot inherit from a default value in the property set. This does not affect non-customer profiles, nor does it affect any other properties of customer profiles.

    While the WebLogic Portal Administration Tools do display inherited default values for the CustomerProperties property set, a getProperty call returns an empty String if you set values in CustomerProperties to null.

21. The E-Business Control Center cannot delete files with non-standard filenames. (CR 59810)

    The E-Business Control Center cannot delete files with names that contains spaces or other special characters. For example:

    1. In the directory C:\bea\ebcc4.0\applications\petflowApp\application-sync\webapps\petflow, you use the Windows Explorer to make a copy of user.wf

    2. Windows Explorer creates a file named Copy of user.wf.

    3. From the E-Business Control Center, if you try to delete a Webflow named Copy of user, you see an error message:
       could not delete Copy of user.null

22. Sample accounts and LDAP server. (CR 60290)

    If you are using LDAP for authentication and want to use the accounts and groups provided by the WebLogic Portal sample data, you must set up the accounts and groups in your LDAP server. It is not necessary to enter the first name and last name fields. The required fields in the LDAP records are the account names and passwords. For details, please see the "Overview of Portal Administration" chapter of Getting Started with Portals and Portlets.

23. Property searching does not support wildcard characters. (CR 60356)

    When searching for properties, such as properties from user profiles, HTTP Sessions or HTTP Requests, you cannot use characters such as * or ? as directives for matching parts of strings.

    For example, from the E-Business Control Center you configure a scenario action to fire when a visitor has specific characteristics. When you specify the characteristics, you cannot use * or ? as wildcards in an attempt to match partial strings.

24. When items are deleted, the user is not alerted when reopening entities to which those items are associated. (CR060418 and CR061615).

    If items referred to by a document are deleted, such as segments and placeholders referred to by a campaign, the E-Business Control Center does not alert the user when the document is reopened.

25. Sybase does not support sample data. Service Pack 2 Only (CR 63357)

    Sybase allows a maximum of 255 bytes for VARCHAR column definitions. However, the loadSampleData script that creates database tables for the WebLogic Portal sample applications creates DOCUMENT and DOCUMENT_METADATA tables that exceed this maximum.

    If you want to view sample data, you must use the default Cloudscape database or some supported database type.

26. Search for subgroups returns "group not found." (CR 61396)

    In User Management, if there are any subgroups added to a group, search returns "group not found".

27. Oracle Limitation: Reading CLOB data from UTF8 database with JDBC Thin. (CR 66757 and 76588)

    There is a known bug with the Oracle Thin Driver 8.1.7 when reading a CLOB from a UTF8 database. The error occurs when reading CLOB data that has more than 10838 double-bytes characters. The Oracle Bug number is 2140668.

28. PersistenceException- when Syncing from Solaris EBCC to server with SQL2000 DB. (CR 77354)

    If you create a connection to a server pointing to an SQL 2000, you will receive errors when you sync. Please check with BEA support if you have this problem. Please provide them with the CR number associated with this problem.

    weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:200)

 

---

Product Documentation

This section includes the following additional notes about the product documentation:

• Where to Get Product Documentation

• Refresh Browser to View Updated Pages

Where to Get Product Documentation

Documentation for this product is available from the following locations:

• On the product CD. If you ordered the WebLogic Portal 4.0 software packaged in a BEA product box, the product CD contains the software kit and the separate documentation kit for release 4.0. The documentation kit file name is wlportal400_doc.zip. After you install the product software, you can unzip a local copy of the product documentation in a directory of your choice (standalone option), or in the PORTAL_HOME\applications\wlpDocsApp\wlpDocs\* directory (manually integrated option). For information about the documentation installation procedure, see the Installation Guide.

• On the BEA e-docs Web site. Visit the BEA E-docs site at http://www.oracle.com/technology/documentation/index.html and select the entries for WebLogic Portal 4.0 online documentation, starting at http://download.oracle.com/docs/cd/E13218_01/wlp/docs40/index.htm.

• From the BEA download site. In addition to the product CD and the E-docs Web site, the product documentation is available in a separate download kit from the BEA Download Web site. The starting point is http://commerce.bea.com/downloads/products.jsp. On the final WebLogic Portal download page, look for the file wlportal400_doc_with_sp*.zip. After you install the product software, you can unzip a local copy of the product documentation in a directory of your choice (standalone option), or in the PORTAL_HOME\applications\wlpDocsApp\wlpDocs\* directory (manually integrated option). For information about the documentation installation procedure, see the Installation Guide.

• In PDF format. To access PDF files, open either your local copy or the e-docs version of the product documentation Home page (http://download.oracle.com/docs/cd/E13218_01/wlp/docs40/index.htm), click the PDF Files link, and select the document you want to view or print. If you do not have the Adobe Acrobat Reader, you can download it from the Adobe Web site at http://www.adobe.com/.

Refresh Browser to View Updated Pages

Depending on your browser settings, you may need to enter Shift-Reload (Netscape) or Shift-Refresh (Microsoft Internet Explorer) to see the latest version of WebLogic Portal documentation pages you have already visited. When in doubt, please refresh your browser view to ensure that you are viewing the latest content. Also check a refreshed WebLogic Portal documentation What's New page for information about recent updates.

 

---

Contacting BEA Customer Support

If you have any questions about this version of BEA WebLogic Portal, or if you have problems installing and running the product software, please contact BEA Customer Support through BEA WebSUPPORT http://www.bea.com/support. You can also contact Customer Support by using the contact information provided on the Customer Support Card, which is included in the product package.

When contacting Customer Support, be prepared to provide the following information:

• Your name, e-mail address, phone number, and fax number

• Your company name and company address

• Your machine type and licensing information

• The name and version of the product you are using

• A description of the problem and the content of pertinent error messages

Submitting Documentation Comments

Your feedback on the BEA WebLogic Portal documentation is important to us. Send us e-mail at [e-mail] if you have questions or comments about the documentation. Your comments will be reviewed directly by the BEA professionals who create and update the WebLogic Portal documentation.

Note: Please do not use the [e-mail] E-mail account to report software problems or inquire about software functionality.

In your e-mail message, please indicate that you are using the documentation for the WebLogic Portal 4.0 with Service Pack 2 release.

Note About Evaluation Support

If you are evaluating this product and it is your first 30-day evaluation, BEA Systems is pleased to offer technical support through its BEA WebEvalNET at http://www.bea.com/evalnet/.

The first time you need technical support, complete the WebEvalNET registration form to receive a Login ID and other BEA WebEvalNET information. In most cases, the BEA EvalNET team of support engineers will address your technical issues within one business day.