Migrate your Watson Content Hub integration

If you integrated Watson Content Hub with the WebSphere Commerce Version 8 runtime environment, we can migrate this integration to WebSphere Commerce Version 9.

Note: If you integrated Watson Content Hub with the WebSphere Commerce Version 8 development environment, see Migrating your Watson Content Hub integration for WebSphere Commerce Version 8 Developer.


Before beginning

  1. Migrate our custom assets.

  2. Migrate the site security.

  3. Migrate your offline database.


Task info

The following steps are to be performed on the offline database that you migrated earlier. The offline database is not serving traffic, which is why it is considered offline. By migrating this integration on your offline database, we can perform the necessary testing before your migrate this integration on your online, live database.


Procedure

  1. Update the STORECONF table to include your Watson Content Hub host name.

    1. Go to Watson Content Hub.

      • https://www.digitalexperience.ibm.com

    2. Log on to Watson Content Hub by using your IBMid.

    3. In the Watson Content Hub header, expand the menu by clicking your user name.

    4. Click Hub information.

    5. Note the value and format of the host name. For example: https://myX.digitalexperience.ibm.com.

    6. Open a database command prompt and connect to the database.

    7. Run the following SQL and use the host name that you just acquired. 

        update storeconf set value='https://myX.digitalexperience.ibm.com' where name='wc.externalContent.hostName';

      Where X is a number value associated with your host name. For example, https://my1.digitalexperience.ibm.com.

  2. Restart the WebSphere Commerce server.

  3. Restart the search server.

  4. Enable SSL for Watson Content Hub integration.


What to do next

If you migrated the Watson Content Hub integration to your offline database and performed all necessary testing, we can proceed with migrating your live database. After the live database is migrated, we can repeat these steps on the live database.