Example: configuring an SAG for a master LT
Table 1 shows the values
used for this example.
| Information type | Parameter description | Parameter value |
|---|---|---|
| General information | FTM SWIFT instance name | INST1 |
| SAG information | SAG name | SAG1 |
| Message partner name | XXXXUSNYA | |
| Message partner type | ClientServer | |
| Message format | Sag:RelaxedSNL | |
| Certificate list name | certlist1 | |
| LAU key name | LAU42123 | |
| First half-key (hk1) | 12qwertzuAsdrgt2 | |
| Second half-key (hk2) | 8u8kjhU2339ikkut | |
| IBM® MQ information | Queue manager | QM1 |
| Local queue cluster | SAGCLUS1 | |
| Queue prefix | DNI | |
| Server connection channel | QM1.SAG1 | |
| Transport type | TCP | |
| Host name | HOSTA | |
| Port number of the queue manager | 1415 | |
| LT information | LT | XXXXUSNYA |
Because FTM SWIFT uses InterAct
to implement its SIPN FIN service, both request
and response queues are needed. If an LT is to be used by both client
and server applications, request and response queues for both the
client and the server side must be configured. These queues are:
- Client request queue
-
FTM SWIFT naming schema: DNIvQPFX.DNFvLQCLUS
Example: DNI.SAGCLUS1
- Client response queue
-
FTM SWIFT naming schema: DNIvINST.DNF_FSM_CNR.ltname
Example: INST1.DNF_FSM_CNR.XXXXUSNYA
Note: The client response queue for an LT is created automatically during its LOGIN processing and does not have to be configured. - Server request queue
-
FTM SWIFT naming schema: DNIvINST.DNF_FSM_SLS.ltname
Example: INST1.DNF_FSM_SLS.XXXXUSNYA
Note: The server request queue for an LT is created automatically during its LOGIN processing. - Server response queue
-
FTM SWIFT naming schema: DNIvQPFX.DNIvSRV.SERVER.RESPONSE
Example: DNI.SAG1.SERVER.RESPONSE
- DNIvINST (FTM SWIFT instance name) is INST1
- DNIvSRV (SAG) is SAG1
- DNFvLQCLUS (local queue cluster) is SAGCLUS1
- DNIvQPFX (queue prefix) is DNI
- ltname (name of the LT) is XXXXUSNYA
Before you configure an SAG for a master LT:
- Configure the LAU key to be used by the message partner associated with the SAG (see Configuring a LAU key to be used by a message partner)
- Configure the certificate list to be used by the SAG (see Creating and managing lists of certificates and SWIFTNet services)
To configure an SAG for a master LT: