IBM WebSphere Commerce WCH Dataload

Enhanced business object based loading utility

  1. Home >
  2. IBM WebSphere Commerce WCH Dataload >

Our Solution

A custom dataload script that helps to map images between Watson Commerce and Watson Content Hub. It is invoked during product dataload in Commerce.

IBM Watson Commerce has specific requirements which need to be filled to work with Watson Content Hub e.g. product Image, Content Type etc. With our solution, you just need to provide the URLs of your images and it will upload your content.

Commerce Challenges

Websphere Commerce has challenges when it comes to uploading product images to Watson Content Hub. Our solution can help to overcome this issue.  It is basically a dalaload script which gets invoked during product dataload in Commerce. We need external content ID for each product for Watson content hub image for mapping.

Performance Tuning
Following flow explains the implementation
  • Get Image binary from external URL’s for both thumbnail and full image
  • Resource creation from binary ->get resource id -> wch REST API call to create resource O/P of service RESOURCE ID
  • Asset creation from the resource -> wch REST API to create asset O/P of service ASSET ID 1
  • Resource creation from binary ->get resource id -> wch REST API call to create resource O/P of service RESOURCE ID
  • Asset creation from the resource -> wch REST API to create asset O/P of service ASSET ID 2
  • Create content with newly created assets (asset id1 and asset id2) -> o/p of service content id -> this content id is wrote back to a file for mapping purpose
  • Publish the newly created content. REST call to publish new content.
  • Java flow starts with function : uploadImages()
API CALLS

  • LOGIN
  • CREATE RESOURCE
  • CREATE ASSET
  • CREATE RESOURCE
  • CREATE ASSET
  • CREATE CONTENT
  • PUBLISH CONTENT
Solution’s Functions

  • Get Image binary from external URL’s for both thumbnail and full image
  • Resource creation from binary ->get resource id -> wch REST API call to create resource O/P of service RESOURCE ID
  • Asset creation from the resource -> wch REST API to create asset O/P of service ASSET ID 1
  • Resource creation from binary ->get resource id -> wch REST API call to create resource O/P of service RESOURCE ID
  • Asset creation from the resource -> wch REST API to create asset O/P of service ASSET ID 2
  • Create content with newly created assets (asset id1 and asset id2) -> o/p of service content id -> this content id is wrote back to a file for mapping purpose
  • Publish the newly created content. REST call to publish new content.
Competitive Advantage

  • No manual uploading images for WCS
Top 5 industry targets

  • Retailers
  • Wholesalers
  • Any B2B or B2C
  • Any company that deals in huge content/images
Business Opportunities

  • If any company wants to use empty WCH from scratch with Watson Commerce, this solution can help to build its own databank.
Business Problem

  • It solves the gap between WCS and WCH Products mapping.
Return on Investment

  • It saves time and gives a competitive advantage by providing a reliable solution for uploading images.
Operating System

  • Compatible with all OS with which Watson Commerce works such Windows, UNIX etc.
Multiple Selections

  • Digital media
Hardware Platforms

  • Works with all hardware platforms with which Watson Commerce works.