
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
- Open the Administration Console.
- Select Site on the Administration Console Site/Store Selection page.
-
Click
.The Transport Configuration page displays.
-
Click Add.
The Add Transport page displays.
-
Select the Watson Content Hub Integration transport method and click
Add.
The Watson Content Hub transport is added and placed in active state.
-
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.
-
Enter the values to be used by the transport method:
Parameter Value 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: - In the Watson Content Hub header, expand the menu by clicking your user name.
- Click Hub information.
- 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. - Click OK to accept the changes, or click Cancel to return to the Transport Configuration page.
-
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
Update the STORECONF table to include your tenant ID to ensure that Watson Content Hub is reachable.
-
Update the STORECONF table to include your Watson Content Hub host name to
ensure that Watson Content Hub is reachable at the correct address.
-
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.
- Restart the WebSphere Commerce search server.