Many SAP Commerce projects are still using regular storefront approach, often incorporating modern frameworks like Vue.js and using default SAP Commerce build. Implementing parallel execution of FE and BE builds can lead to significant reductions in overall build time. Even for projects utilizing the OOTB Grunt build, parallelization can result in significant time savings. Furthermore, parallelization provides the valuable advantage of decoupling FE and BE builds, enabling developers to skip FE builds when focusing on BE development.
In some SAP Commerce setups, there is an unusual problem where web unit tests occasionally fail when run with a suppressed tenant. These tests encounter random failures while creating mock classes, resulting in exceptions like java.lang.NoClassDefFoundError: Could not initialize class org.mockito.codegen.
With Solr 8’s support ending in June 2024, it’s crucial for local environments to transition to Solr 9. Unlike cloud installations of SAP Commerce (where you can easily switch Solr versions via manifest.json), local setups encounter difficulties in switching between Solr versions.
There are cases, when it is required to use same solr index to index/search different itemtypes. For example, it is required to have in search box autocompletion different types, like Product and Media. Another common use case would be display on search result page search results of different itemtypes mixed together (for example, Product, Media, custom Resource itemtype).
Changing log level and properties from HAC is often used by developers for various support things. Unfortunately on SAP Commerce Cloud (CCv2) there is no more such possibility, as HAC is not available on storefront nodes.
Patching Framework is a Hybris OOTB framework, which is designed to simplify releasing of new code on production (for example automation of impex execution after new code deployment). Hybris provides a set of interfaces and abstract classes, which allows to write “Patches”, where Patch itself is a Java class that is executed during a system initialization or an update.
In article SameSite cookie issue in Hybris is described, how to fix issue with SameSite cookie attribute. But, unfortunately, it is not working with enabled session persistence.
Solr hot update indexing always uses current session user, for example current backoffice user, who triggered solr hot reindex. In lots of real world cases it would lead to wrong results in solr due to different flexible search restrictions, which are applied to backoffice user and solr indexing user.
It is a common case to execute requests to third-party systems on Hybris model change. For that purpose perfectly fits Hybris Interceptors, but execution of long-running operations inside interceptors can lead to great performance degradations and data lost. To deal with that, operations should be executed asynchronously in separate thread.
During migration on newer version of hybris you could find that Backoffice is not working due to failed context initialization with error in creating 'backofficeWarmUpTypeFacadeCaches' bean. Root cause of that issue is broken itemtype definition in composedtypes table.