Adherence of Business Event-Names to BIAN Standards
This section describes the externalisation of the Banking Industry Architecture Network (BIAN) standards in events raised across Temenos.
REST API interfaces are developed and published using open API specifications (OPEN API 3.0). However, events are raised as cloud events from the microservices. This feature adopts the externalisation of the Banking Industry Architecture Network (BIAN) standards in events raised across Temenos and expects these event names to be fully qualified with BIAN service domain and operation names. The BIAN is an association of banks, solution providers and educational institutions with the shared aim of defining a semantic service operation standard for the banking industry. It provides standard definitions of business functions and service interactions that describe the general internal working of any bank.
Externalising BIAN Service Mapping
The externalisation and transformation steps are performed as outlined below:
- BIAN and Product Domain ID mapping should be externalised and maintained as data records in the configuration microservice.
- Both TI-based and Java-based microservices use the above mapping to generate business events with the BIAN Service Domain ID with the above convention.
Storing BIAN and Product Domain ID Mapping using Configuration Microservice
The configuration microservice is used to store or process the BIAN and Product Domain ID mapping. It is stored as shown below in the configuration microservice.
The URI of the configuration microservice is,
v2.0.0/system/configurationGroups/com.temenos.product.bianmappings/configuration/{service}
This API has the following parameters:
- Group Id - com.temenos.product.bianmappings
- Configname - {service} - It is the product line from the event
Externalising during Event Delivery for MS
The BIAN and Product Domain ID Mapping externalisation is performed during event delivery for all microservices.
- Event runtime while delivering the events, event library makes use of mapping exits under the com.temenos.product.bianmappings group ID in the configuration microservice entry to translate the event name from <ProductLine>.<ProductGroupID> to < BIAN Service domain id >
- In case of missing mapping entries in the configuration microservice, event run time retains the event names.
Event Delivery for MS – KAFKA
Kafka is a commonly used event streaming platform in k8 microservices deployments.
To enable the BIAN service domain, add the following configurations in configmap.yaml under Event Delivery (inbox outbox)configuration.
|
Property |
Value |
Description |
|---|---|---|
|
temn.msf.event.bian.mapping |
true |
This is to enable externalise BIAN service mapping during event delivery.
|
|
temn.config.service.base.path |
http://<IP ADDRESS>:<PORT>/ms-genericconfig-api/api/v1.0.0/ |
Configuration microservice endpoint base URL
|
|
temn.config.service.resource.path |
system/configuration Groups/{groupId}/configuration/{configName} |
Configuration microservice resource path to get by Config-Name |
After deploying configuration and payment order microservice, to raise business events, create an API request and verify the outbox topic for the business event raised with revised BIAN domain name from the configuration microservice. The payments domain revised with BIAN domain “personal loan” is shown below.
Event Delivery for MS – KINESIS
Kinesis is a commonly used event streaming platform in the AWS microservices deployments.
To enable BIAN service domain, add the below properties under outbox handler configuration in install.bat/sh for AWS environment.
|
Property |
Value |
Description |
|---|---|---|
|
temn.msf.event.bian.mapping |
true |
This is to enable externalise BIAN service mapping during event delivery. |
|
temn.config.service.base.path |
http://<IP ADDRESS>:<PORT>/ms-genericconfig-api/api/v1.0.0/ |
Configuration microservice endpoint base URL |
|
temn.config.service.resource.path |
system/configuration Groups/{groupId}/configuration/{configName} |
Configuration microservice resource path to get by Config-Name |
To raise business events ,create an API request and verify the outbox topic for the business event raised with the revised BIAN domain name from the configuration microservice. The payments domain revised with the BIAN domain “personal loan” is shown below.
Externalising during Event Delivery for Transact
In case of events designed with only a product line (that is, without a product group), while raising events from the Transact code, add the product group to the event name and raise events in the Event Library of the product. For example, lending.mortgages. createLoan.loanCreated
To enable BIAN service mapping in outbox MDB, add the following configuration in Temenos/setenv.bat in UTP Folder.
|
Property |
Value |
Description |
|---|---|---|
|
-Dtemn.msf.event.bian.mapping |
true |
This is to enable externalised BIAN service mapping during event delivery. |
|
-Dtemn.config.service.base.path |
http://<IP ADDRESS>:<PORT>/ms-genericconfig-api/api/v1.0.0/ |
Configuration Microservice endpoint base URL
|
|
-Dtemn.config.service.resource.path |
system/configuration Groups/{groupId}/configuration/{configName} |
Configuration microservice resource path to get by Config-Name |
To raise a business event, create a request and the outbox topic for the business event raised with revised BIAN domain name from the configuration microservice. The payments domain revised with the BIAN domain “personal loan” is shown below.
In this topic
