SFD Client components
The components that comprise the SFD client process are (in the
order in which they process an outbound message):
- CBT layer of the SFD client process (CLC)
- A CLC retrieves, from the OAMS, the FIN messages to be sent via an LT session. It ensures that messages are sent in FIFO order, and assigns session and sequence numbers (SSNs) to each message before starting the ALC.
- Application Layer of the SFD client process (ALC)
- The ALC implements the SWIFTNet FIN AL protocol for outbound message traffic. It checks the message sequence, controls the arrival of expected FIN acknowledgments, and starts the Session Layer of the SFD client process (SLC) for the protocol elements to be exchanged over the session layer.
- Session Layer of the SFD client process (SLC)
-
The SLC implements the SWIFTNet FIN SL protocol for outbound message traffic. It collects SWIFT APDUs into batches and, for each batch, generates an InterAct message that contains a SWIFTNet FIN USER SL PDU (including signature information). It then starts the SL Output service (SLO).
- SL Output service (SLO)
- The
SLO:
- Implements the SL Retry protocol for the PDUs to be sent. For more information, see Session Layer (SL) Retry.
- Implements the Local Authentication (LAU) protocol. For more information, see LAU keys.
- Uses IBM® MQ to pass the InterAct message to the appropriate SAG. This message is prefixed by an MQHA envelope, as required by the SAG.