Example: configuring an SAG for use by MSIF applications

Table 1 shows the values used for this example.
Table 1. Sample values for an SAG used with the MSIF transfer services
Information type Parameter description Parameter value
General information FTM SWIFT instance name INST1
SAG information SAG name SAG1
IBM MQ information Queue manager used by the MSIF transfer service (do not specify if a cluster is used) QM1
Queue prefix DNI
Server connection channel QM1.SAG1
Transport type TCP
Host name of the system on which the MSIF transfer service runs HOSTA
Port number of the queue manager 1415
MSIF transfer service information for service DNF_O_FT Name of the SI endpoint and message partner for the business OU FT_CLSRVBANKA
SNL endpoint specific for the business OU (this is the endpoint specified by the SAG MP option with the name SnlEP) xxxxdeff_ep1_ft
Business OU BANKA
Message partner name for SAG events to service DNF_O_FT (this is the message partner specified by the SAG communication option with the name SAG1) FT_SRVEVT
MSIF transfer service information for service DNF_O_FT1

(this transfer service is used in addition to DNF_O_FT to decouple message and file transfers)

Name of the SI endpoint and message partner for the business OU FT1CLSRVBANKA
SNL endpoint specific for the business OU (this is the endpoint specified by the SAG MP option with the name SnlEP) xxxxdeff_ep1_ft1
Business OU BANKA
Message partner name for SAG events to service DNF_O_FT1 (this is the message partner specified by the SAG communication option with the name SAG1) FT1SRVEVT
SAG global parameters
Note: These parameters must be specified only if the SAG is to be used to conduct file transfers and if, during those file transfers, LFT is to be used to transfer file data between the host and the SAG.
GetFile queue DNI.DNF_GETFILEQ
FileDirectory /tmp/mqha
FileExpiration 90
MaxLFTMessageSize 4
In this example, the following queues must be configured:
Server request queues
These are the queues into which the SAG puts request messages that are to be processed by the MSIF transfer services.

FTM SWIFT naming schema: DNIvINST.DNFSYSOU.DNF_O_FTTMHx

In this example: INST1.DNFSYSOU.DNF_O_FTTMH and INST1.DNFSYSOU.DNF_O_FTTMH1

Server response queue
This is the queue into which the MSIF transfer service puts responses that are to be passed to the SAG.

FTM SWIFT naming schema: DNIvQPFX.DNIvSRV.SERVER.RESPONSE

In this example: DNI.SAG1.SERVER.RESPONSE

Client request queue
This is the queue into which the MSIF transfer service puts requests that are to be passed to the SAG.

FTM SWIFT naming schema: DNIvQPFX.DNIvSRV.SPECIFIC.CLIENT.REQUEST

In this example: DNI.SAG1.SPECIFIC.CLIENT.REQUEST

LFT PutFile queue
If local file transfer (LFT) is to be used to exchange files between the host and the SAG, this is the queue into which the MSIF transfer service puts data that is to be transferred to the SAG.

FTM SWIFT naming schema: DNIvQPFX.DNIvSRV.DNF_PUTFILEQ

In this example: DNI.SAG1.DNF_PUTFILEQ

LFT GetFile queue
If local file transfer (LFT) is to be used to exchange files between the host and the SAG, this is the queue into which the SAG puts data that is to be transferred to the MSIF transfer service.

FTM SWIFT naming schema: DNIvQPFX.DNF_GETFILEQ

In this example: DNI.DNF_GETFILEQ

To configure an SAG for use with the MSIF transfer services:
  1. If the MSIF transfer services are to conduct file transfers, and if LFT is to be used to transfer file data between the host and the SAG, set the following SAG global parameters:
    Parameter Value
    GetFileQueue (this is the queue specified by the SAG communication option with the name LftGetFileQueue) DNI.DNF_GETFILEQ
    FileDirectory (this is the directory specified by the SAG communication option with the name SagDirectory) /tmp/mqha
    FileExpiration (this must be greater than or equal to the value specified by the SAG communication option with the name LftTimeOut) 90
    MaxLFTMessageSize 4
  2. Configure an MQ connection with the following values:
    Parameter Value
    SAG name SAG1
    Queue manager used by the MSIF transfer service (do not specify if a cluster is used) QM1
    Message coding 1208
    Channel name QM1.SAG1
    Transport type TCP
    Connection name 'HOSTA(1415)'
    Server response queue DNI.SAG1.SERVER.RESPONSE
    Client request queue DNI.SAG1.SPECIFIC.CLIENT.REQUEST
    Putfile queue (this is the queue specified by the SAG communication option with the name LftPutFileQueue) DNI.SAG1.DNF_PUTFILEQ
  3. Configure the certificate list the SAG is to use.
  4. Configure two message partner to be used for file and message transfers.
    1. For message or file transfers conducted by MSIF transfer service DNF_O_FT in business OU BANKA, create a message partner with the following values:
      Parameter Value
      SAG name SAG1
      Message partner name (this is the message partner specified by the SAG MP option with the name MP) FT_CLSRVBANKA
      Message partner type ClientServer
      Message format Sag:RelaxedSNL
      Certificate list Name of the list created in step 3
      Default message format Sag:RelaxedSNL
      Name of set of MQHA parameters FT_CLSRVBANKAP
      Queue manager used by the MSIF transfer service (do not specify if a cluster is used) QM1
      Request queue INST1.DNFSYSOU.DNF_O_FTTMH
      Message coding 1208
      Message expiration -1
      Conversion MQFMT_NONE
      Envelope with envelope
    2. For message or file transfers conducted by MSIF transfer service DNF_O_FT1 in business OU BANKA, create a message partner with the following values:
      Parameter Value
      SAG name SAG1
      Message partner name (this is the message partner specified by the SAG MP option with the name MP) FT1CLSRVBANKA
      Message partner type ClientServer
      Message format Sag:RelaxedSNL
      Certificate list Name of the list created in step 3
      Default message format Sag:RelaxedSNL
      Name of set of MQHA parameters FT1CLSRVBANKAP
      Queue manager used by the MSIF transfer service (do not specify if a cluster is used) QM1
      Request queue INST1.DNFSYSOU.DNF_O_FTTMH1
      Message coding 1208
      Message expiration -1
      Conversion MQFMT_NONE
      Envelope with envelope
  5. Configure two SI endpoints to be used by file and message transfers and connect them to the message partners you created in step 4.
    1. Configure an SI endpoint to be connected to Message Partner FT_CLSRVBANKA:
      Parameter Value
      SAG name SAG1
      SI endpoint name FT_CLSRVBANKA
      SNL endpoint name (this is the endpoint specified by the SAG MP option with the name SnlEP) xxxxdeff_ep1_ft
      Message partner name (this is the message partner specified by the SAG MP option with the name MP) FT_CLSRVBANKA
      SNL protocol Relaxed
      Cryptographic protocol Advanced
    2. Configure an SI endpoint to be connected to Message Partner FT1CLSRVBANKA:
      Parameter Value
      SAG name SAG1
      SI endpoint name FT1CLSRVBANKA
      SNL endpoint name (this is the endpoint specified by the SAG MP option with the name SnlEP) xxxxdeff_ep1_ft1
      Message partner name (this is the message partner specified by the SAG MP option with the name MP) FT1CLSRVBANKA
      SNL protocol Relaxed
      Cryptographic protocol Advanced
  6. If the MSIF transfer services are to conduct file transfers or SnF message transfers, configure message partners to handle SNL events (one per SAG and MSIF transfer service for all OUs):
    1. For SAG1 and MSIF transfer service DNF_O_FT, configure a message partner with the following values:
      Parameter Value
      SAG name SAG1
      Message partner name (this is the message partner specified by the SAG communication option with the name EventMP) FT_SRVEVT
      Message partner type ClientServer
      Message format Sag:RelaxedSNL
      Certificate list Name of the list created in step 3
      Default message format Sag:RelaxedSNL
      Name of set of MQHA parameters FT_SRVEVTP
      Queue manager used by the MSIF transfer service (do not specify if a cluster is used) QM1
      Request queue INST1.DNFSYSOU.DNF_O_FTTMH
      Message coding 1208
      Message expiration -1
      Conversion MQFMT_NONE
      Envelope with envelope
    2. For SAG1 and MSIF transfer service DNF_O_FT1, configure a message partner with the following values:
      Parameter Value
      SAG name SAG1
      Message partner name (this is the message partner specified by the SAG communication option with the name EventMP) FT1SRVEVT
      Message partner type ClientServer
      Message format Sag:RelaxedSNL
      Certificate list Name of the list created in step 3
      Default message format Sag:RelaxedSNL
      Name of set of MQHA parameters FT1SRVEVTP
      Queue manager used by the MSIF transfer service (do not specify if a cluster is used) QM1
      Request queue INST1.DNFSYSOU.DNF_O_FTTMH1
      Message coding 1208
      Message expiration -1
      Conversion MQFMT_NONE
      Envelope with envelope

    The SAG automatically creates the event endpoints that correspond to these message partners when the MSIF transfer services subscribe to receive SNL events from the SAG.

How you configure an SAG for use with the MSIF transfer service depends on whether you have access to the SAG configuration service (DNFSAGCFG):
  • If you do not have access to DNFSAGCFG, you must configure all these values using the SWIFT Alliance Web Platform.
  • If you have access to DNFSAGCFG, configure these values by carrying out the following steps:
    1. Start the SAG (see Starting the SAG).
    2. Open the CLI with the following parameters:
      dnicli -i INST1 -ou DNFSYSOU -s DNFSAGCFG
    3. If LFT is to be used to transfer file data between the host and the SAG, configure the required SAG global parameters by issuing the ugp (updateGlobalParameters) command as follows:
      ugp  -sag SAG1
           -gfq DNI.DNF_GETFILEQ
           -fdir /tmp/mqha
           -fexp 90
           -maxlftms 4
    4. Configure the MQ connection. Issue the amqc (addMQConnection) command as follows:
      amqc   -sag SAG1
             -qm QM1
             -cid 1208
             -ch QM1.SAG1
             -tt TCP
             -cn 'HOSTA(1415)'
             -srq DNI.SAG1.SERVER.RESPONSE
             -crq DNI.SAG1.SPECIFIC.CLIENT.REQUEST
             -pfq DNI.SAG1.DNF_PUTFILEQ
      This command configures the IBM MQ connection needed to transfer FileAct or InterAct requests and response messages between the MSIF transfer service and an SAG.
    5. Configure a certificate list. To do this, issue the ac (addCert) command:
      addCert -cln  certlist1
              -cert cn=department-a,o=xxxxusny,o=swift
              -cert cn=department-a1,o=xxxxusny,o=swift
              -cert cn=department-a2,o=xxxxusny,o=swift
    6. Configure two message partners. To do this, issue the amp (addMessagePartner) command:
      amp   -sag  SAG1
            -mpn  FT_CLSRVBANKA
            -type ClientServer
            -mfm1 Sag:RelaxedSNL
            -cln  certlist1
            -dfm  Sag:RelaxedSNL
            -mqha  (
                   -name FT_CLSRVBANKAP
                   -qm   QM1
                   -rqq  INST1.DNFSYSOU.DNF_O_FTTMH
                   -cid  1208
                   -mex  '-1'
                   -con  MQFMT_NONE
                   -env  With
                   )
      
      amp   -sag  SAG1
            -mpn  FT1CLSRVBANKA
            -type ClientServer
            -mfm1 Sag:RelaxedSNL
            -cln  certlist1
            -dfm  Sag:RelaxedSNL
            -mqha  (
                   -name FT1CLSRVBANKAP
                   -qm   QM1
                   -rqq  INST1.DNFSYSOU.DNF_O_FTTMH1
                   -cid  1208
                   -mex  '-1'
                   -con  MQFMT_NONE
                   -env  With
                   )
      These commands identify the MSIF application within FTM SWIFT and configures how that application is addressed by the MQ Host Adapter.
    7. Configure two SI endpoints. To do this, issue the aep (addSiEndpoint) command:
      aep  -sag  SAG1
           -epn  FT_CLSRVBANKA
           -sep  xxxxdeff_ep1_ft
           -mpn  FT_CLSRVBANKA
           -spro Relaxed
           -cpro Advanced
      
      aep  -sag  SAG1
           -epn  FT1CLSRVBANKA
           -sep  xxxxdeff_ep1_ft1
           -mpn  FT1CLSRVBANKA
           -spro Relaxed
           -cpro Advanced
      These commands configure the routing. All inbound messages that refer to the SNL endpoint with the name xxxxdeff_ep1_ft are routed to the message partner FT_CLSRVBANKA. All inbound messages that refer to the SNL endpoint with the name xxxxdeff_ep1_ft1 are routed to the message partner FT1CLSRVBANKA.
    8. To configure an additional business OU for use with an MSIF application, repeat the steps 6 and 7 with the appropriate values for the application name and the SNL endpoint.
    9. If the MSIF transfer services are to conduct file transfers or SnF message transfers, configure message partners for SNL event processing. To do this, issue the amp (addMessagePartner) command:
      amp   -sag  SAG1
            -mpn  FT_SRVEVT
            -type ClientServer
            -mfm1 Sag:RelaxedSNL
            -cln  certlist1
            -mqha  (
                   -name FT_SRVEVTP
                   -qm   QM1
                   -rqq  INST1.DNFSYSOU.DNF_O_FTTMH
                   -cid  1208
                   -mex  '-1'
                   -con  MQFMT_NONE
                   -env  With
                   )
      
      amp   -sag  SAG1
            -mpn  FT1SRVEVT
            -type ClientServer
            -mfm1 Sag:RelaxedSNL
            -cln  certlist1
            -mqha  (
                   -name FT1SRVEVTP
                   -qm   QM1
                   -rqq  INST1.DNFSYSOU.DNF_O_FTTMH1
                   -cid  1208
                   -mex  '-1'
                   -con  MQFMT_NONE
                   -env  With
                   )
    10. Approve and deploy the SAG configuration by issuing the following commands:
      app -sag SAG1
      dep -sag SAG1
    11. Stop and restart the SAG (see Stopping and restarting the SAG).
    12. Issue the enable command (see enable) for the following SAG entities:
      • The MQ connection DnfMqConnection
      • The message partners FT_CLSRVBANKA and FT1CLSRVBANKA
      • The message partners FT_SRVEVT and FT1SRVEVT
      • The endpoints FT_CLSRVBANKA and FT1CLSRVBANKA
    13. Set up SWIFTNet user and security information as described in Managing SWIFTNet users and SWIFTNet security.