README

IBM(R) WebSphere(R) Commerce
Professional Edition
Business Edition
for Solaris Operating Environment(TM) software

Version 5.4

Last Updated: March 27, 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.
     

Installation

  1. Many warning messages appear during installation. To prevent this, do the following before adding the WebSphere Commerce docs package:
    1. Click on the Properties menu.
    2. Click on the Package Administration menu
    3. The default option for Existing Files should be "Ask". Change it to "Overwrite"
    4. Click on OK
    5. Proceed to add the docs package.
  2. For machines that do not allocate a file system for /opt and /export/home, the wc54sunpreq.sh script returns the following error:

    FREE HARD DRIVE SPACE in 1K blocks:
    No /opt directory detected  FAIL
    No /export/home directory detected  FAIL

    You will need a total of 5 GB free space between /opt and /export/home.

    3. Note that the error message appears whether or not you have 5 GB free space. As long as you have 5 GB free space, ignore the message.

  3. When you run the script used to start the Configuration Manager, you may get an error message that states: "whoami not found". Ensure the following two lines are in the .profile of both root and wasuser:

    PATH=$PATH:/usr/ucb
    export PATH

     Run the script again to launch Configuration Manager.
  4. To start WebSphere Application Server (WAS) as a non-root user, the /tmp directory must have file permissions set to 777 since WAS will be writing to this directory.
  5. While running wcpostinstall.sh, if you choose an existing user ID other than the default to run WebSphere Application Server, the default home directory of that user ID must be /export/home/userID. If you choose to create a new user ID, the home directory for that user ID will be created correctly by the script.
  6. WebSphere Commerce supports the following codesets:
    Language LANG variable value
    German de_DE.ISO8859-1
    English en_US.ISO8859-1
    Spanish es_ES.ISO8859-1
    French fr_FR.ISO8859-1
    Italian it_IT.ISO8859-1
    Brazilian Portugese pt_BR.ISO8859-1
    Japanese ja_JP.eucJP
    Korean ko_KR.EUC
    Simplified Chinese zh_CN.GBK
    Traditional Chinese zh_TW.BIG5

    Ensure that the supported codeset for your locale is installed on your Solaris machine. To check the installed codesets, run locale -a.
    Ensure that any locale-related environment variables (LANG, LC_ALL) are set to include the WebSphere Commerce supported locale. To check, run locale, and check LANG and LC_ALL variables. If your locale is not set to the supported codeset, change your locale properties by running the following commands as root user:

    LANG=xx_XX.XXXX
    export LANG
    LC_ALL=xx_XX.XXXX
    export LC_ALL

    For example:
    LANG=en_US.ISO8859-1
    export LANG
    LC_ALL=en_US.ISO8559-1
    export LC_ALL

    You must ensure these values are set correctly as root before you run wcpostinstall.sh. For non-root configuration, after you run wcpostinstall.sh, you have to edit /export/home/wasuser/.profile file. In the .profile file, LANG value should be set to the supported codeset. Add the codeset extension. For example: from LANG=en_US to LANG=en_US.ISO8559-1.
     

  7. In the Instance Creation wizard, the Database Administrator home directory field is mandatory. If it is not filled in, instance creation will fail.

WebSphere Application Server 

  1. 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.
     
  2. If you are installing WebSphere Application Server Advanced Single Server Edition on a Sun Solaris machine, you need to change the GB2312 key to GBK in the converter.properties file to avoid corrupted pages. The converter.properties file is located in the following directory: WebSphere/AppServer/properties. 

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.

Store Publish

The following java system property is needed to ensure proper error handling if 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 = /opt/WebSphere/CommerceServer/temp/instance_name/tools/devtools
  7. Click Apply then restart your instance.

Catalog Manager and Loader

  1. Online help doesn't launch for Text Transformer and XSL Editor. The tools do not launch the help and the error message refers to .hlp files. The Web page for the Text Transformer is located in the opt/WebSphere/CommerceServer/web/doc/locale/f1_fs/fdpttt.htm file. For the XSL Editor, refer to the file named fdpxtt.htm in the same directory.
  2. 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

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

Windows and  Windows NT are trademarks of Microsoft Corporation 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