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.
Table of contents
- Preparing to install JR53048
- Installing WebSphere Commerce Developer cumulative interim fix JR53048.fepfp
- Completing required steps after you install cumulative interim fix JR53048.fep
- Completing required steps after you install cumulative interim fix JR53048.fp
- Completing optional steps after you install cumulative interim fix JR53048.fep
- Completing optional steps after you install cumulative interim fix JR53048.fp
- Removing a WebSphere Commerce interim fix
- 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
Procedure
- Install the cumulative interim fix by following the steps in Installing WebSphere Commerce Developer interim fixes Installing WebSphere Commerce interim fixes.
- Complete the required steps to enable critical fixes on your environment.
- Complete the required steps to enable critical fixes on your environment.
- Review the optional steps and complete any steps that apply to your environment.
- Review the optional steps and complete any steps that apply to your environment.
- Republish your WebSphere Commerce Test Server.
3. Completing required steps after you install cumulative interim fix JR53048.fep
Before you begin
Procedure
3. Completing required steps after you install cumulative interim fix JR53048.fp
Procedure
4. Completing optional steps after you install cumulative interim fix JR53048.fep
Procedure
-
Fixes and enhancements related to Stores and Mobile:
-
Fixes and enhancements related to Search:
- 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.
- Optional:
Enabling interim fix JR50873 - Enable this fix if
you want to ensure that when the
crawlurl
andindexurl
are the same, the URL is still crawled. - Optional: Enabling interim fixes JR48505 and JR43778 - Enable these fixes if you want to enable deep search sequencing.
-
Fixes and enhancements related to Runtime:
- Optional: Enabling interim fix JR44600 - Enable this fix if you want to preview content changes in BOD and REST service clients.
-
Fixes and enhancements related to Messaging and Integration:
-
Fixes and enhancements related to Member and Session Management:
- 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.
-
Fixes and enhancements related to Marketing and Promotions:
- 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.
- 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.
- 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.
- Optional: Enabling interim fix JR43903 to display custom email templates - Enable this fix if you want to display custom email templates in Management Center.
-
Fixes and enhancements related to Catalog, Assets, Contracts, and Pricing:
- Optional: Enabling interim fix JR47591 - Enable this fix if you have issues with associating attachments to catalog entries in Management Center.
- Optional: Enabling interim fix JR51140 - Enable this fix if you want to use Management Center to update FIELD1 to FIELD3 of the FACET table.
- 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.
- Optional: Enabling interim fix JR45700 - Enable this fix if you want to add a "Save and Close" button in Management Center.
- 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.
- 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.
- 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
Procedure
-
Fixes and enhancements related to Catalog, Assets, Contracts, and Pricing:
- Optional: Enabling interim fix JR48723 - Enable this fix if workspaces is enabled in your development environment (WebSphere Commerce Developer).
- 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.
-
Fixes and enhancements related to Runtime:
- Optional: Enabling interim fix JR49256 - Enable this fix to ensure that Management Center honors the URL redirect filtering configuration.
- Optional: Enabling interim fix JR47553 - Enable this fix if shoppers encounter exceptions related to cookies, which forces shoppers to re-logon to continue shopping.
- 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.
-
Fixes and enhancements related to Orders, Payments, and Inventory:
- 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.
-
Fixes and enhancements related to Member and Session Management:
- Optional: Enabling interim fix JR45670 - Enable this fix to allow simultaneous logon across multiple channels and browsers.
-
Fixes and enhancements related to Marketing and Promotions:
- Optional: Enabling interim fix JR48904 - Enable this fix to improve performance of catalog entry entitlement checks during e-Marketing Spot recommendations.
- Optional: Enabling interim fix JR51650 - Enable this fix to add support for cachespec invalidation.
- 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.
- Optional:
Fixes and enhancements related to Authoring and Staging:
- 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.
- Optional: Enabling interim fix JR47901 - Enable this fix if you want to look up the inventory count from the storefront.
5. Removing a WebSphere Commerce interim fix
To remove a fix from WebSphere Commerce Developer, see Uninstalling WebSphere Commerce Developer Fix Pack interim fixesUninstalling WebSphere Commerce Fix Pack interim fixes.
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.