Holdings Data Ingestion

This section explains the ingestion feature in microservice which is used to ingest data from external system into microservice.

In Holding microservice, there is two types of ingestion feature,

• Internal Ingestion - Ingested data from external system
• External Ingestion - Feature used for ingesting account aggregation data

The prerequisite of ingestion feature is to check the properties configuration for ingestion in HMS Configuration > HMS External Ingestion Configuration

Holding microservice uses full data event. To configure full data event, open des-kafka-t24.properties from the DES\des-docker\src\main\resources\des-config path and update the following property in the Event Pull Adapter section, for DES to understand from Temenos Transact tables it should pull the data and post into kafka.

The file name mentioned changes based on the company mnemonic. You should update Event Processor section by adding new assembly definition for arrangement microservice, for DES to understand from the regex pattern which event should be posted into assembled-event topic

RR.PARAM Configuration

The following entries are to be added in the RR.PARAM application for Arrangement microservice.

• FBNK.EB.CONTRACT.BALANCE
• FBNK.STMT.ENTRY

Sample RR.PARAM record is given below.

ILP Configuration

ILP is used for ingesting the legacy records into AMS.

You can configure RR.INITIAL.LOAD.PARAMETER for applications for which ILP to be run.

Once RR.INITIAL.LOAD.PARAMETER is configured, you should start TSM and BNK/RR.INITIAL.LOAD.SERVICE (name of the service changes based in company). You should run the service for ILP

The order in which the RR.PARAM to be created and ILP service to be run is given below.

Order	Application
1	FBNK.EB.CONTRACT.BALANCES
2	FBNK.STMT.ENTRY