WebSphere Commerce EnterpriseFeature Pack 5 or later

Migrating a store to use catalog entry description overrides

If your extended site store is published on a previous Feature Pack level of WebSphere Commerce, you must migrate your store before you can set descriptions overrides. After you configure your extended site store, you can then load description overrides by using the Data Load utility or the Management Center Catalog Upload feature.

Feature Pack 6 or laterYou can also use the Management Center Catalogs tool to set store specific descriptions to override inherited catalog entry descriptions in your storefront.

Note: If your store is created after WebSphere Commerce Feature Pack 5 is installed, your store is already enabled to use description overrides.

Before you begin

  • Catalog entry description overrides are only supported for the Aurora starter store extended sites store model. Your store must be based on this store model to use description overrides.
  • Ensure that your extended site store uses WebSphere Commerce search and the catalog storefront SOA web services.

    If your store does not use WebSphere Commerce search and the catalog storefront SOA Web services, follow the instructions in the topic Samples: Catalog storefront services to upgrade your store.

  • If your store uses WebSphere Commerce search, upgrade your WebSphere Commerce search to the Feature Pack 5 level with the search index setup migration utility. For more information about migrating with the search index setup migration utility, see Migrating WebSphere Commerce search

About this task

Description overrides provide your store with the capability to set store-specific storefront descriptions for catalog entries that are inherited from your asset store. When you set a description override, the inherited description no longer displays on your storefront. Your description override displays to shoppers on your storefront for the catalog entry.


  1. Determine the internal unique identifier and the member internal unique identifier for your store by running the following SQL statement:
    Where: YourStoreIdentifier is the external identifier of the store.
  2. Add records to the CATOVRGRP and STORECATOVRGRP database tables. You must add records to these tables to create the association between your description overrides and your store catalog entries. Use the following example SQL statements as a guide.
    store_member_id, identifier, store_id)
    INSERT INTO STORECATOVRGRP (STOREENT_ID, CATOVRGRP_ID, SEQUENCE) VALUES (store_id, catalog_override_group_unique_id,  0)
    The store internal unique identifier that you found in the previous step.
    The member internal unique identifier that you found in previous step.
    The unique internal identifier that is assigned to the catalog override group. To find the unique ID, run the following SQL statement:
    SELECT COUNTER FROM KEYS WHERE tablename='catovrgrp'
    Set the counter in the KEYS table so that WebSphere Commerce uses a primary key value greater than the value used in the manual insert. Run the following SQL statement:
    UPDATE KEYS SET COUNTER=key_value WHERE tablename='catovrgrp'
    The catalog_override_group_unique_id you used to create the override group plus 1.
  3. Build the WebSphere Commerce search index. For more information about building this index, see building the WebSphere Commerce search index.
  4. Restart the WebSphere Commerce server.

What to do next

  • You can enable support for searching in store preview within a workspace. By default, support is not provided for searching your store in store preview with override description information when a business user is working in a workspace. To enable searching in store preview with override information when you are working in a workspace, you must download and install an interim fix. For more information, see APAR JR43778, and APAR JR44287.

    Feature Pack 6 or laterWorkspaces support for searching for catalog entries in store preview with description override information is provided by default.

  • With your store migration to enable loading catalog entry description overrides complete, you can set description overrides: