Configuring a synonym LT

Note: Before you configure a synonym LT, you first must configure the corresponding master LT.

You can configure synonym LTs for use with the SIPN FIN and FMT FIN services. Each synonym LT corresponds to exactly one master LT. Both LTs must belong to the same OU.

For each message that is processed:

If the sending LT, which is specified in the basic header, is a synonym LT, the sending service uses the corresponding master LT to send the message.
If the receiving LT, which is specified in the application header, is a synonym LT, the receiving service uses the corresponding master LT to receive the message.

In order for a message to be processed by a synonym LT:

For SIPN FIN: The corresponding master LT must be logged in. Do not log in the synonym LT.
For FMT FIN: The FMT FIN service must be started for the corresponding master LT. Do not start the FMT FIN service for the synonym LT.

You configure a synonym LT by creating COs of the types DnfLTApplicationSettings and DnfSynonymLT, and adding them and their attributes to the appropriate business OU. To help you do this, FTM SWIFT generates, during customization, for each business OU, a script with a name of the form:

deployment_dir/instance/admin/ou_dnfcfcsl.cli

where:

deployment_dir: Directory specified in the CDP initialization file.
instance: Name of the instance.
ou: Name of the OU.

These scripts contain the following commands:

; create CO of CT DnfLTApplicationSettings and fill its attributes
add -ou DNIvOU -ct DnfLTApplicationSettings -co <synonymLT> -attr send
add -ou DNIvOU -ct DnfLTApplicationSettings -co <synonymLT> -attr Queue        -val <applicationQ>
add -ou DNIvOU -ct DnfLTApplicationSettings -co <synonymLT> -attr QueueManager -val <applicationQM>
;
; If you want to enable special exception processing for this synonym LT, you
; must add the attribute ExceptionOptionSet and replace the placeholder with
; the appropriate value
; <exception_co>         The name of the option-set to be used for exception
;                       processing
; To do this, remove the comment-sign of the next line
; add -ou DNIvOU -ct DnfLTApplicationSettings -co <synonymLT> -attr ExceptionOptionSet -val <exception>
;
; commit OU (must be approved and deployed separately)
com -ou DNIvOU
;
; create CO of CT DnfSynonymLT and fill its attribute Master
add -ou DNFSYSOU -ct DnfSynonymLT           -co <synonymLT> -attr Master -val <masterLT>
;
; commit DNFSYSOU (must be approved and deployed separately)
com -ou DNFSYSOU

The customization process substitutes the placeholder DNIvOU in the script with the name of the OU. Modify and run this script once for each LT:

Copy the script into the home directory.
Replace the following items in the copy of the script as appropriate:
<synonymLT>

The name of the synonym logical terminal. It must be the LT name provided by SWIFT. Note that an LT name must fulfill the format rules of LT names according to SWIFT even if it is used for FMT FIN only. In particular, a zero (0) is not allowed as LTID at the 9th position of the LT name.

Queue <applicationQ>
The IBM MQ queue on which a FIN application receives FIN messages from FTM SWIFT.
Note: If this queue is a cluster queue, do not specify a queue manager; that is, comment out the line that configures the queue manager (QueueManager) in the dnfcfcsl.cli script. If you already configured the queue manager value, use the following command to remove it:
rem -ou DNIvOU -ct DnfLTApplicationSettings -co ltname -attr QueueManager
QueueManager <applicationQM>

The queue manager that holds the queue on which a FIN application receives FIN messages from FTM SWIFT.

Master <masterLT>

The name (BIC9) of the master LT.
Run the dnfcfcsl.cli script once for each synonym LT by issuing the following command:
```
dnicli -i instance -ou SYSOU -s DNI_SYSADM -cf dnfcfcsl.cli
```
where instance represents the instance you are using. To do this, you must have the system configuration administrator (DniSA) role.
Approve and deploy the changes:
```
dnicli -i instance -ou SYSOU -s DNI_SYSADM 
app -ou ou
dep -ou ou
```
If dual authorization is enabled, another user with the appropriate access rights must approve the changes before they can be deployed. If dual authorization is disabled, you can skip approving the changes and immediately deploy them.
Ensure that the following conditions are met:
- The destination (BIC8) of each synonym LT must be associated with exactly one OU by means of a CO of type DnfBic8Map:
  - The name of the CO is the BIC8 of the destination
  - The value of the BOU attribute of the CO is the business OU to which the destination belongs
- Ensure that a synonym LT belongs to the same business OU for which the user ID has the role SWIFTNetFINSender.