Migrate a previously published store to use Watson Content Hub
If the catalog asset store is published on a previous level of WebSphere Commerce, migrate the catalog asset store so that the catalog asset store has a catalog override group. Doing so enables you to use the Management Center Catalogs tool to assign external content to a WebSphere Commerce business object, such as a catalog group or product, when using Watson Content Hub.
Procedure
- Determine the internal unique identifier and the member internal unique identifier for our 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 catalog asset store.
- Add records to the CATOVRGRP and STORECATOVRGRP database tables. For example.
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) VALUES (store_id, catalog_override_group_unique_id)Where:
- store_id
- The store internal unique identifier found in the previous step.
- store_member_id
- The member internal unique identifier found in previous step.
- catalog_override_group_unique_id
- The unique internal identifier assigned to the catalog override group. To find the unique ID, run...
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 used to create the override group plus 1.
For example:
INSERT INTO CATOVRGRP (CATOVRGRP_ID, MEMBER_ID, IDENTIFIER, STOREENT_ID) VALUES (10003, 7000000000000000101, 'Extended Sites Catalog Asset Store', 10051) INSERT INTO STORECATOVRGRP (STOREENT_ID, CATOVRGRP_ID) VALUES (10051, 10003)
- Complete the following task to ensure that WebSphere Commerce search correctly applies updates: Additional steps for WebSphere Commerce search interim fixes: Setting up the search index
This WebSphere Commerce search task involves setting up the search index using the following actions: configWCforSolrUpdate, and configSolrCoresUpdate. Then, preprocessing and building the search index.
- Restart the WebSphere Commerce server.