Installing WebSphere Commerce V7 Developer Fix Pack 6, APAR JR53048.fp (readme)Installing WebSphere Commerce V7 Fix Pack 6, APAR JR53048.fp (readme)Installing WebSphere Commerce V7 Feature Pack 5, APAR JR53048.fep (readme)Installing WebSphere Commerce V7 Developer Feature Pack 5, APAR JR53048.fep (readme)

Cumulative interim fix JR53048 is a fully tested package that includes all the interim fixes that have accumulated for Fix Pack 6Feature Pack 5. This package eliminates the complicated installation process of applying many fixes individually. Any Fix Pack 6Feature Pack 5 interim fixes that are installed on the environment do not need to be uninstalled. Any Fix Pack 6 interim fixes that are created after the release of this cumulative interim fix require this cumulative interim fix as a prerequisite.Any Feature Pack 5 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 JR53048.fpJR53048.fep on WebSphere Commerce Developer 7.0.0.67.0.0.6V7 Developer Feature Pack 5V7 Feature Pack 5.
Attention: If you encounter an Out Of Memory condition during the installation of this fix, see Encountering Out Of Memory during APAR installation.

Table of contents

  1. Preparing to install JR53048
  2. Installing WebSphere Commerce Developer cumulative interim fix JR53048.fepfp
  3. Completing required steps after you install cumulative interim fix JR53048.fep
  4. Completing required steps after you install cumulative interim fix JR53048.fp
  5. Completing optional steps after you install cumulative interim fix JR53048.fep
  6. Completing optional steps after you install cumulative interim fix JR53048.fp
  7. Removing a WebSphere Commerce interim fix
  8. List of fixes that are included in JR53048

1. Preparing to install JR53048

  • Ensure that WebSphere Commerce Developer 7.0 is at the 7.0.0.6 level (Fix Pack 6)Feature Pack 5 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.
  • If you are on Fix Pack 7 or later, download the prerequisite cumulative interim fix (JR53048.fp) for the Fix Pack version that you are on. Save the .pak file to a location that is accessible to the WebSphere Commerce Update Installer. For example, the UPDI_installdir/maintenance/ directory.
    Note: If you are on Fix Pack 6, you do not have to download the fix pack cumulative. The package is included when you downloaded the cumulative for Feature Pack 5.
  • 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 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 OpenLaszlo code is also present. If the compile is not successful, you must consult with Management Center developers who implemented the customizations.
  • Ensure that all customizations are deployed by using the recommended methods or customizations might be lost when you apply this fix. For information about the recommended method, see Deploying in the IBM Knowledge Center.
  • Create a back-up of your store archive file (.sar) if you are using a published store that is based on the Feature Pack 5 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/

2. Installing WebSphere Commerce Developer interim fix JR53048.fpJR53048.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.
  2. Complete the required steps to enable critical fixes on your environment.
  3. Complete the required steps to enable critical fixes on your environment.
  4. Review the optional steps and complete any steps that apply to your environment.
  5. Review the optional steps and complete any steps that apply to your environment.
  6. Republish your WebSphere Commerce Test Server.

3. Completing required steps after you install cumulative interim fix JR53048.fep

Some critical fixes that are included in this package could not be automatically enabled, therefore you need to manually complete the following steps. If you do not complete these required steps, your environment might not function properly.

Before you begin

The prerequisite fix pack cumulative interim fix might include additional installation steps to successfully enable the fix pack changes onto your environment. Before you move on to the following procedure, complete the required installation steps (section 3) for the fix pack cumulative interim fix.

Procedure

  1. Required: (Search) Updating the Solr web archive (WAR) - You must update the Solr web archive to synchronize the Solr server with the newest files.
  2. Required: (Search) Enabling interim fixes JR47273, JR47089, JR47194, JR43818 - You must enable these fixes, otherwise you might encounter errors when you run search-related utilities.
  3. Required: (Search) Enabling interim fix JR47787 - You must enable this fix, otherwise SEO URLs stop working if the default language is changed in Management Center.
  4. Required: (Marketing and Promotions) Enabling interim fixes JR45152, JR45153, and JR46765 - You must enable these fixes to apply schema changes to the PX_CDPOOL table. Completing this step also applies promotion performance enhancements and resolves exceptions that you might encounter when you publish a task group that contains promotions with promotion codes.
  5. Required: (Marketing and Promotions) Enabling interim fix JR48519 - You must enable this fix, otherwise you might encounter unexpected issues with the Promotions tool in Management Center. This fix provides performance enhancements when you attempt to view a promotion list that contains many promotions codes.
  6. Required: (Marketing and Promotions) Enabling interim fix JR43903 to update marketing expression builders - You must enable this fix, otherwise you will have outdated marketing expression builders.
  7. Required: (Catalog, Assets, Contracts, and Pricing) Enabling interim fix IV23778.fep - You must enable this fix to update OpenLaszlo files and ensure continuing Management Center functionality.
  8. Required: Replace dbconnect.zip file - For Oracle databases only: You must complete this step to ensure that the massload utility executes successfully.
  9. Optional: Complete optional steps after you install cumulative interim fix JR53048.fep.

    JR53048.fep includes some optional fixes and enhancements that are not automatically enabled on your WebSphere Commerce environment. To enable these optional fixes and enhancements, you need to complete some manual steps.

3. Completing required steps after you install cumulative interim fix JR53048.fp

Some critical fixes that are included in this package could not be automatically enabled, therefore you need to manually complete the following steps. If you do not complete these required steps, your environment might not function properly.

Procedure

  1. Required: (Authoring and Staging) Enabling interim fix JR43881 - For staging server only: You must enable this fix, otherwise you might encounter issues where the stagingprop utility fails when the utility attempts to propagate changes to production server.
  2. Required: (Catalog, Assets, Contracts, and Pricing) Enabling interim fix JR48723 - You must enable this fix to resolve potential security vulnerabilities. An access control policy was added for a component service and you must load the new policy.
  3. Required: (Member and Session Management) Enabling interim fix SE53160 - You must enable this fix to resolve Potential Information Disclosure vulnerabilities.
  4. Required: (Member and Session Management) Enabling interim fix JR44776 - You must enable this fix, otherwise you might encounter some access control issues related to orders. This fix sets the selected organization into the command context so that the eligible contracts can be retrieved in the entitlement context.
  5. Required: (Runtime) Enabling interim fix JR49904 - You must enable this fix, otherwise you might encounter errors related to the WebSphere Commerce scheduler. This fix also allows you to use the SCHBRDCST table to check the status of jobs in a cluster.
  6. Required: Replace dbconnect.zip file - For Oracle databases only: You must complete this step to ensure that the massload utility executes successfully.
  7. Optional: Complete optional steps after you install cumulative interim fix JR53048.fp.

    JR53048.fep includes some optional fixes and enhancements that are not automatically enabled on your WebSphere Commerce environment. To enable these optional fixes and enhancements, you need to complete some manual steps.

4. Completing optional steps after you install cumulative interim fix JR53048.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.

Procedure

  1. Fixes and enhancements related to Stores and Mobile:
    1. Optional: JR46693, JR49265, JR46284, and JR50880.fep - Enable these fixes to improve store functionality and performance.
      JR46693, JR49265, JR46284, and JR50880.fep fix the following issues:
      • Resolves an issue where if a bundle product contains swatches and you click an unavailable option, you are redirected to a blank page
      • Resolves an issue with Management Center store preview
      • Resolves an issue where product defining attributes and their values are displayed in a different sequence compared to the sequence that is defined in Management Center (Elite sample store only).
      If you did not customize your store, republish your store archive to propagate the changes to your environment. If you customized your store, review the following topic to ensure that your customizations are not overwritten, Enabling store-related interim fixes.
  2. Fixes and enhancements related to Search:
    1. Optional: Enabling interim fix JR46771 - Enable this fix if you want to improve store performance. Performance is improved by simplifying synonym expansion logic for AND type searches in the storefront.
    2. Optional: Enabling interim fix JR50873 - Enable this fix if you want to ensure that when the crawlurl and indexurl are the same, the URL is still crawled.
    3. Optional: Enabling interim fixes JR48505 and JR43778 - Enable these fixes if you want to enable deep search sequencing.
  3. Fixes and enhancements related to Runtime:
    1. Optional: Enabling interim fix JR44600 - Enable this fix if you want to preview content changes in BOD and REST service clients.
  4. Fixes and enhancements related to Messaging and Integration:
    1. Optional: Enabling interim fix JR46224 - Enable this fix if you want to improve performance for WebSphere Commerce environments that leverage the DOM inventory model.
    2. Optional: Enabling interim fix JR44017 - Enable this fix if you want to enable the following new features for WebSphere Commerce environments that are integrated with Sterling Order Management Systems:
      • The ability to load the inventory .csv files automatically with a scheduler job.
      • The ability to use a service to validate shipping methods of an order.
      • The ability to populate and return 'unit of measure' data for components of kits or bundles in the GetCatalogNavigationView service.
    3. Optional: Enabling interim fix JR44015 - Enable this fix if you want to enable the following enhancements for WebSphere Commerce environments that are integrated with Sterling Order Management Systems:
      • Adds the capability for an order item to reserve inventory from multiple fulfillment centers
      • Adds order merging capabilities: If a guest shopper submits a payment, completes an order, and then registers and logs on in the same session, WebSphere Commerce can now merge the order to the registered shopper's account. WebSphere Commerce then notifies the Sterling Order Management System that the user of the order changed, so that the registered shopper can view the information in the order history.
      • Includes performance improvements:
        • Code was modified to reduce potential deadlock issues
        • Improves the performance of the findInventory method
    4. Optional: Enabling interim fix JR44734 - Enable this fix if you want to support viewing historical order details in WebSphere Commerce, which were persisted in Sterling.
  5. Fixes and enhancements related to Member and Session Management:
    1. Optional: Enabling interim fix JR52577 - Enable this fix if you send along both WCToken and WCTrustedToken when making loginidentity REST calls. This fixes an issue where invalid JSON response is thrown when REST returns Invalid Token.
  6. Fixes and enhancements related to Marketing and Promotions:
    1. Optional: Enabling interim fix JR43657 - Enable this fix if you want to add the capability to create, update, and delete folders using the Promotions tool in Management Center.
    2. Optional: Enabling interim fixes JR49477 and JR49896 - Enable this fix if you want to ensure that 'one time use' promotion codes expire after they are used.
    3. Optional: Enabling interim fix JR47728 - Enable this fix if you want to improve promotion code generation utility performance on WebSphere Commerce environments with an Oracle database.
    4. Optional: Enabling interim fix JR43903 to display custom email templates - Enable this fix if you want to display custom email templates in Management Center.
  7. Fixes and enhancements related to Catalog, Assets, Contracts, and Pricing:
    1. Optional: Enabling interim fix JR47591 - Enable this fix if you have issues with associating attachments to catalog entries in Management Center.
    2. Optional: Enabling interim fix JR51140 - Enable this fix if you want to use Management Center to update FIELD1 to FIELD3 of the FACET table.
    3. Optional: Enabling interim fix JR46212 - Enable this fix if you encounter a NullPointerException when you use the Catalogs tool to browse categories in the utility pane for the Extended Sites Catalog Asset Store.
    4. Optional: Enabling interim fix JR45700 - Enable this fix if you want to add a "Save and Close" button in Management Center.
    5. Optional: Enabling interim fix JR43828 - Enable this fix if you want to enable a new "attribute folder" function for the Catalogs tool in Management Center.
    6. Optional: Enabling interim fix JR46213 - Enable this fix if you want to allow more than one contract to be passed in and evaluated in the GetCatalogNavigationView service call.
    7. Optional: Enabling interim fix JR50830 - Enable this fix if you want to save catalog entry descriptive attribute values for multiple languages in the Management Center.

4. Completing optional steps after you install cumulative interim fix JR53048.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.

Procedure

  1. Fixes and enhancements related to Catalog, Assets, Contracts, and Pricing:
    1. Optional: Enabling interim fix JR48723 - Enable this fix if workspaces is enabled in your development environment (WebSphere Commerce Developer).
    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.
  2. Fixes and enhancements related to Runtime:
    1. Optional: Enabling interim fix JR49256 - Enable this fix to ensure that Management Center honors the URL redirect filtering configuration.
    2. Optional: Enabling interim fix JR47553 - Enable this fix if shoppers encounter exceptions related to cookies, which forces shoppers to re-logon to continue shopping.
    3. Optional: Enabling interim fix JR46985 - Enable this fix if you want to apply traces at the class level and reduces the overhead of traces at the component level.
  3. Fixes and enhancements related to Orders, Payments, and Inventory:
    1. Optional: Enabling interim fix JR51793 - For ATP inventory users: Enable this fix to extend configuration options to all database types so that the concurrent inventory reservation (for ATP system) on the same product are avoided.
  4. Fixes and enhancements related to Member and Session Management:
    1. Optional: Enabling interim fix JR45670 - Enable this fix to allow simultaneous logon across multiple channels and browsers.
  5. Fixes and enhancements related to Marketing and Promotions:
    1. Optional: Enabling interim fix JR48904 - Enable this fix to improve performance of catalog entry entitlement checks during e-Marketing Spot recommendations.
    2. Optional: Enabling interim fix JR51650 - Enable this fix to add support for cachespec invalidation.
    3. Optional: Enabling interim fix JR47434 - Enable this fix to improve the performance of the Best Deal feature in the promotion engine when dealing with promotions that are of the same priority within the same group.
  6. Optional: Fixes and enhancements related to Authoring and Staging:
    1. Optional: Enabling interim fix JR46230 - For users with staging and production environments: Enable this fix to use key splitting to avoid key collisions during staging propagation.
    2. Optional: Enabling interim fix JR47901 - Enable this fix if you want to look up the inventory count from the storefront.

6. List of fixes

JR53048.fp provides a set of interim fixes for WebSphere Commerce V7 Fix Pack 6. All interim fixes for Fix Pack 6 that are created after the release of JR53048.fp require JR53048.fp as a prerequisite.JR53048.fep provides a set of interim fixes for WebSphere Commerce V7 Feature Pack 5. All interim fixes for Feature Pack 5 that are created after the release of JR53048.fep require JR53048.fep as a prerequisite.

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