IBM® WebSphere Commerce V7 Developer Fix Pack 7, APAR JR53048.fp, readme fileIBM® WebSphere Commerce V7 Fix Pack 7, APAR JR53048.fp, readme fileIBM® WebSphere Commerce V7 Feature Pack 6, APAR JR53048.fep, readme fileIBM® WebSphere Commerce V7 Developer Feature Pack 6, APAR JR53048.fep, readme file
Cumulative interim fix JR53048 is a fully tested package that includes all the interim fixes that have accumulated for Fix Pack 7Feature Pack 6. This package eliminates the complicated installation process of applying many fixes individually. Any Fix Pack 7Feature Pack 6 interim fixes that are installed on the environment do not need to be uninstalled. Any Fix Pack 7 interim fixes that are created after the release of this cumulative interim fix require this cumulative interim fix as a prerequisite.Any Feature Pack 6 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 the WebSphere Commerce interim fix
- Installing WebSphere Commerce Developer cumulative interim fix JR53048.fepfp
- Completing required steps after you install cumulative interim fix JR53048.fep
- 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 the interim fix
- Ensure that WebSphere Commerce Developer 7.0 is at the 7.0.0.7 level (Fix Pack 7)Feature Pack 6 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 8 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 7, you do not have to download the fix pack cumulative. The package is included when you downloaded the cumulative for Feature Pack 6.
- 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.
- 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 6 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 apply critical fixes to 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
Required: Update Solr web archive (WAR)
Procedure
Required: Apply interim fix JR50044
Procedure
4. Completing optional steps after you install cumulative interim fix JR53048.fep
Procedure
-
Fixes and enhancements related to Stores and Mobile:
- Optional:
(Stores and Mobile) JR46451 - Apply
this fix to enable
relativeURL
generation by usingwcf:url
tags.
- Optional:
(Stores and Mobile) JR46451 - Apply
this fix to enable
-
Fixes and enhancements related to Search:
- Optional: (Search) JR47563 - Apply this fix if you have multiple instances at different feature pack levels so that you can run the preprocess utility and buildindex utility to use instance level JAR files rather than product level JAR files.
- Optional: (Search) JR48121 and JR49050. - Apply these fixes to improve performance of Solr multi-index reader.
- Optional: (Search) JR50286 - Apply this fix to improves Management Center performance by providing a flag so that unstructured delta indexing is not triggered by Management Center.
- Optional: (Search) JR49419 - Apply this fix to enable delta index build instead of always using the full index build.
- Optional: (Search) JR49587 - Apply this fix if you want to make entitlement fast flow configurable.
- Optional: (Seach) JR49326 and JR48977 - Apply these fixes to enable a new parameter for the invalidateSearchCache script so that you can specify a custom password file to store the encrypted passwords for the
- Optional: (Search) JR48148 - Apply this fix if shoppers cannot add to cart or add to wish list.
- Optional: (Seach) JR50755.fep and JR50129 - Apply this fix to update the the di-buildindex and di-preprocess utilities.
- Optional: (Search) Apply fix JR49109 - Corrects the multi-index handler to allow fields from inventory index to be returned along with collate spellcheck results.
- Optional: (Search) Apply fix JR48954 - Supports sequencing products across categories and all its subcategories.
- Optional:
(Search) Apply fix JR50873 - If you
modify StaticContentSitemap.jsp with
crawurl
andindexurl
to contain the same value, complete this step to fully apply the fix. - Optional: (Search) Apply fix JR48101 - Hides attribute values with zero count upon filtering and hides the facet if all facet counts are zero upon filtering.
-
Fixes and enhancements related to Runtime:
- Optional: (Runtime) Apply fix JR49630 - Adds support for shared inventories for the Extended Sites business model.
-
Fixes and enhancements related to Messaging and Integration:
- Optional: (Messaging and Integration) Apply fix JR46224 - Improves performance for WebSphere Commerce environments that leverage the DOM inventory model.
- Optional: (Messaging and Integration) Apply fix JR49610 - Firing Phase capability is enabled in the WebSphere Commerce and Sterling Configurator integration
- Optional: (Messaging and Integration) Apply fix JR48683 - Add support for the Test Model button when you integrate WebSphere Commerce with Sterling Configurator.
- Optional: (Messaging and Integration) Apply fix JR49090 - Supports the option to set the Visual Modeler skin in the WebSphere Commerce transport setting.
-
Fixes and enhancements related to Marketing and Promotions:
- Optional: (Marketing and Promotions) Apply fix JR50383 - Management Center: Enables the ability to add a web activity to a campaign.
- Optional: (Marketing and Promotions) Apply fix JR47728 - Improves performance of promotion code generation utility on WebSphere Commerce environments with an Oracle database.
- Optional: (Marketing and Promotions) Apply fix JR49477 and JR49896 - Ensures that 'one time use' promotion codes expire after it is used.
-
Fixes and enhancements related to Orders, Payments, and Inventory:
- Optional: (Orders, Payments, and Inventory) Apply fix JR47546 - Enhance DOM inventory performance.
-
Fixes and enhancements related to Data load and other utilities:
- Optional: (Data load and other utilities) Apply fix JR48801 - Can export existing promotions from one machine and import the promotions to a different machine.
- Optional: (Data load and other utilities) Apply fix JR50311 - Enhances Data Load utility to support organization data that contains special characters for the organization name.
-
Fixes and enhancements related to Catalog, Assets, Contracts, and Pricing:
- Optional: (Catalog, Assets, Contracts, and Pricing) Apply fix JR48359 - Supports modification of the preprocess SQL statements that are used in the CatalogHierarachyPreProcessor to customize them in the wc-dataimport-preprocess-parent-catgroup.xml file.
- Optional: (Catalog, Assets, Contracts, and Pricing) Apply fix JR46213 - Allows more than one contract to be passed in and evaluated in the GetCatalogNavigationView service call.
- Optional: (Catalog, Assets, Contracts, and Pricing) Apply fix JR47308 - For Madisons starter stores: Fixes how the ProductViewHandler returns URLs.
- Optional: (Catalog, Assets, Contracts, and Pricing) Apply fix JR47399 - Enables integration between IBM Web Content Manager and IBM WebSphere Commerce.
- Optional: (Catalog, Assets, Contracts, and Pricing) Apply fix JR50830 - Enables the ability to save catalog entry descriptive attribute values for multiple languages in the Management Center.
Optional: Apply interim fix JR46451
wcf:url
tag to construct relative URLs with context path,
complete the following procedure.Procedure
Optional: Apply interim fix JR47563
Procedure
Optional: Apply interim fix JR48121 and JR49050
Procedure
Optional: Apply interim fix JR50286
Procedure
Optional: Apply interim fix JR49419
Procedure
Optional: Apply interim fix JR49587
To disable the entitlement flow, complete the following procedure.
Procedure
Optional: Apply interim fix JR49326 and JR48977
Procedure
Optional: Apply interim fix JR48148
Procedure
Optional: Apply interim fix JR50755.fep and JR50129
- JR50755 includes the ability to specify a custom password file to store encrypted passwords for the utilities
- JR50129 includes performance enhancements to the utilities when run against large catalogs
Procedure
Optional: Apply interim fix JR49109 and JR50878.fep
Procedure
Optional: Apply interim fix JR48954
Procedure
Optional: Apply interim fix JR50873
With this interim fix, when the crawlurl
and
indexurl
are the same, the URL is still crawled. To use
this implementation, you must complete the following procedure:
Procedure
Optional: Apply interim fix JR48101
To enable this behavior, complete the following procedure.
Procedure
Optional: Apply interim fix JR49630
Procedure
Optional: Apply interim fix JR46224
Procedure
Optional: Apply interim fix JR49610
Procedure
Optional: Apply interim fix JR48683
Procedure
Optional: Apply interim fix JR49090
The Sterling Configurator Visual Modeler URL configured in transports should be modified to be http://vm_hostname:VM_port/context_root/en/US/enterpriseMgr/skin
Optional: Apply interim fix JR50383
Procedure
Optional: Apply interim fix JR47728
WC_installdir/schema/database/apar/wcs.schema.px_cdpool_error.sql
Invoke
the following command to run the sql file:sqlplus -S [username]/[password]@[connection-spec]@[wc-install-dir]/schema/oracle/apar/wcs.schema.px_cdpool_error.sql;
quit;
- [username] refers to the username authorized to create objects on the appropriate schema
- [password] refers to the password for [username] required to connect
- [connection-spec] refers to the SID or TNS service-name or expanded service-name of the WebSphere Commerce Oracle instance
- If the schema associated with tables in the database is not the default
([username]) in most cases, you might need to invoke a schema change.
For example, to change the schema name:
- If database back end is Oracle, issue this statement before line
2:
alter session set current_schema=[schemname]
- Here,
[schemaname]
refers to the schema associated with tables in the WebSphere Commerce database
- If database back end is Oracle, issue this statement before line
2:
Optional: Apply interim fix JR49477 and JR49896
To use the new Unique Promotion Code validation task command, complete the following procedure:
Procedure
Optional: Apply interim fix JR47546
Procedure
Optional: Apply interim fix JR48801
Procedure
- wc-dataextract.xml
- wc-dataextract-env.xml
- wc-extract-xml-promotion.xml
- wc-dataload.xml
- wc-dataload-env.xml
- wc-loader-xml-promotion.xml
- promotion.xml
Optional: Apply interim fix JR50311
Procedure
Optional: Apply interim fix JR48359
Procedure
Optional: Apply interim fix JR46213
OR
evaluation of contract product-set
exclusion to AND
the product sets together. To use this new
functionality, complete the following procedure: Procedure
Optional: Apply interim fix JR47308
- src/businessModels/internal/sar/MadisonsV2/StoreAssetsDir/ShoppingArea/CheckoutSection/MultipleShipment/MSOrderItemDetailSummary.jsp
- src/businessModels/internal/sar/MadisonsV2/StoreAssetsDir/ShoppingArea/CheckoutSection/MultipleShipment/MSOrderItemDetails.jsp
- src/businessModels/internal/sar/MadisonsV2/StoreAssetsDir/ShoppingArea/CheckoutSection/SingleShipment/OrderItemDetailSummary.jsp
- src/businessModels/internal/sar/MadisonsV2/StoreAssetsDir/ShoppingArea/CheckoutSection/SingleShipment/OrderItemDetails.jsp
- src/businessModels/internal/sar/MadisonsV2/StoreAssetsDir/ShoppingArea/DiscountSection/DiscountDetailsDisplay.jsp
- src/businessModels/internal/sar/MadisonsV2/StoreAssetsDir/Snippets/Order/Cart/OrderItemDetail.jsp
- src/businessModels/internal/sar/MadisonsV2/StoreAssetsDir/Widgets/CatalogEntry/CatalogEntryDisplay_Data.jspf
- src/businessModels/internal/sar/MadisonsV2/StoreAssetsDir/Widgets/ProductDescription/ProductDescription_Data.jspf
- src/businessModels/internal/sar/MadisonsV2/StoreAssetsDir/Widgets/ProductFullImage/ProductFullImage_Data.jspf
- src/businessModels/internal/sar/MadisonsV2/StoreAssetsDir/Widgets/Shared/GetCatalogEntryDetailsByID.jsp
Optional: Apply interim fix JR47399
To complete the integration between WebSphere Commerce and an external content management system, complete the following procedure.
Procedure
Optional: Apply interim fix JR50830
Procedure
3. 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).
-
Fixes and enhancements related to Orders, Payments, and Inventory:
- Optional: Enabling interim fix JR47545 - Enable this fix if you want to enhance DOM inventory performance.
-
Fixes and enhancements related to Member and Session Management:
- Optional: Enabling interim fix JR45670 - Enable this fix if you want to allow simultaneous logon across multiple channels and browsers.
-
Fixes and enhancements related to Marketing and Promotions:
- Optional: Enabling interim fixes JR41022 and JR46449 - Enable this fix if you want to allow dialog activities to be able to send emails that contain order details of a previous order.
- Optional: Enabling interim fix JR50747 - Enable this fix to add support for invalidation policies in the cachespec.xml file to invalidate base cache JSP pages when a new e-Marketing Spot is created.
- Optional: Enabling interim fix JR48904 - Enable this fix if you want to improve the performance of catalog entry entitlement checks during e-Marketing Spot recommendations.
-
Fixes and enhancements related to Authoring and Staging:
- Optional: Enabling interim fix JR47235 - Enable this fix to avoid database connection timeouts when the stagingprop utility is run.
- Optional: Enabling interim fix JR49401 - Enable this fix to rectify an issue where records in the CATGRPTPC table cannot be updated by using the stagingprop utility.
5.4. 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.
65. List of fixes
JR53048.fp provides a set of interim fixes for WebSphere Commerce V7 Fix Pack 7. All interim fixes for Fix Pack 7 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 6. All interim fixes for Feature Pack 6 that are created after the release of JR53048.fep require JR53048.fep as a prerequisite. The following fixes are included in this cumulative interim fix JR53048.fepJR53048.fp:
JR53048.fp provides a set of interim fixes for WebSphere Commerce V7 Fix Pack 7. All interim fixes for Fix Pack 7 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 6. All interim fixes for Feature Pack 6 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 7Cumulative interim fixes for Feature Pack 6.