11. Commerce Cache Configuration

The CoreMedia system uses caching to provide a faster access to various eCommerce entities (that is, products, categories, etc.). These entities will automatically be cached when used by the CoreMedia system. Unified API cache keys are used for caching the commerce entities.

Cache configuration if Commerce Hub is used

The caching of commerce entities is implemented on different layers in the Commerce Hub infrastructure:

For each entity a default capacity and cache time is configured in Spring. Each of the default values can be adapted to the needs of your system environment by overwriting the corresponding properties. There is a reasonable default configuration for the commerce cache which can be customized to meet your project requirements.

Refer the Chapter 14, Commerce Adapter Properties if you want to adjust the cache configuration for your Commerce Adapter

In order to adjust the cache configuration for Studio and Content Application Engine you can use the following properties (see Section 4.6, “Commerce Hub Properties” in Deployment Manual for details) for cache capacities and cache timeouts respectively:

Figure 11.1.  Actuator URLs in overview page

You have to replace the trailing "*" with the configuration key of the concrete cache key. You can find the keys and the default values using the Actuator URLs from the default overview page (https://overview.docker.localhost) in the default Blueprint Docker deployment. Click the Config link and search for the cache.capacities.ecommerce or cache.timeout-seconds.ecommerce prefix.

Figure 11.2.  Actuator results for cache.timeout-seconds.ecommerce properties

Cache configuration if HCL Commerce Extension is used

See a list of available cache entry classes in the commerce-cache-defaults.properties file or consult the Spring Boot environment actuator of the app using the commerce cache.