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
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.
WebSphere Commerce Build and Deployment tool issues
If you encounter problems while using the Build and Deployment tool, refer to the troubleshooting information to help determine the problem and find possible solutions.
package-info classes are not compiled by the build process
In certain cases, if Apache Ant 1.7.1 is used, the build process does not compile package-info.java files.

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.
    - WebSphere Commerce Build and Deployment tool issues
      If you encounter problems while using the Build and Deployment tool, refer to the troubleshooting information to help determine the problem and find possible solutions.
      - Ant tasks and types fail to load or run due to missing classes
        The build and deployment processes fail when Ant tasks and types that depend on external libraries fail to load or run.
      - EJB deployment fails in the build process on Windows operating systems
        On a Windows build system, the EJB deployment process might fail due to an IOException with error code 87.
      - package-info classes are not compiled by the build process
        In certain cases, if Apache Ant 1.7.1 is used, the build process does not compile package-info.java files.
      - Server deployment process fails at task MapModulesToServers
        Deployment of a new Java EE module using the server deployment process with the WebSphere Commerce Build and Deployment tool fails at task "MapModulesToServers" with a WASX7111E error.
      - Application fails to start due to incorrect settings
        After deploying your customization using the server deployment process with the WebSphere Commerce Build and Deployment tool, the WebSphere Commerce application fails to start due to incorrect settings applied to the WebSphere Commerce Java EE modules. Examples of incorrect settings include data source JNDI names and virtual hosts.
      - Running SQL scripts
        When you make database schema changes, you run SQL scripts.
      - WCBD utility error ''package com.ibm.mq does not exist''
        WCBD build process fails if an EJB project has dependencies on IBM MQ.
    - Loading changed data
      You encounter problems when you load changed data with the idresgen and massload utility.
    - Loading access control policies
      You encounter problems loading changed access control policy data using the loading utility, acpload.
    - Enabling application management tracing
      You encounter errors during deployment or suspect that your changes are not being deployed. You need more details on the errors to help determine how to fix them.
    - Error WSW0012E when deploying an EJB module that contains Web services
      When deploying an EJB module that contains Web services, you may see the WSWS0012E error message.
    - Changes do not appear in the application during run time
      The WebSphere Application Server deployment tool indicated that the deployment was complete; however, changes do not appear in the application during run time.
    - Backing up and restoring your Java assets
      While you deploy your Java EE assets, you can encounter problems and require a rollback of your changes.
    - Displaying incorrect content
      You test the URL in your browser and see that the old content is displayed.
    - Error 404 - File not found
      You test the URL in your browser and encounter Error 404 - File not found.
    - Error 403 - Forbidden
      You test the URL in your browser and encounter Error 403 - Forbidden.
    - Gathering data to troubleshoot deployment
      When you deploy your custom files and changes to your production server, you may run into deployment problems using WebSphere Application Server.
    - Save conflict error
      You receive a save conflict when you try to run a job that requires an EAR update.
  - 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.
  - 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: Package-info classes are not compiled by the build process

In certain cases, if Apache Ant 1.7.1 is used, the build process does not compile package-info.java files.

Problem

The javac Ant task employs specific code logic to handle package-info.java. In Apache Ant 1.7.1, the logic includes package-info.java for compilation only if one of the following conditions are met:

package-info.class already exists in the output directory at the package level.
The output directory does not exist.
The last modified timestamp of package-info.java is newer than that of the output directory.

For connector and EJB modules, the source directory is the same as the output directory by default (specifically, connectorModule and ejbModule). With the WebSphere Commerce Build and Deployment tool, compilation of such modules is done in such a way that the first condition would not be met. If there are other Java files in the same package as package-info.java, it is possible that the javac task will process the other Java files first. In this case, the output directory will be created (which deviates from the second condition) and its last modified timestamp will be updated as class files are generated. At this point, the output directory is always newer than package-info.java and the last condition would not be met. package-info.class is therefore not generated.

Note: If package-info.java does not contain any annotation, regardless of the above conditions, package-info.class will not be created.

Solution

The problem has been fixed in Apache Ant 1.8.0, so the solution is to upgrade to Apache Ant 1.8.0 or later.