Migrating a store to use catalog entry description overrides

If your extended site store is published on a previous 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.

You can also use the Management Center Catalogs tool to set store specific descriptions to override inherited catalog entry descriptions in your storefront.

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.

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.

Procedure

Determine the internal unique identifier and the member internal unique identifier for your store by running the following SQL statement:
```
SELECT STOREENT_ID, MEMBER_ID FROM STOREENT WHERE IDENTIFIER='YourStoreIdentifier'
```
where: YourStoreIdentifier is the external identifier of the store.
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.
```
INSERT INTO CATOVRGRP (CATOVRGRP_ID, MEMBER_ID, IDENTIFIER, STOREENT_ID) VALUES (catalog_override_group_unique_id, 
store_member_id, identifier, store_id)

INSERT INTO STORECATOVRGRP (STOREENT_ID, CATOVRGRP_ID, SEQUENCE) VALUES (store_id, catalog_override_group_unique_id,  0)
```
where:
store_id

The store internal unique identifier that you found in the previous step.

store_member_id

The member internal unique identifier that you found in previous step.

catalog_override_group_unique_id
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'
where:

key_value

The catalog_override_group_unique_id you used to create the override group plus 1.
Build the WebSphere Commerce search index. For more information about building this index, see building the WebSphere Commerce search index.
Restart the WebSphere Commerce server.

What to do next

Workspaces 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:
- For more information about using Catalog Upload to load description overrides, see Adding catalog entry overrides with Catalog Upload
- For more information about loading description overrides with the Data Load utility, see Sample: Loading catalog entry description override data
- For more information about setting description overrides with the Catalogs tool, see Adding catalog entry description overrides