| Table of Contents |
|---|
The ESR integration consists mostly from a modern eventful tech stack.
...
AppRecords
Services involved:
AppGenerator
DataExportDataExporter
TCS
When an ESR Position has been reconciled against a TIS Post, AppRecords are then generated. For every Placement linked to said Post, we’ll generate an AppRecord and send it to the DataExport service to persist.
...
AppRecords that then match a criteria (within a window of +2 days and less than 13 weeks start date) are then picked up, written to file which is then FTP’d to the AWS server
Notifications
Confirmations
...
Services involved:
NotificationGenerator
DataExporter
TCS
Also after the reconciliation of Posts and Positions, the notification service then starts to generate Notification records. Like the AppRecords, they will be generated and sent to the DataExporter where they will be saved if they have not been submitted before. Also like the AppGen process, notifications are picked up are a certain time if they meet the criteria before being written to file and sent
Inbound
Services involved:
InboundDataWriter
TCS
The inbound stream takes data ASG data from the RMT files and updates the relating data in TIS, this data is pushed from the splitter to the esr.queue.asg.split queue and is read by the InboundDataWriter service. Currently this data is limited to Personal data such as personal details, address and absence and is updated via REST to TCS using POST, PUT and PATCH endpoints.
Confirmations
not yet been defined
All services have been defined with transaction support, this means that if an operation fails with MongoDB or RabbitMQ, any previous actions done with those within the same transaction will be rollback and can be attempted again