Generic Service Settings

Caching

System level configurations to set up retention times and the behavior of the service's cache.

Table 1. payment-service.properties
Name Data Type, Range Description Default
caching.cachingEnabled Boolean Enables caching for the Self Scanning Service true
caching.mbeansEnabled Boolean If JMX MBeans should be registered (which allows cache clearing and access to cache statistics) false
caching.statisticsEnabled Boolean If statistics should be recorded and made available over JMX (recording involves a performance penalty) false
caching.cache Individual cache configs (per tenant)

Add caching.cache.<cacheName>.<configName> to the properties

  • cacheName - target cache name used in the application
  • configName - specific config
  • expiration - cache item expiration after write, time value (e.g. 1d, 4h, 90m...), required
  • capacity - how many items can be cached
BusinessUnit.expiration String Cache BusinessUnit; used for every payment and finalization. 4h
BusinessUnit.capacity Integer Cache BusinessUnit; used for every payment and finalization. 10000
LoyaltyProgram.expiration String Cache LoyaltyProgram; used for points payment 4h
LoyaltyProgram.capacity Integer Cache LoyaltyProgram; used for points payment 10000
Tender.expiration String Cache Tender; used to create payment positions 4h
Tender.capacity Integer Cache Tender; used to create payment positions 10000
TenderTypeCode.expiration String Cache TenderTypeCode; used to create payment positions 4h
TenderTypeCode.capacity Integer Cache TenderTypeCode; used to create payment positions 10000