Installing WebSphere Commerce V7 Developer Fix Pack 9, APAR JR53438.fp (readme)Installing WebSphere Commerce V7 Fix Pack 9, APAR JR53438.fp (readme)Installing WebSphere Commerce V7 Feature Pack 8, APAR JR53438.fep (readme)Installing WebSphere Commerce V7 Developer Feature Pack 8, APAR JR53438.fep (readme)

Cumulative interim fix JR53438 is a fully tested package that includes all the interim fixes that have accumulated for Fix Pack 9Feature Pack 8. This package eliminates the complicated installation process of applying many fixes individually. Any Fix Pack 9Feature Pack 8 interim fixes that are installed on the environment do not need to be uninstalled. Any Fix Pack 9 interim fixes that are created after the release of this cumulative interim fix require this cumulative interim fix as a prerequisite.Any Feature Pack 8 interim fixes that are created after the release of this cumulative interim fix require this cumulative interim fix as a prerequisite.

Follow these instructions to successfully install the interim fix JR53438.fpJR53438.fep on WebSphere Commerce Developer 7.0.0.97.0.0.9V7 Developer Feature Pack 8V7 Feature Pack 8.
Attention: If you encounter an Out Of Memory condition during the installation of this fix, see Encountering Out Of Memory during APAR installation.

1. Preparing to install JR53438

  • Ensure that WebSphere Commerce Developer 7.0 is at the 7.0.0.9 level (Fix Pack 9)Feature Pack 8 level before you apply this interim fix. This interim fix is not applicable to any other fix packfeature pack versions of WebSphere Commerce Developer 7.0.
  • Ensure that features are enabled. For more information, see Enabling features.
  • Install the latest cumulative interim fix for the fix pack version that you are on before you attempt to install the feature pack cumulative. The fix pack cumulative is a prerequisite.
  • Ensure that you are using the latest version of WebSphere Commerce Update Installer.
    Warning: If you need to install a newer version of Update Installer (UPDI), ensure that you do not overwrite the original Update Installer that is in the WCDE_installdir/UpdateInstaller directory. Install the new version to a different directory and use the new UPDI version to install an interim fix. The original UPDI version is used by Installation Manager when you upgrade a fix pack in WebSphere Commerce Developer. If you overwrite the original UPDI version, Installation Manager will fail during a fix pack upgrade.
  • Ensure that customizations are backed up and can be reimplemented if necessary. IBM ensures that the IBM Management Center for WebSphere Commerce compile completes successfully when only IBM code is present. IBM cannot ensure that the compile is successful when client-customized OpenLaszlo code is also present. If the compile is not successful, you must consult with Management Center developers who implemented the customizations.
  • Stop the WebSphere Commerce test server.
  • Create a back-up of your store archive file (.sar) if you are using a published store that is based on the Feature Pack 8 Aurora starter store.

    This fix changes Aurora starter store files.

    You can locate the file in the ConsumerDirect or ExtendedSites subdirectories in the following location:
    • WC_installdir/instances/instance_name/starterstores/
    • WCDE_installdir/starterstores/
Note: If you upgraded from Feature Pack 2 or 3 to Feature Pack 8 and encountered errors when you tried to enable foundation, this cumulative interim fix solves the issue but requires unique installation steps. Review the following topic before your begin installing the cumulative interim fix, Enabling features when you upgrade from Feature Pack 2 or 3 to Feature Pack 8.

2. Installing WebSphere Commerce Developer interim fix JR53438.fpJR53438.fep

You must install this interim fix from the machine where you created your WebSphere Commerce instances. If customizations are not deployed by using the recommended methods, they might be lost by applying this fix. For more information, see Deploying in the IBM Knowledge Center. Complete the following steps to install the cumulative interim fix and then manually enable fixes on your environment.

Procedure

  1. Install the cumulative interim fix by following the steps in Installing WebSphere Commerce Developer interim fixes Installing WebSphere Commerce interim fixes.
    Note: If you upgraded from Feature Pack 2 or 3 to Feature Pack 8 and encountered errors when you tried to enable foundation, this cumulative interim fix solves the issue but requires unique installation steps. Review the following topic before your begin installing the cumulative interim fix, Enabling features when you upgrade from Feature Pack 2 or 3 to Feature Pack 8.
  2. Review the optional steps and complete any steps that apply to your environment.
  3. Review the optional steps and complete any steps that apply to your environment.
  4. Republish your WebSphere Commerce Test Server.

3. Completing optional steps after you install cumulative interim fix JR53438.fep

Some fixes and enhancements that are included in this package are not automatically enabled because you might not need them on your environment. The following list describes optional fixes and enhancements that you can manually enable. Review the following section to see if you want to enable any new features or apply any particular fixes.

Before you begin

Before you review the following procedure, complete the additional steps (section 3) in the cumulative interim fix (JR53438.fp) readme file for Fix Pack 9.

Procedure

  1. Fixes and enhancements related to Stores and Mobile:
    1. Optional: Enabling store-related interim fixes - Enable these fixes if you encounter any of the following issues in your Aurora starter store.
      • JR51843 fixes an issue where a shopper's order history, wish list, and other store pages display empty product information when a product is not in the current sales catalog
      • JR52816 fixes display issues and link-related issues in the Facebook Like and Facebook Activity widgets
      • JR51876 fixes an issue where non-English characters display in the browser title after you republish the Aurora starter store.
      The following folders contain the fixes for JR51843, JR52816, and JR51876:
      • In the WC_installdirWCDE_installdir/components/store-enhancements/wc.ear/Stores.war/ directory:
        • com.ibm.commerce.store.widgets.OrderDetail_ItemTable
        • com.ibm.commerce.store.widgets.RequisitionListItems
        • com.ibm.commerce.store.widgets.SavedOrderItems
        • com.ibm.commerce.store.widgets.FacebookActivity
        • com.ibm.commerce.store.widgets.IBMProductRecommendations
        • com.ibm.commerce.store.widgets.PDP_FacebookLike
      • In the WC_installdirWCDE_installdir/components/store-enhancements/starterstores/ConsumerDirect/Aurora.sar file:
        • StoreAssetsDir/EmailTemplates
        • StoreAssetsDir/ShoppingArea
        • StoreAssetsDir/Snippets
        • StoreAssetsDir/UserArea
        • StoreAssetsDir/Widgets
        • StoreAssetsDir/css
        • StoreAssetsDir/data
    2. Optional: Enabling interim fix JR52714 - Enable this fix if you are integrated with Sterling Selling and Fulfillment Suite 9.4 and you want to be able to view the Order Details page for a store order.
      Interim fix JR52714 addresses an issue where an order details service call that includes the ModificationType input parameter does not return the JSON response in the expected format. You can enable this fix to ensure that users can see order history details on the Order Details page when side-by-side integration is enabled between WebSphere Commerce and Sterling Selling and Fulfillment Suite.
  2. Fixes and enhancements related to Search:
    1. Optional: Setting up the search index - Enable these fixes if you want to use any of the following features:
      • Use the di-buildindex utility on an Oracle 12c database
      • Use an option to incrementally publish or unpublish a product or category for each language independently
      • Ensure that the sequence of products in the product list page on the storefront matches the sequence that is defined in Management Center
  3. Fixes and enhancement related to Runtime:
    1. Optional: Enabling interim fix JR52486 - Enhancement: Enable this fix if you want to use your custom search profile wc-rest-resourceconfig.xml as the default search profile.

3. Completing optional steps after you install cumulative interim fix JR53438.fp

Some fixes and enhancements that are included in this package are not automatically enabled because you might not need them on your environment. The following list describes optional fixes and enhancements that you can manually enable. Review the following section to see if you want to enable any new features or apply any particular fixes.

Note: If you installed cumulative interim fix JR52306.fp, you do not have to repeat any steps that you previously completed.

Procedure

  1. Fixes and enhancements related to Orders, Payments, and Inventory:
    1. Optional: Enabling interim fix JR52515 - Enhancement: Enable this fix if you want your DOM inventory system to skip inventory reservation in a shopping flow.
    2. Optional: Enabling interim fix JR53434 - Enhancement: Enable this fix if you want to limit the maximum number of pending orders that a single user can create.
  2. Fixes and enhancements related to Catalog, Assets, Contracts, and Pricing:
    1. Optional: Applying interim fix JR52552 - Enable this fix if a user with the Workspace Task Group Approver role cannot view catalog information in Management Center.
    2. Optional: Enabling interim fix JR53335 - Enable this fix to improve caching for contract pricing. The wcs.cacheivl.trigger.sql file is updated in JR53335, therefore you need to drop and recreate triggers.

5. List of fixes

JR53438.fp provides a set of interim fixes for WebSphere Commerce V7 Fix Pack 9. All interim fixes for Fix Pack 9 that are created after the release of JR53438.fp require JR53438.fp as a prerequisite.JR53438.fep provides a set of interim fixes for WebSphere Commerce V7 Feature Pack 8. All interim fixes for Feature Pack 8 that are created after the release of JR53438.fep require JR53438.fep as a prerequisite.
Note: JR53438 is the second cumulative interim fix for Fix Pack 9. Every subsequent cumulative interim fix release contains all fixes from the previous cumulative releases.

For a complete list of fixes that are included in this package, see Cumulative interim fixes for Fix Pack 9Cumulative interim fixes for Feature Pack 8.