README

IBM(R) WebSphere(R) Commerce
Professional Edition
Business Edition
for iSeries(R) eServer(TM) 400

Version 5.4

Last Updated: March 4, 2002

Contents

• What's in this README
• CD contents
• Documentation
• Deployment of Customized Code
• WebSphere Application Server
• Commands
• WebSphere Commerce Accelerator
• Store Publish
• Loader

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.

CD contents

WebSphere Commerce Professional Edition comes packaged on two CDs. WebSphere Commerce Business Edition comes packaged on three CDs. The CDs contain all of the National Language Versions.
The CD's contents are as follows:

Disk 1

• *BASE
• Option 1
• Option 2
• English (MRI2924, MRI2938, MRI2950, MRI2984)

  To complete the install, and take advantage of all of the product's features, you must install *BASE, Option 1, and Option 2. The English MRI is optional, unless you are using an iSeries machine with an English environment.

Disk 2

• Brazilian Portuguese (MRI2980)
• French (MRI2928, MRI2940)
• German (MRI2929, MRI2939)
• Italian (MRI2932, MRI2942)
• Spanish (MRI2931)
• Japanese (MRI2962)
• Korean (MRI2986)
• Simplified Chinese (MRI2989)
• Traditional Chinese (MRI2987)
  
  Install the MRI required for each language you plan on supporting.

Disk 3 (Business Edition only)

• Option 3.
  
  You must install this option if you are running WebSphere Commerce Business Edition.

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.

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.

• "Exporting XML configuration information for the enterprise application" in Chapter 9.
• "Exporting XML configuration information for the enterprise application" in Chapter 10.
• "Exporting configuration information for enterprise beans" in Appendix B.
   

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

WebSphere Application Server

1. After the WebSphere Commerce instance configuration is complete, you must re-generate the WebServer plugin in the WebSphere Application Server administrative console as follows:
   1. Open the WebSphere Application Server administrative console.
   2. Expand Nodes.
   3. Right-click your_node.
   4. Select Regen WebServer Plugin.
   5. From an iSeries command window, start your HTTP Server, only after the date stamp has changed on the file /QIBM/UserData/webasadv4/was_inst/config/plugin-cfg.xml.

      This is required after all instance updates which impact the WebSphere Application Server, such as virtual hosts, cloning, and other similar changes.
       

2. If you create more than one instance, you will receive an error message stating that the HTTP Transport Port is already in use when you start another WebSphere Commerce instance. You must do the following and then re-generate the plugin configuration in the WebSphere Application Server administrative console:
1. Open WebSphere Application Server administrative console.
2. Expand Administrative Domain.
3. Expand Nodes.
4. Expand host_name.
5. Expand Application Servers.
6. Select your Application Server instance name - WebSphere Commerce Server.
7. Click on the Services tab.
8. Select Web Container Service.
9. Click Edit Properties.
10. Click the Transport tab.
11. Select the HTTP Transport and click Edit.
12. In the Transport Port field, enter a unique port number.
13. Click OK.
14. Click OK.
15. Click Apply.

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.

WebSphere Commerce Accelerator

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

Store Publish

The following java system property is needed to ensure proper error handling when store publish fails.

Add this property using the WebSphere Application Server administrative console:

1. Open the WebSphere Application Server administrative console.
2. Expand Nodes.
3. Expand your_node.
4. Expand Application Servers
5. Click instance_name.
6. Click JVM Settings, and add the following:
   com.ibm.wcm.ErrorReporterDir = /QIBM/UserData/WebCommerce/instances/instance_name/temp/tools/devtools
   
   This value should be the same as the TempPath property specified in the instance configuration file, which is named similar to: /QIBM/UserData/WebCommerce/instances/instance_name/xml/instance_name.xml
7. Click Apply then restart your instance.

Loader

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(*DLT)option on the LODWCSDTA 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

IBM      WebSphere     iSeries
eServer

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.

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

End of README File