README

IBM(R) WebSphere(R) Commerce
Professional Edition
Business Edition
for Windows NT(R) and Windows(R) 2000

Version 5.4

Last Updated: March 22, 2002

Contents

What's in this README

This README file contains information about known problems with the product. Updates to this README file will be posted to the WebSphere Commerce Business Edition Technical Library page and to the WebSphere Commerce Professional Edition Technical Library page. You can also check the Technotes database on WebSphere Commerce Business Edition Support page and the WebSphere Commerce Professional Edition Support page for reported problems and other product support information.

Documentation

  1. The WebSphere Commerce Business Edition Technical Library page and the WebSphere Commerce Professional Edition Technical Library page contain any updates that have been made to the online help and installation guide. Also available is additional product information not shipped on the CD.
     
  2. If you use the WebSphere Commerce online help search function on a machine which is configured with regional settings other than en_US, you may experience problems such as improperly displayed national characters, or no search results. Upgrading the Java(TM) Runtime Environment may correct this problem. To obtain a more recent version, go to java.sun.com and search for Java 2 Runtime Environment. After upgrading the Java Runtime Environment, you must close all Internet Explorer windows before restarting the online help.

WebSphere Application Server 

The e-fix PQ57024 is required for WebSphere Application Server 4.0 FixPak2 in a Japanese environment. After applying the FixPak, install the e-fix PQ57024 provided to correct a problem with Japanese translation. You can download the e-fix from the following Web site:

WebSphere Application Server Support

For details about the problem corrected by the e-fix, see the README packaged with the e-fix.
 

Deployment of Customized Code

As part of deployment of both new enterprise beans and modified WebSphere Commerce public entity beans, an XML file must be generated that describes each of the beans in the WebSphere Commerce enterprise application. This file is created by using the XMLConfig tool with the "export" option.

This XML file cannot have carriage return characters included in the specification of the application server full name for each enterprise bean. Applying this workaround ensures that application server full names are properly formatted (that is, without carriage returns) in the XML file.

The workaround must be performed after you have completed any of the following tasks described in the WebSphere Commerce Programmer's Guide.

Each of the preceding tasks uses the XMLConfig -export command to create an XML file that provides configuration information for the enterprise beans in an enterprise application. This file is not formatted properly. In particular, the name of the application server is split across multiple lines. If this does not get reformatted to span only a single line, an error indicating that the application server cannot be found is encountered when the file is used as input to the XMLConfig -import command.

To properly format the XML file that is generated by the XMLConfig -export command, do the following:

  1. Using a text editor, open the OutputFile.xml, where OutputFile is the name of your file that was generated by the XMLConfig -export command.
  2. For each value that is contained between <application-server-full-name> and </application-server-full-name> tags, ensure that there are no carriage returns in the value. If a carriage return exists in this value, delete it so that the application server name is specified on a single line.
  3. Save the file.
  4. Continue with the next steps for code deployment, as described in the WebSphere Commerce Programmer's Guide.

Commands

If the response properties object of any command that redirects to another HTTP request (for example, redirecting to a JavaServer Page) is greater than 4KB in size, an error is generated. To avoid this error, you must modify the response properties object to contain less than 4KB of data before redirecting. One way to reduce the size of the response properties object would be to remove unnecessary parameters from URL strings. For information on this, refer to "Handling a limited length redirect URL" in the WebSphere Commerce Programmer's Guide.

Integration

WebSphere Commerce cannot use Domino as an LDAP server with the IBM Developer Kit for Windows, Java2 Technology Edition, v1.3 that is shipped as part of the present version of WebSphere Application Server. Check the WebSphere Commerce Business Edition Support page and the WebSphere Commerce Professional Edition Support page for updates.

WebSphere Commerce Accelerator

The Delete button has been removed from the Fulfillment Centers page.

Loader Package

The Loader may not roll back records in a failed commit. If this occurs, you can manually delete the records in the database. You can also specify the -method delete option on the Load command to delete the records from the database. The input file for the Loader must contain the records that need to be deleted when using this option. Refer to the Catalog Manager User's Guide for more information.

Trademarks and Service Marks

The following are trademarks or registered trademarks of IBM Corporation in the United States and other countries:
IBM      WebSphere   AIX  
Windows and  Windows NT are trademarks of Microsoft Corporation in the United States, other countries, or both.

Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both.

Other company, product, or service names may be trademarks or service marks of others.

**************************************************************************

** © COPYRIGHT INTERNATIONAL BUSINESS MACHINES CORPORATION 2002

** ALL RIGHTS RESERVED.

**************************************************************************
Note to US Government Users -- Documentation related to restricted rights -- Use, duplication, or disclosure is subject to restriction set forth in GSA ADP Schedule Contract with IBM Corp.

End of README File