Architecture
Figure 1 shows the components that comprise the Relationship Management Application and their interactions.
- RMA enterprise application
- The web-based user interface to RMA. It runs in the application server and allows users to view and manage RMA authorisations, queries, and answers stored in the RMDS. This component is not needed if a third-party product or another instance of FTM SWIFT is used for those tasks.
- RM data store (RMDS)
- A set of Db2® tables that hold RMA authorisations, queries, and answers. The RMA authorisations are needed to perform RMA traffic filtering when sending or receiving messages. If a third-party product or another instance of FTM SWIFT is used for managing RMA authorisations, the RMDS contains only current RM authorisations, but no queries and answers. If RMA is used to manage authorisations, the RMDS also holds pending versions of RMA authorisations.
- RM transfer service
- A service that processes messages about RMA authorisations, queries, and answers. The RM transfer service also handles the RMA data synchronization. When, as a result of changes to RM data, a message must be sent to a correspondent, this service creates that message and sends them to the MSIF transfer service. The MSIF transfer service must be configured to exchange ages (service swift.rma or swift.rma!p) with correspondents. When messages from correspondents are received and routed to the RM transfer service, it stores their contents in the RMDS. The RM transfer service is described in RM transfer service. This component is not needed if a third-party product or another instance of FTM SWIFT is used for managing RMA authorisations, queries, and answers.
- ASP data
- A set of Db2 tables that hold Application Service Profile (ASP) data. Application Service Profiles define parameters for relationship management and RMA traffic filtering. ASP packages are provided by SWIFT and must be imported into the database by the ASP administrator.
- RM and ASP admin service
- A service for administrative operations on the RMDS and the ASP data. RMA authorisation data can be exported for distribution to other components that implement RMA traffic filtering. RMA authorisation data can be imported if a third-party product or another instance of FTM SWIFT is used for managing authorisations. ASP packages must be imported to provide the ASP data required for RMA traffic filtering.
The MSIF and SIPN FIN transfer services use the ASP data to check
whether RMA traffic filtering is required for a message. If so, they
use the data in the RMDS to determine whether each message is authorized.
The transfer services use only current authorisations; they ignore:
- Pending versions of authorisations
- Queries
- Answers
The RMA enterprise application provides access to current and pending versions of authorisations, queries, and answers. It uses the ASP data to validate user input like service names, validity periods, or message types. Selection lists are populated with ASP data to prevent incorrect input. The RMA enterprise application uses the BIC directory of the reference data to perform BIC expansion and to check for stale authorisations, where the own BIC or correspondent BIC is no longer listed in the BIC directory.