Migration of commerce cache configuration

The former commerce cache configuration for in the vendor specific commerce extension needs to be migrated to the new cache configuration used for commerce hub. There are two in memory caching layer. The commerce adapter iteself comes with a default cache configuration to reduce the load on the connected commerce systems. The configuration is described in the Commerce Adapder documentation. The commerce api which communicates via gRPC with the Commerce Adapter comes also with its own caching layer. You should adapt existing cache sizes and timeouts to the new commerce hub property keys. See com.coremedia.blueprint.base.livecontext.client.config.CommerceAdapterClientConfigurationProperties.CacheConfiguration for details. The default configuration can be found in com.coremedia.blueprint.base.livecontext.client.cache.CachingDataClientFactory. If you want to customize the defaults you can use the following property pattern: commerce.hub.capacities.* commerce.hub.timeoutSeconds.*

Follow Section, “Migration of commerce cache configuration” for upgrade information.

(CMS-14940)