Data Ingestion

This section explains the data models of extension data and alternate key. Microservice framework supports:

• Configuration based ingestion for local reference fields
• Product ingester additionally looks for mapping configuration for extension data fields and populates product extension and alternate key tables.
• Configuration for mapping between extension data key and JSON path of local reference field in JSON message (AVRO, in case of Temenos Transact).

As part of Data Ingester extension, you should write a mapping specification in the form of a jolt specification JSON file to transform required fields of source system’s (for example, Temenos Transact) extension fields to the microservice extension fields.

In the case of Temenos Transact Data events, Avro schema name can be obtained from the DES schema registry.