Considerations for moving from Sterling Configurator to Omni-Configurator

WebSphere Commerce Version 9 supports the integration with Omni-Configurator: a brand new implementation to Sterling Configurator. If you integrated with the traditional Sterling Configurator on previous versions and have migrated to version 9.0, you need to move to the Omni-Configurator integration. Below is a summary and some tips to assist with your move to Omni-Configurator.

  1. Since Sterling Omni-Configurator is considered a brand new implementation to the Sterling Configurator application, there is no migration from Sterling Configurator to Omni-Configurator. If we are using WebSphere Commerce Version 9, we must install Omni-Configurator and configure the integration by following the enablement documentation. For more information about enabling this integration, see Enable Sterling Omni-Configurator integration with WebSphere Commerce.

  2. After integrating, move your existing models to new the Omni-Configurator environment. For assistance with this process, please contact the Sterling CPQ support team.

  3. By default, WebSphere Commerce stores render the Configurator page by using Omni-Configurator widget instead of an iFrame, which is a responsive and reusable widget. If we are using a custom store, we can configure the store widget to render the Configurator page by following the customization guide. For more information on this guide, see Updating the storefront to sell dynamic kits with the Omni-Configurator widget.

  4. If you have any customizations on the Configurator page, for example, styling, we can reference the customization guide to ensure the customization is properly configured, before deploying the asset. For more information on this guide, see Updating the storefront to sell dynamic kits with the Omni-Configurator widget.

  5. Under the integration with Omni-Configurator, WCCatalogAdapter and WCPricingAdapter are the adapters for the Configurator, which call WCS REST to perform entitlement checks and query prices. WebSphere Commerce Version 9 does not rely on the Sterling user exit framework. If you have any customizations based on the UE framework, investigate whether similar customizations are needed for our integration with Onni-Configurator.

  6. If we are using a B2B store model, we must install WebSphere Commerce 9.0.0.7 (or higher).