(Enterprise)

Sample: Loading catalog entry description override data

This sample demonstrates how to load catalog entry description override data to your extended sites store.

By loading catalog entry description overrides with the Data Load utility or Catalog Upload feature, we can override the catalog entry descriptions that are inherited from our asset store. By overriding these inherited catalog entry descriptions, we can create store specific catalog entry descriptions to display on the storefront.


About this sample

The data load mediator in this sample loads catalog entry override data into the extended site store catalog. The sample that we are loading in this procedure overrides the description for two shared catalog entries in the catalog asset store. The sample is included in a new directory:

If you need to update the catalog entry description overrides, we can change the content of your input file and run the sample again.

Note: Both the extended sites store and the catalog asset store must be published. The following is the override for the first catalog entry with part number ‘AuroraWMDRS-11’:

Column name Extended site store override value
Name White Flower Sundress
ShortDescription Celebrate life with this white flower sundress
Thumbnail images/catalog/apparel/women/womens_dresses_160x160/WD_031_a_red.jpg
FullImage images/catalog/apparel/women/womens_dresses_1000x1000/WD_031_a_red.jpg

The following is the override for the second catalog entry with part number ‘AuroraWMDRS-6’:

Column name Extended site store override value
Name Strapless Cocktail Dress
ShortDescription Luigi Valenti red cocktail dress with appliqued roses and tassels at the hem
Thumbnail images/catalog/apparel/women/womens_dresses_70x70/WD_006_a_red.jpg
FullImage images/catalog/apparel/women/womens_dresses_1000x1000/WD_006_a_red.jpg


Procedure

  1. Before you run this sample, ensure that you publish the AuroraEsite store which uses the WebSphere Commerce Search.

  2. Open the wc-dataload-env.xml configuration file in the appropriate directory:

  3. Update the file with the database settings, catalog asset store identifier, and catalog identifier

  4. (Developer) On a command line, go to the WCDE_installdir\bin directory.

  5. (Linux) Open a command line in the Utility server Docker container. Change the directory to utilities_root/bin directory.
    For information about entering and leaving containers, see Running utilities from the Utility server Docker container.

  6. Enter the following command:

    • (Linux) ./dataload.sh ../samples/DataLoad/Catalog/ESiteOverride/wc-dataload.xml -Dinstance=instance_name

    • (Developer) dataload ..\samples\DataLoad\Catalog\ESiteOverride\wc-dataload.xml -Dinstance=instance_name


Verifying results

The wc-dataload.xml configuration file calls the wc-catalog-entry-description-override-loader.xml configuration file to load the description override from the CatEntryDescriptionOverride.csv source file. Verify that the data is loaded into the database by running the following SQL statements:

These SQL statements return details about the description override of those two catalog entries. We can also verify the load by viewing the catalog entry in the storefront.

Note: If you do not see the changes in the store front, try the following steps

  1. Clear the browser cache.

  2. If you have DynaCache turned on, clear the cache that is created by DynaCache.

  3. Rebuild our search index.

We can also verify that your description override information displays in Management Center and in the storefront. In the Management Center Catalogs tool, open the properties view for the catalog entry to verify the override information. We can further change your override information in this properties view.

We can preview your loaded information and any changes in the storefront by launching store preview in Management Center. For more information about using the Management Center to change and preview your description overrides, see Adding catalog entry description overrides


Cleaning up the data

To remove the data loaded in this sample from the database, run the Cleanup.sql file in the /samples/DataLoad/Catalog/ESiteOverride directory.