Identify Message and Interface Types
For the purposes of this sample, communication between FTM and external systems, services, or both, is assumed to be MQ.
The following table shows the message format support that is required.
| Source System | Target System | Format | Business Purpose |
|---|---|---|---|
| Client | FTM | Swift FIN MT103 | Payment Origination |
| Client | FTM | ISO Pain.001.001.03 | Batch Payment Origination |
| FTM | Repair Service | Swift FIN MT103 | Repair Request |
| Repair Service | FTM | Swift FIN MT103 | Repair Response |
| FTM | Liquidity Service | Swift FIN MT103 | Liquidity Request |
| Liquidity Service | FTM | Swift FIN MT103 | Liquidity Response |
| FTM | Payment Gateway | Swift FIN MT103 | Payment Initiation |
| Payment Gateway | FTM | Swift FIN MT103 | Gateway Acknowledgment |
| FTM | Client | ISO Pain.002.001.03 | Client Acknowledgment / Client Batch Acknowledgment |
Note: A generic business purpose label has been assigned to each transmission. During analysis and design, the
focus will be on the identified business purpose rather than specific format names in order to help de-couple
the process from the formats.
To monitor the various interfaces, the sample application publishes
the following external events to inform periodically on the progress
or about certain milestones:
- FTMHostedServiceBeginSummary
- Periodically summarizes beginning transactions in a service hosted by FTM directly.
- FTMHostedServiceEndSummary
- Periodically summarizes ending transactions in a service hosted by FTM directly.
- FTMInvokedServiceSummary
- Periodically summarizes transactions currently processed by a service that got invoked by FTM.
- FTMHostedServiceTxnFail
- Milestone reached that a particular transaction failed in a service hosted by FTM directly.
- FTMInvokedServiceTxnFail
- Milestone reached that a particular transaction failed in a service that got invoked by FTM.