HMS Transact Outbox Ingestion
HMS Transact Outbox Ingestion ingests single or bulk data that comes from the Transact through Event Store infrastructure Microservice.
Docker
You can check the Configuration for the Event Store Microservice:
- MongoDB: Transact Outbox Ingester - MongoDB
- PostgreSQL DB:Transact Outbox Ingester - PostgreSQL DB
The Event Store Microservice send the sample data in the following format:
{ "specversion": "1.0", "id": "086f09bb-903a-4a35-947d-a323d2390800", "source": "https://temenos.com/microservice/cloudevents/ModelBank", "type": "STMT_ENTRY_DATA_EVENT", "datacontenttype": "application/json", "subject": "event", "time": "2023-07-05T08:02:25.372Z", "organizationid": "GB0010001", "sequenceno": -999, "businesskey": "ModelBank|GB0010001|FT23108D0HLQ", "correlationid": "086f09bb-903a-4a35-947d-a323d2390800", "data": { "applicationContext": { "tableKey": "ModelBank|GB0010001|202753367627470.020001", "applicationData": { "contractBalId": "100021", "positionType": "TR", "departmentCode": "1", "tdglDetails": ["TD", "", "", "", "", "", "", "VALUE.DATE"], "processingDate": "20230418", "productCategory": "1001", "ourReference": "FT23108D0HLQ", "balanceType": "CURBALANCE", "exchangeRate": "1.1432", "customerId": "100404", "currency": "EUR", "aaItemRef": "ACCOUNTS-TRANSFERIN-ARRANGEMENT*20230418*GB0010001*AA23075M4GPX**DIRECT*AAACT23108D7FXWBDC*", "companyCode": "GB0010001", "systemId": "FT", "consolKey": "AC.1.TR.EUR.1001.1002.US.....2200.....GB0010001", "exposureDate": "20230418", "amountLcy": "5000.00", "crfType": "DEBIT", "amountFcy": "4373.69", "transactionCode": "258", "valueDate": "20230418", "accountNumber": "100021", "netParam": "CLDEFAULT", "accountOfficer": "61", "origCcyMarket": "1", "transReference": "FT23108D0HLQ", "maskPrint": "SYSTEM", "bookingDate": "20230418", "stmtNo": ["202753367627470.02", "1-4"], "currencyMarket": "1", "systemDateTimeRec": ["20230705073750613"] }, "tableName": "FBNK_STMT_ENTRY" }, "eventContext": [{ "originatingApplication": "FUNDS.TRANSFER,", "bankingDate": "20230418", "transactionType": "ONLINE", "application": "FBNK_STMT_ENTRY", "action": "REVERSE", "channelType": "BROWSERTC", "operation": "WRITE", "requestStatus": "Reversed" }] } }
RR.PARAM and ILP Configuration for DES
The following are the entries added in RR.PARAM application for AMS.
| FXXX.AA.ARRANGEMENT | FXXX.ACCOUNT.CLOSED | FXXX.AA.ARR.PAYMENT.SCHEDULE |
| FXXX.AA.ARR.ACCOUNT | FXXX.AA.ARR.STATEMENT | FXXX.AA.INTEREST.ACCRUALS |
| FXXX.AA.ARR.CUSTOMER | FXXX.AA.ARR.TERM.AMOUNT | FXXX.AA.BILL.DETAILS |
| FXXX.AA.ARR.OFFICERS | FXXX.AA.ARR.INTEREST | FXXX.AA.ARR.FACILITY |
| FXXX.AA.ACCOUNT.DETAILS | FXXX.EB.CASHFLOW | |
Here FXXX - XXX denotes the company mnemonic.
Here is a sample RR.PARAM record
ILP Configuration
ILP enables ingesting the legacy records into Microservice.
Configure RR.INITIAL.LOAD.PARAMETER for applications that need ILP to be ran.
After RR.INITIAL.LOAD.PARAMETER is configured, start TSM and XXX/RR.INITIAL.LOAD.SERVICE (name of the service changes based in company).
In this topic