Migration limitations
While you plan your migration project, be aware of the migration limitations.
Operating system and software support
The supported operating systems and software for the development and production environments have changed in version 9.0. For more information about supported software, see Supported software levels, fixes, and settings for HCL Commerce.
Migrated store runs on Transaction server
Version 9.0 uses containerization to deliver a continuous development and delivery cycle. Part of that containerization was moving the Store server to a separate container. Migrated stores cannot be deployed to the Store server. Migrated stores must run on the Transaction server. For more information about migrated your store, see Migrating the store dynamic web project.
Enterprise Java Beans
Enterprise Java Beans are unsupported in version 9.0. You must migrate your EJB beans to Java Persistence API (JPA).
For more information on migrating to JPA, see Migrating IBM Websphere Commerce Version 8 EJB entity beans to Java Persistence API.
HCL Cache
The HCL Cache extends the capabilities and performance of DynaCache by adding remote centralized caching with Redis, and improved operational and monitoring support.
With HCL Commerce Version 9.1, all provided default caches are configured by default to use the HCL Cache provider. By being deployed as a DynaCache Cache provider, the HCL Cache is enabled for DynaCache caches and used through standard DynaCache interfaces, including Servlet Caching (cachespec.xml), command caching, and DynaCache distributed maps.
For more information on HCL Cache, see HCL Cache.
Local Store Preview
In HCL Commerce Version 9.1.3.0 and later, the Store preview feature is supported for Struts 2 migrated local stores, in non-workspace context environments only.
For more information on enabling the Store Preview feature in your migrated local store environment, see step 4.c of Migrating REST-based Search.