Case Studies
AEM INTEGRATION WITH WCS (IBM WebSphere Commerce)
Background / Task
Our Client, a leading shoe and apparel manufacturer, for their online store were using AEM 6.x, WCS, Fluid, Scene 7, Cloud Front. Our task was to remove Fluid functionality completely from the existing system and to use AEM / WCS for all the functionality achieved through Fluid.
Solution
In existing system, WCS was used to store all the product recipes, manages all the user-related activities and e-commerce activities. Existing system was using Fluid for storing default product recipes, swatches and product details. For removing this Fluid from the existing architecture, we have done the following task -
- We have customized AEM coral UI to provide an admin dashboard. i.e. In the Home screen of AEM. Client was having a different section for his requirement and has his own navigation structure.
- This UI contains multiple navigation tabs where the author can perform different activities.
- Author can create new swatches.
- List existing Swatches.
- Sort these swatches. An author can see these swatches in all 3 supported view (column, list, and cart).
- A swatch can be anything it can be a pattern, solid designs, different types of materials, and different color options. Once a new swatch is created it goes for approval from another admin author and once approved this swatch becomes available for creating recipes.
- This custom UI supports all the functionality like multi-select, properties, and all the available features.
- Once a new swatch has been added another author starts creating different recipes against a new or existing product using a unique Id, for understanding - A recipe is a unique product that an end customer can directly buy.
- Once new recipes are ready for the end customer and approved by the admins, author triggers a workflow to send newly added recipes to WCS against a defined product with a unique id.
- Once new recipes become added to an existing product or added new product recipes, we have also added a custom transport handler that was responsible for removing the cache from cloud front CDN for that product.
- This UI supports all the recipes activation, deactivation, and delete of new recipes.
It is a small introduction of the actual implementation this solution was also maintaining all the newly created recipes from the end customer that can be a logged-in user or an anonymous user. These recipes also need to be visible based on user login behavior. We have added workflows for achieving this functionality and transport handler for clearing cache from the CDN.
