MDAL Events
In Party Microservices, MDAL Events raised through following methods:
Scheduler Flow
Scheduler raises the MDAL events based on the frequency set in the scheduler container.
- Frequency to trigger the scheduler job is set in the property temn.msf.scheduler.mdalcacheupdate.cron.trigger.time as cron expression.
- By default the frequency set to for every one hour (0 0 * * * *).
To update the frequency of the scheduler job, temn.msf.scheduler.mdalcacheupdate.cron.trigger.time need to be configured in the ENV under the config folder C:\ms-party-docker\config
ENV
#Scheduler Configuration temn_msf_scheduler_mdalcacheupdate_cron_trigger_time=0 0 * * * * temn_msf_scheduler_nosqlInboxCatchup_cron_trigger_time=0 */30 * ? * * temn_msf_scheduler_nosqlOutboxCatchup_cron_trigger_time=0 */30 * ? * * temn_msf_disableInbox_scheduler=true
Scheduler Flow is introduced in 2021.10 release
Adapter Flow
In Party Microservice, MDAL events are raised for the below scenarios
- When a new party, party identifier, observations, roles, contact references, and party relations records are created and updated through its respective API, an this raises MDAL event called MDAL_EVENT.
- For each address record is created and updated through its createAddresses and updateAddresses API, this raises a separate MDAL event MDAL_EVENT.
The above events are captured by the EventStore microservice and then route to Adapter and Generic config microservices and it must be configured to route TAFJ events.
Party API
Below is the list of Party APIs delivered for supporting MDAL Architecture.
| OPERATION ID | URI | API DESCRIPTION | RESPONSE |
|---|---|---|---|
| getCustomerProfile | /party/customers/{customerId}/profiles | Retrieves Personal details such as Residence details, Communication details, etc for the provided customer. | CustomerProfile |
| getCustomerSwiftAddress | /party/customers/{customerId}/addresses/swiftAddresses/{addressId} | Retrieves the SWIFT address details of electronic address type such as short name,tagIndicator for the customer, and BIC for the provided customer with the given addressId where the addressId is the reference id from the address record. For creating Address record,refer createAddressesV5 | CustomerSwiftAddress |
Upto 2021.07 release, In MDAL Architecture uses IRIS APIs.
Publisher API
Below is the list of APIs that are delivered for supporting MDAL architecture.
| OPERATION ID | URI | API DESCRIPTION | RESPONSE |
|---|---|---|---|
| getCustomerProfile | /party/customers/{customerId}/profiles | This API retrieves personal details such as Residence details, Communication details, and so on for the provided customer. | CustomerProfile |
| getCustomerSwiftAddress | /party/customers/{customerId}/addresses/swiftAddresses/{addressId} | This API retrieves the SWIFT address details of electronic address type such as short name, tagIndicator for the customer, and BIC for the provided customer with the given addressId where the addressId is the reference id from the address record. For creating Address record,refer createAddressesV5 | CustomerSwiftAddress |
| getCustomerId | /party/customers/alternateReferences/{alternateReference} | This API retrieves the customer identifier for the provided alternate reference of the customer where alternateReference is mapped to ALTERNATE.ID field in arrangement activity and ensure that this Account doesn't already exist in T24 with another reference (Configure ALTERNATE.ID as unique across T24). | CustomerId |
Field Name
|
Application/Table name
In this topic