Configuring TAFJ Properties

This section describes the configurations that you need to make in the tafj.properties file to enable the various TAFJ caching mechanisms.

You can configure the TAFJ properties using the following procedure.

1. To enable external caching, set the following property:

   temn.tafj.runtime.use.external.caching = true

2. To enable batch write caching, set the following property:

   temn.cache.runtime.use.batch.write=true

   For more information, see Batch caching.

3. To enable dictionary caching, set the following property:

   temn.tafj.runtime.use.cache.dict.item=true

   For more information, see Dictionary caching.

Batch caching

This caching technique caches records of the application until either a TRANSEND (batch committed), TRANSABORT (batch rolled back) or the batch size defined is reached (batch submitted but not committed).

• If the cache status is TRANSEND, then the cached records are flushed to the database and committed.
• If the cache status is TRANSABORT, then the cached records are rolled back.
• The batch size is defined at the thread level. For more information, see Batch Caching.

The batch write caching technique is independent of external caching. Hence, there is no need to enable the temn.tafj.runtime.use.external.caching property in the tafj.properties file.

For more information on working of batch caching, see Enabling Batch Caching.

Dictionary caching

Dictionary caching is currently relegated to the TAFJ local caching mechanism as the Object is a complex object and not a String. The local caching mechanism provides the fastest access.

Dictionaries are rarely updated. The whole dictionary cache expires occasionally and is controlled by the temn.cache.dict.expiry.time property, which is defined in milliseconds. The default is 4 hours. The cache is also cleared if STANDARD.SELECTION is rebuilt, but this happens only on one node and is not cluster wide.