Integrating TAFJ Cache Apache Ignite Setup with Data Event Streaming

You can integrate the Data Event Streaming (DES) product with the Temenos Transact system’s F.DATA.EVENTS table to cache all records from this table using the following procedure.

1. Deploy data-repository-core.jar and data-repository-cache.jar instead of TAFJCache.jar to your application server.
2. Depending on your DES environment, set the property for the Ignite configuration file, which exists in the data-repository-core.jar file for the application server.
   • -Dtemn.cache.ignite.conf.file.name=des-ignite-cache.xml or
   • -Dtemn.cache.ignite.conf.file.name=des-ignite-cache-secure-ssl.xml
3. On the Temenos Transact server, insert the following into the TAFJ_CACHE table and commit.

   INSERT INTO TAFJ_CACHE (RECID, CACHENAME) VALUES (‘F.DATA.EVENTS’,’ FDataEventCache’)

4. If data is written to different company tables, repeat step 2 for each of the company tables, i.e. FBNK_DATA_EVENTS, FEU1_DATA_EVENTS, etc.
5. Depending on whether or not you are running the application server as an Ignite server (i.e. -Dtemn.tafj.cache.ignite.server.mode=true), start an Ignite server if you have not started. To do this in the DES product, go to the data-repository-server folder and type start-application.bat(sh). The items cached and written from the TAFJ system to FDataEventCache will be read by the DES Event Processor from this same cache.
6. Enable the external caching in TAFJ, i.e. temn.tafj.runtime.use.external.caching=true

Advantages of Integrating TAFJ Cache Apache Ignite Setup with Data Event Streaming

This integration has the following advantages:

• Offload work from the OLTP Temenos Transact database
• Cache the records before it is required by the Event Processor in the Data Event Streaming. Therefore, the cache records are available without going back to the database.