Installing WebSphere Commerce V7 Developer Fix Pack 9 cumulative interim fix JR59483.fp (readme)Installing WebSphere Commerce V7 Fix Pack 9, cumulative interim fix JR59483.fp (readme)Installing WebSphere Commerce V7 Feature Pack 8, cumulative interim fix JR59483.fep (readme)Installing WebSphere Commerce V7 Developer Feature Pack 8, cumulative interim fix JR59483.fep (readme)

Cumulative interim fix JR59483 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 JR59483.fpJR59483.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 JR59483

Note: Follow the installation instruction provided in JR60453 if you downloaded the JR59483 before December 24th 2018.
  • Complete the steps in the following topic, Preparing to install WebSphere Commerce maintenance.
  • 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.
  • Ensure that you also downloaded the latest cumulative interim fix for Fix Pack 9 (JR59483.fp) before you attempt to install the feature pack cumulative. The fix pack cumulative is a prerequisite.
  • Ensure that you are using the latest version 7.x 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 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 you 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 cumulative interim fix JR59483.fpJR59483.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 you begin installing the cumulative interim fix, Enabling features when you upgrade from Feature Pack 2 or 3 to Feature Pack 8.
  2. This cumulative interim fix updates the following files, which you might have customized:
    • WC_eardir/xml/PromotionEngineConfiguration/WCSPromotionEngineConfig.xml
    • WC_installdir/wc.ear/xml/PromotionEngineConfiguration/WCSPromotionEngineConfig.xml  
    • WCDE_installdir/workspace/WC/xml/PromotionEngineConfiguration/WCSPromotionEngineConfig.xml
    Compare and merge the updates into your customized version of the WCSPromotionEngineConfig.xml file.
  3. Review the optional steps and complete any steps that apply to your environment.
  4. Review the optional steps and complete any steps that apply to your environment.
  5. Republish your WebSphere Commerce Test Server.

3. Completing optional steps after you install cumulative interim fix JR59483.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 steps, review section 3 of the cumulative interim fix (JR59483.fp) for Fix Pack 9, Completing optional steps after you install cumulative interim fix JR59483.fpCompleting optional steps after you install cumulative interim fix JR59483.fp.

Procedure

  1. Fixes and enhancements related to Search:
    1. Optional: Enabling interim fix JR58696- Enable this fix to resolve the issue that, when building extension index with language cores, the word generic is added to the core name.
  2. Fixes and enhancements related to Marketing and Promotions:
    1. Optional: Enabling interim fix JR59223 - Enable this fix to enhance the WebSphere Commerce backend services to support General Data Protection Regulation (GDPR).

3. Completing optional steps after you install cumulative interim fix JR59483.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 previously installed a cumulative interim fix for Fix Pack 9, then 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 JR58214 - Enable this fix to resolve a Failed to find physical store by external identifier error if you are integrated with Sterling Order Management.
    1. Optional: Enabling interim fix JR58394 - Enable this fix if you want to disable the API change to query ORDIADJUST table that were included in JR48648.
  2. Fixes and enhancements related to Marketing and Promotions:
    1. Optional: Enabling interim fix JR59223 - Enable this fix to enhance the WebSphere Commerce backend services to support General Data Protection Regulation (GDPR).
  3. Fixes and enhancements related to Member and Session Management:
    1. Optional: Enabling interim fix JR52717 - Enable this fix to resolve an issue where the shopper registration fails if the LDAP server is enabled with UserAccountValue 512 and 544.
  4. Fixes and enhancements related to Catalog, Assets, Contracts, and Pricing:
    1. Optional: Enabling interim fix JR58887 - Enable this fix if you want to resolve the issue with contract ID settings with generic users.
  5. Fixes and enhancement related to Runtime:
    1. Optional: Enabling interim fix JR59684 - Enable this fix to resolve an issue with contract ID settings of generic users, which was partially resolved by JR58887.

5. List of fixes

JR59483.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 JR59483.fp require JR59483.fp as a prerequisite.JR59483.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 JR59483.fep require JR59483.fep as a prerequisite.
Note: JR59483 is the fourth 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.