Configuring the MSIF services

FTM SWIFT provides the following MSIF services:
MSIF transfer services (DNF_O_FT, DNF_O_FT1, DNF_O_FT2, DNF_O_FT3)
These services conduct each message and file transfer scenario. Service DNF_O_FT must always be used. You can optionally use services DNF_O_FT1, DNF_O_FT2 and DNF_O_FT3 to decouple message or file transfers from transfers with different processing requirements, for example in terms of message or file volume. See Messaging Services for SWIFTNet InterAct and FileAct (MSIF) for more information on using more than one MSIF transfer service.

A counterpart to or from which the MSIF transfer service transfers messages or files can use MSIF or any other product that implements the InterAct or FileAct protocols.

MSIF command service (DNF_O_CMD)
This service processes commands issued by operators and administrators, for example, commands to start or stop the MSIF transfer service, or to operate store-and-forward (SnF) queues. In addition, this service:
  • Automatically detects scenario timeouts (that is, when a SendMsg or SendFile request is not processed within its timeout period)
  • Automatically detects expired scenarios and modifies their status
  • Automatically detects SendMsg, ReceiveMsg, and DownloadFile scenarios that encountered recoverable errors and, if automatic recovery was configured, instructs DNF_O_FT to periodically attempt to recover them.
  • Automatically cleans up information pertaining to completed scenarios (if so configured)
  • Automatically reattempts to send files to an SAG when the SAG exhausts its capacity for concurrent file transfers.
Notes:
  1. Before you begin to configure these services, make sure that you carry out the following steps:
    • Decide whether you want to run MSIF transfer service DNF_O_FT only, or whether you need to decouple message or file transfers with different service requirements by using additional MSIF transfer services DNF_O_FT1, DNF_O_FT2 or DNF_O_FT3. See Messaging Services for SWIFTNet InterAct and FileAct (MSIF) for more information on using more than one MSIF transfer service.
    • Completely configure an SAG as described in Preparing to configure and configuring SAGs. This entails configuring, among other things:
      • An MQ connection
      • A certificate list for the SAG to use
      • Message partners for business OUs used for message and file transfers (one message partner for each MSIF transfer service and OU)
      • Message partners for the DNFSYSOU used for SAG event processing (one message partner for each SAG)
      • An endpoint per message partner that handles file and message transfer requests
    • Set the SWIFTNet user and security information as described in Managing SWIFTNet users and SWIFTNet security.
  2. For clarity, some of the command examples in the following sections show each parameter on a new line. When you enter these commands, you must enter them and their parameters all on a single line.