WebSphere Commerce Version 8.0.4.0

Configuring the Watson Content Hub transport method

Configure the Watson Content Hub Integration transport in the WebSphere Commerce Administration Console so that messages can be sent between WebSphere Commerce and Watson Content Hub.

Procedure

  1. Open the Administration Console.
  2. Select Site on the Administration Console Site/Store Selection page.
  3. Click Configuration > Transports.
    The Transport Configuration page displays.
  4. Click Add.
    The Add Transport page displays.
  5. Select the Watson Content Hub Integration transport method and click Add.
    The Watson Content Hub transport is added and placed in active state.
  6. Configure the Watson Content Hub transport method. Select the check box beside the Watson Content Hub Integration transport method and click Configure.
    The Transport Configuration Parameters dialog opens.
  7. Enter the values to be used by the transport method:
    ParameterValue
    Password Your IBMid password that you use to log in to Watson Content Hub.
    Tenant ID Your Watson Content Hub tenant ID. To view your tenant information:
    1. In the Watson Content Hub header, expand the menu by clicking your user name.
    2. Click Hub information.
    3. Note the value of Content hub ID. This is your tenant ID.
    User Name Your IBMid user name that you use to log in to Watson Content Hub.
  8. Click OK to accept the changes, or click Cancel to return to the Transport Configuration page.
  9. Disable URL redirect filtering so that Watson Content Hub can be properly accessed.
    Disable URL redirect filtering for the following web modules:
    • LobTools
    • Store
    • Preview
    For more information about which web modules enable URL redirect filtering, see Enabling URL redirect filtering.
  10. Oracle Update the STORECONF table to include your tenant ID to ensure that Watson Content Hub is reachable.
    1. Run the following SQL statement:
      
      update storeconf set value='TenantID' where name = 'wc.externalContent.tenant-id';
      
      Where TenantID is the Tenant ID value you entered in the transport method configuration parameters in the preceding steps.
  11. Update the STORECONF table to include your Watson Content Hub host name to ensure that Watson Content Hub is reachable at the correct address.
    1. In the Watson Content Hub header, expand the menu by clicking your user name.
    2. Click Hub information.
    3. Note the value of Hostname.
      The value will be in the following format:
      https://myX.digitalexperience.ibm.com
      Where X is a number value associated with your host name. For example, https://my1.digitalexperience.ibm.com.
    4. Run the following SQL statement, using the hostname value obtained in the preceding step:
      
      update storeconf set value='https://myX.digitalexperience.ibm.com/api/' where name='wc.externalContent.authContextRoot';
      update storeconf set value='https://myX.digitalexperience.ibm.com/api/' where name='wc.externalContent.authUriContextRoot';
      update storeconf set value='https://myX.digitalexperience.ibm.com/api/' where name='wc.externalContent.prodUriContextRoot';
      
  12. 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.

  13. Restart the WebSphere Commerce server.
  14. Restart the WebSphere Commerce search server.