SWIFT Module 7.1 SP10.July 2020 | Configuring SWIFT Module for FileAct and InterAct Message Exchange over SAG | Configuration Steps for InterAct and FileAct Messaging Services over SAG MQHA | Overview
The SWIFTNet component of SWIFT Module supports two types of transport for InterAct and FileAct messaging services over SWIFT Alliance Gateway (SAG): the Remote API Host Adapter (RAHA) and the MQ Host Adapter (MQHA).
The MQHA enables your SWIFTNet component client and server applications to communicate with SAG through IBM WebSphere MQ.
This chapter describes how to prepare your server or client application to exchange messages and files over SAG using the MQHA transport. For more information about the SWIFT messaging services and the two types of transport, see SWIFTNet Component. For information about how to configure the RAHA transport, see Configuration Steps for InterAct and FileAct Messaging Services over SAG RAHA.
The following diagram shows the response-request interaction between the client, server, and SAG when you use the MQHA transport.
The client and server must first register with the SWIFT Network. SAG must be installed on both the client and the server. In the diagram above, the applications are designated as SAG 1 for the client and SAG 2 for the server.
1. The client registers itself with the SWIFT Network through SAG 1.
2. The client application puts a message in the client request queue.
3. SAG 1 takes the message from this queue and determines the destination for the message is the server.
4. SAG 1 sends this message across the SWIFT Network to SAG 2.
5. On receipt of this message, SAG 2 puts the message in the server request queue of the server application.
6. The server application takes the message from the server request queue and processes the message as required. Then, the server application puts the reply message into the server response queue.
7. SAG 2 takes this message, determines its destination, and sends it across the SWIFT Network to SAG 1.
8. On receipt of this message, SAG 1 puts it in the client response queue.
9. The client takes this message from this queue.
To prepare your server application or your client application for the response-request interaction with SAG, you must complete the steps described in the following sections.