Home
User Guide
The information contained in this section applies to WebSphere Commerce Version 8. The documentation also applies to all subsequent releases and modifications until otherwise indicated in a newer section.WebSphere Commerce is a single, unified e-commerce platform that offers the ability to do business directly with consumers (B2C), directly with businesses (B2B), and indirectly through channel partners (indirect business models). WebSphere Commerce is designed to be a customizable, scalable, and high availability solution that is built to leverage open standards. It provides easy-to-use tools for business users to centrally manage a cross-channel strategy. Business users can create and manage precision marketing campaigns, promotions, catalog, and merchandising across all sales channels.
Troubleshooting
Utilities
If you encounter problems while using WebSphere Commerce utilities, refer to the following troubleshooting information to help determine the problem and find possible solutions.
Data Load utility
If you encounter problems when you use the Data Load utility, refer to these troubleshooting topics to help determine the problem and find possible solutions.
XPath in Data Load utility configuration file is invalid
An error occurs when you are running the Data Load utility that generates an error message that an unexpected error occurred.

User Guide
The information contained in this section applies to WebSphere Commerce Version 8. The documentation also applies to all subsequent releases and modifications until otherwise indicated in a newer section.WebSphere Commerce is a single, unified e-commerce platform that offers the ability to do business directly with consumers (B2C), directly with businesses (B2B), and indirectly through channel partners (indirect business models). WebSphere Commerce is designed to be a customizable, scalable, and high availability solution that is built to leverage open standards. It provides easy-to-use tools for business users to centrally manage a cross-channel strategy. Business users can create and manage precision marketing campaigns, promotions, catalog, and merchandising across all sales channels.
- Planning
  Creating a custom implementation of a WebSphere Commerce store requires a significant amount of planning. From gathering client needs, to deploying the live solution, much work is needed to successfully deploy a custom client store. Use the resources in here to help you plan every phase of store creation.
- Installing
  Review the following sections for information about installing the WebSphere Commerce product, associated maintenance, and WebSphere Commerce enhancements.
- Migrating
  Before you migrate to WebSphere Commerce Version 8.0, review this information to help plan and execute your migration.
- Deploying
  The topics in this section describe how to publish stores to either a test or production environment, and how to deploy customized code.
- Operating
- Integrating
  Topics in the Integrating category highlight the tasks that are commonly performed for using WebSphere Commerce in combination with other products.
- Administering
- Tutorials
  WebSphere Commerce provides many tutorials to help you customize and understand your WebSphere Commerce instance and stores.
- Samples
- Developing
  The topics in the Developing section describe tasks performed by an application developer.
- Compliance
  The following section describes how you can leverage WebSphere Commerce features and functionality to help your site be compliant with different privacy and security standards.
- Securing
  These topics describe the security features of WebSphere Commerce and how to configure these features.
- Performance
- Troubleshooting
  - WebSphere Commerce messages
  - Contacting HCL Customer Support
    HCL Customer Support provides assistance with product defects. Contact HCL if you require assistance with an WebSphere Commerce problem.
  - Installation issues
    Both installing and uninstalling WebSphere Commerce encompass a wide range of steps. If you encounter problems, refer to the following resources for assistance.
  - WebSphere Application Server issues
    Review this information when you encounter problems with the WebSphere Application Server that is associated with your WebSphere Commerce instance.
  - Configuration issues
    If you encounter problems while configuring WebSphere Commerce, refer to the following resources for assistance.
  - Web server issues
    Review this information when you encounter problems with the Web server that is associated with your WebSphere Commerce instance.
  - General issues
    Review the following information when you encounter any general problems with WebSphere Commerce.
  - Update Installer issues
    If you encounter issues with the WebSphere Commerce Update Installer, refer to the following topics.
  - Fix pack issues
    If you encounter problems during the installation or uninstallation of the WebSphere Commerce fix pack, review the following issues:
  - WebSphere Commerce Developer fix pack issues
    Common fix pack installation problems and solutions for WebSphere Commerce Developer.
  - Deployment
    The troubleshooting information for deployment is divided into the following categories: Custom WebSphere Commerce database assets, Custom WebSphere Commerce Enterprise Application (EAR) or Java EE assets and Custom WebSphere Commerce Web server assets.
  - Access control problems
    Access control problems are often indicated by generic application errors with error message keys such as _ERR_USER_AUTHORITY. The first step in problem determination is to enable tracing for the access control component.
  - Catalogs
    If you encounter problems when you are managing or displaying catalogs, refer to the troubleshooting information to help determine the problem and find possible solutions.
  - Contracts
    If you encounter problems working with contracts, review the following troubleshooting topics.
  - Messages
    Problems encountered when sending e-mail for error notification.
  - Workspaces
    If you encounter problems while using workspaces, refer to the troubleshooting information to help determine the problem and find possible solutions.
  - Management Center
    If you encounter problems while using the Management Center, refer to the troubleshooting information to help determine the problem and find possible solutions.
  - Aurora starter store
    If you encounter problems when you use the Aurora starter store, refer to the troubleshooting information to help determine the problem and find possible solutions.
  - Changed data
    When data is changed in the WebSphere Commerce database, it will sometimes appear not to have any effect on the server functionality -- specifically, when the values are modified directly through loading utilities or through SQL statements. Certain tables are cached for performance reasons, and their values will not be reread by WebSphere Commerce until the server is restarted or the registry is refreshed. Examples of cached tables are the STORE table or the URLREG table.
  - Promotion code problem
    When you try to log on to the storefront in a B2C store, the Logon URL is used to log on to the system. If information already exists for the guest customer, the guest customer's basic information, such as their shopping cart, is merged with the registered user. You might experience the following problem with the shopping cart merge because of promotion codes.
  - Guest shopping in the advanced B2B direct store
    When you try to log on to the storefront in an advanced B2B direct store, the Logon URL is used to log on to the system. If information already exists for the guest shopper, the guest shopper's basic information, such as their shopping cart, is merged with the registered user. You might experience the following problem with the shopping cart merge because of multiple pending shopping carts for the registered user.
  - Enabling error message details in the storefront
    The storefront hides specific error details from shoppers by default for security purposes. For example, instead of seeing a 404 error page with details, shoppers instead see a generic error page. If you need to enable error message details in the storefront, to satisfy a particular business requirement, you can enable verbose error messages in the configuration file.
  - Publishing a store archive
  - Storefront categories do not display after you publish a store archive
    After successfully publishing a store archive, the category navigation menu is not displayed in your storefront. For example, in the Aurora starter store, the Department menu does not display any categories.
  - Storefront does not display catalog filters
    When a catalog filter is applied to your store, the store continues to display catalog entries that are not included in the filtered catalog.
  - WebSphere Commerce Developer
    You might experience the following problems when you use WebSphere Commerce Developer.
  - Inventory issues
  - Logging issues
  - Member group issues
  - Promotions issues
  - Tax
    If you encounter problems while using the tax codes or calculation codes, refer to the troubleshooting information to help determine the problem and find possible solutions.
  - Utilities
    If you encounter problems while using WebSphere Commerce utilities, refer to the following troubleshooting information to help determine the problem and find possible solutions.
    - Data Load utility
      If you encounter problems when you use the Data Load utility, refer to these troubleshooting topics to help determine the problem and find possible solutions.
      - Troubleshooting: UserData is not defined in the Data Service Layer configuration
        When you load custom userData for business objects, an error can occur when the Data Service Layer (DSL) configuration mappings for the data is not in the expected directory. If DSL configuration mappings are in a custom extension directory, you must specify your WebSphere Commerce instance when you run the Data Load utility. If you do not specify your instance, the utility might not locate the DSL configuration for your userData, which can result in a userData is not defined error.
      - Data load fails on soft delete error with actionOnError configured
        When you load data to delete objects and the actionOnError property is enabled, a load operation can still fail when a soft delete error occurs. This load operation failure can occur when you do not enable the actionOnError for all mediators and do not define the delete mapping for all mediators.
      - ID not resolved for CATENTRY table with unique index data error
        The error occurs if the input file contains both unique ids and part numbers to resolve the ID.
      - Identifier or ID not found when running the Data Load utility
        When trying to load the description for a Catalog/Catalog Group/Catalog Entry/Attribute an error ID or identifier not found occurs.
      - Mandatory parameter missing when populating ITEMSPC table
        An error occurs while attempting to populate ITEMSPC table due to mandatory parameter missing.
      - Data Load fails to start in development environment
        An error occurs when you fail to stop the WebSphere Commerce test server in the development environment.
      - Error occurs when the VM argument is misspelled or omitted
        An error occurs when you misspell or omit the VM argument when running the Data Load utility.
      - Business object changes with the Data Load utility are not reflected in the Management Center
        Enabling dynamic caching on the WebSphere Commerce Server might cause some unexpected behavior when you update objects with the Data Load utility.
      - Data Load utility configuration file XML is invalid
        An error occurs when you are running the Data Load utility that generates an error message that the configuration XML file is invalid.
      - Data Load utility configuration file is missing environment configuration declaration
        An error occurs when you are running the Data Load utility that generates an error message that the configuration file is missing an element declaration.
      - Data Load utility configuration file is missing DataloadBusinessObjectConfiguration declaration
        An error occurs when you are running the Data Load utility that generates an error message that the configuration file is missing an element declaration.
      - Data Load utility configuration file content is invalid
        An error occurs when you are running the Data Load utility that generates an error message that the configuration file content is invalid.
      - PartNumber is missing or incorrect for business object
        An error occurs when you are running the Data Load utility that generates an error message that the mandatory property PartNumber is missing or incorrect.
      - Missing token value delimiter for input data file
        An error occurs when you are running the Data Load utility that generates an error message that the input data file does not have a matching token value delimiter.
      - XPath in Data Load utility configuration file is invalid
        An error occurs when you are running the Data Load utility that generates an error message that an unexpected error occurred.
      - Business object lock error during data load
        When you load data into an authoring server, you might encounter a business object lock.
      - ID not resolved when calculation codes are loaded into extended site stores
        The error occurs if the Data Load utility or the Catalog Upload feature attempts to load catalog calculation codes into the wrong asset store.
      - DataLoadApplicationException error or tokens are parsed incorrectly when using Data Load utility
        When you run the Data Load utility, you might encounter a DataLoadApplicationException error, or you might notice that tokens from the CSV file are parsed incorrectly.
    - Web feed utility issues
      The web feed utility returns log and trace information. Some typical problems include incorrect parameters that are passed to the utility, errors in data load configuration files, or insufficient space on the server.
    - idresgen utility
      If errors occur while resolving identifiers, refer to the following table.
    - Database connectivity
      You can encounter database connectivity issues when you are creating instances, applying maintenance, or running many WebSphere Commerce utilities. You can use the database connection validation utility to determine whether any configured database parameters that are required to establish a database connection are invalid.
    - File upload
      By default, WebSphere Commerce allows you to upload a file of up to 10 MB in size. You can upload a file where the size exceeds the limit by changing the maximum upload size.
  - WebSphere Commerce Search
    If you encounter problems while you use WebSphere Commerce Search, refer to the troubleshooting information to help determine the problem and find possible solutions.
  - Search engine optimization (SEO)
    If you encounter problems using search engine optimization (SEO), review the following issues:
  - REST services
    If you encounter problems with WebSphere Commerce REST services, refer to the troubleshooting information to help determine the problem and find possible solutions.
  - Staging server
    Issues you may encounter while using the stagingprop utility.
  - Administrator is locked out from Administration Console
    In the event you are locked out from the Administration Console, you need to update the database directly to unlock your account.

Troubleshooting: XPath in Data Load utility configuration file is invalid

An error occurs when you are running the Data Load utility that generates an error message that an unexpected error occurred.

Problem

When you try running the data load utility, you get an error similar to the following error message:

An unexpected error has occurred. The error is Class 'CatalogDescriptionType' does not have a feature named 'Shortdescription'.

This error can occur if your column or element names do not match your defined XPath values for the column or element names.

Solution

XPath is case-sensitive. Ensure that the spelling of the column or element names in your configuration file match the spelling of your XPath notation for mapping these names to create your business object.