Platform Framework
R24 AMR | Min(s) read

TAFJ Caching Properties

The caching properties are loaded from the database by default, although it is possible to use a caching properties file. This section shows the configurations that are made in the caching.properties file.

In the $TAFJ_HOME/conf/cache directory, there is a caching.properties file, which handles the caching properties. This file is separated from the tafj.properties file so that the TAFJCaching.jar file can be used as a separate component independent of TAFJ. Alternatively, the caching properties can be loaded from the database.

The property below allows you to switch a caching provider. Temenos local cache implementation is the default caching provider.

temn.cache.external.caching.provider= com.temenos.tafj.cache.TAFJLocalCacheFactory

The table below shows a list of supported providers that can be configured in the cache.properties file.

Default provider for external caching services is Oracle Coherence. For more information on setting up different providers, see $TAFJ_HOME/doc/TAFJCache.pdf.

External caching provider Configuration

Coherence

temn.cache.external.caching.provider= com.tangosol.coherence.jcache.CoherenceBasedCachingProvider

JBoss

temn.cache.external.caching.provider= org.infinispan.jcache.embedded.JCachingProvider

WebSphere

temn.cache.external.caching.provider= com.ibm.websphere.ObjectGridProvider

Temenos (local cache only across one JVM)

temn.cache.external.caching.provider= com.temenos.tafj.cache.TAFJLocalCacheFactory

Apache Ignite

temn.cache.external.caching.provider= org.apache.ignite.IgniteProvider

TAFJ properties overrides the caching provider configuration, if specified in the tafj.properties file.

If you use an API, the caching provider configuration can be passed as a CacheParameter, which takes ultimate precedence.

In this topic

Copyright © 2020- Temenos Headquarters SA

Published on :
Monday, May 27, 2024 5:03:05 PM IST