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.
Installing
Review the following sections for information about installing the WebSphere Commerce product, associated maintenance, and WebSphere Commerce enhancements.
Installing maintenance
WebSphere Commerce updates include fixes to code or functionality through fix packs and include additions of new features or enhancements through mod packs.
Installing maintenance: Final steps
After you install a WebSphere Commerce maintenance package, complete the following steps.
Enabling fixes and enhancements that are included in maintenance packages
When you install a maintenance package, some fixes and enhancements are not automatically enabled on your environment for various reasons.
Additional steps for catalog, assets, contracts, promotions, or pricing-related interim fixes
Some maintenance packages might include changes that affect your Catalog, Assets, Contracts, and Pricing components. After you install a maintenance package, you might need to complete additional steps if you want to enable a particular fix on your environment.
Enabling fix JR57116
JR57116 provides the ability to invalidate specific cache objects that are in the WCPriceDistributedMapCache.

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.
  - Downloading WebSphere Commerce media images
    To install WebSphere Commerce, you require the product package. Follow these steps to successfully download the required media.
  - Installing WebSphere Commerce Developer
    This section describes how to install and configure WebSphere Commerce Developer. WebSphere Commerce Developer is a test environment for developers or system administrators to develop stores and WebSphere Commerce application code.
  - Installing WebSphere Commerce
    The following roadmap provides a guide to installing WebSphere Commerce.
  - Installing or enabling other software
    The following software programs need extra installation or enablement steps if you want to use them with WebSphere Commerce.
  - Installing maintenance
    WebSphere Commerce updates include fixes to code or functionality through fix packs and include additions of new features or enhancements through mod packs.
    - Maintenance overview
      WebSphere Commerce Version 8.0 provides maintenance packages that can include code fixes, security fixes, new features, or enhancements.
    - Preparing to install maintenance
      These steps prepare you to install WebSphere Commerce fix packs and mod packs. Review all of the following information before you continue with your WebSphere Commerce maintenance installation.
    - Installing maintenance for WebSphere Commerce
      Review the following topics to learn how to install and uninstall maintenance packages for WebSphere Commerce. Maintenance packages include fix packs and mod packs.
    - Installing maintenance for WebSphere Commerce Developer
      Review the following topics to learn how to install and uninstall maintenance packages (updates) for WebSphere Commerce Developer. Maintenance packages can include fix packs and mod packs.
    - Upgrading WebSphere Commerce to Java 8
      The following collection of tasks provide instructions on how to upgrade the version of Java on your WebSphere Commerce developer environment, runtime environment, or cluster. Upgrading to Java 8 allows for you to remain in product support for provided functionality, performance, and security fixes and enhancements.
    - Installing maintenance: Final steps
      After you install a WebSphere Commerce maintenance package, complete the following steps.
      - Enabling fixes and enhancements that are included in maintenance packages
        When you install a maintenance package, some fixes and enhancements are not automatically enabled on your environment for various reasons.
        Additional steps for store or mobile-related interim fixes
        Some maintenance packages might include changes to JSP files that you might have customized. To ensure that your customizations are not overwritten when you install maintenance packages, IBM does not automatically apply the changes to your environment. After you install a maintenance package, you might need to complete additional steps if you want to enable a particular fix on your environment.
        Additional steps for search-related interim fixes
        Some maintenance packages include changes to search indexes, search directory templates, or WebSphere Commerce Search configuration files. After you install a maintenance package, you might need to complete additional steps if you want to enable a particular fix on your environment.
        Additional steps for orders, payments, or inventory-related interim fixes
        Some fixes include changes that affect your Orders, Payments, and Inventory components. After you install a maintenance package, you might need to complete additional steps if you want to enable a particular fix on your environment.
        Additional steps for messaging or integration-related interim fixes
        Some maintenance packages include changes that affect your messaging services or affect your integrations with external components. After you install a maintenance package, you might need to complete additional steps if you want to enable a particular fix on your environment.
        Additional steps for catalog, assets, contracts, promotions, or pricing-related interim fixes
        Some maintenance packages might include changes that affect your Catalog, Assets, Contracts, and Pricing components. After you install a maintenance package, you might need to complete additional steps if you want to enable a particular fix on your environment.
        Enabling fix JR55608
        JR55608 introduces a new parameter that can allow the Data Load utility to change a catalog entry's parent master category relationship.
        Enabling fix JR57116
        JR57116 provides the ability to invalidate specific cache objects that are in the WCPriceDistributedMapCache.
        Enabling fix JR56189
        With JR56189, FIELD1 and FIELD2 columns of the OFFER table are returned by default for the price REST API. But if you want the FIELD1 and FIELD2 columns to be returned to calls from the display_price REST API, then you need to change a property in the price configuration file.
        Enabling fix JR56347
        JR56347 introduces a new parameter that changes the behavior of coupons. The new behavior is enabled by default.
        Additional steps for authoring or staging-related interim fixes
        Some maintenance packages might include changes that affect your authoring or staging environments. After you install a maintenance package, you might need to complete additional steps if you want to enable a particular fix on your environment.
      - Updating the WebSphere Commerce Build and Deployment tool
        WebSphere Commerce fix packs provide fixes and improvements for the Build and Deployment tool, which are highly recommended. After you install a fix pack, perform additional steps to incorporate the fixes into your configuration files and customization.
- 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

Enabling fix JR57116

JR57116 provides the ability to invalidate specific cache objects that are in the WCPriceDistributedMapCache.

Procedure

From a command prompt, connect to the production database with a proper user ID and password.
Drop the existing database triggers by invoking the following SQL script.
- WCDE_installdir/schema/dbtype/wcs.cacheivl.drop.trigger.sql
- WC_installdir/schema/dbtype/wcs.cacheivl.drop.trigger.sql
dbtype is the database type, for example, db2 or oracle.
Add the existing and new database triggers by invoking the following SQL script.
- WCDE_installdir/schema/dbtype/wcs.cacheivl.trigger.sql
- WC_installdir/schema/dbtype/wcs.cacheivl.trigger.sql