Migrating to HCL Commerce Version 9.1 solutions

The following section presents the high-level concepts and steps that you must understand and complete in order to upgrade from earlier WebSphere Commerce technologies to those introduced in HCL Commerce Version 9.1.

Migrating from WebSphere Commerce solutions to those that were introduced in the latest release of HCL Commerce can provide a variety of improvements to site functionality and performance. However, full coverage of base functionality, or extendability is not guaranteed. Review the following section in order to ensure that your solution migration suits your business requirements. Future updates to these solutions will broaden the features available.

In addition to the consideration of functionality parity, any customizations that were previously made to your solution must be re-architected to conform with the conceptual and technical paradigms introduced with the new solutions. Therefore, it can be assumed that such a solution migration will require a higher degree of technical planning, aptitude, and time commitment than a simple version migration.

New solutions offered in HCL Commerce Version 9.1

There are two new solutions that were introduced in HCL Commerce Version 9.1:
  • React-based reference stores.

    The React-based store solutions are single page applications that utilize REST calls to interact with HCL Commerce services. They leverage the new Elasticsearch-based search solution exclusively.

    For more information, see Reference React stores.

  • The Nextjs (Ruby) store.

    The Next.js store offers customizable features for storefronts using the Next.js framework. It uses the same data template as the ReactJS stores and supports business-to-consumer (B2C) and business-to-business (B2B) use cases.

    For more information, see Next.js starter store.

  • The Elasticsearch-based search solution.

    Review Migrating from the Solr-based to the Elasticsearch-based search solution to understand the conceptual differences between the two search solutions, and the considerations that you must make when adopting the Elasticsearch-based search solution.