Configuring SWIFTNet FINCopy and FINInform services

If you use the SWIFTNet FINCopy service TPS to send messages, you must configure its central institution destination (CID). If necessary, you can configure additional settings for any of the SWIFTNet FINCopy services that you use, including TPS. If you are a central institution, you can configure settings for the FINInform service. 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_dnfcfcfs.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:

add -ou DNIvOU -ct DnfFinCopyService -co <fin_copy_service>  -attr CentralInstitution 
                                                             -val <central_institution>
;add -ou DNIvOU -ct DnfFinCopyService -co <fin_copy_service> -attr TransferDirection  
                                                             -val <transfer_direction>
;add -ou DNIvOU -ct DnfFinCopyService -co <fin_copy_service> -attr TolerateSingleAuthentication
com -ou DNIvOU

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

Copy the script into the home directory.
If the OU is to use more than one SWIFTNet FINCopy service, or if it represents a central institution that is to use more than one FINInform service, for each such service that it is to use, copy the lines in the script that begin with:
```
add -ou DNIvOU -ct DnfFinCopyService...
```
For each SWIFTNet FINCopy or FINInform service that is to be configured, replace the <fin_copy_service> placeholder in the script with one of the following values:
- For a TPS service, when there is more than one session BIC8, and when these session BIC8s need to behave differently from one another, specify a name of the form:
```
TPS_sessionBIC8_type
```
- For all other SWIFTNet FINCopy or FINInform services, or for a TPS service when there is only one session BIC8 or when the session BIC8s do not need to specify different behavior, specify a name of the form:
```
code_type
```
where:

code

Three-digit SWIFTNet FINCopy or FINInform service code, for example TGT, TPS, or CPY.

sessionBIC8

The session BIC8 used for sending and receiving messages.

type

Type of the SWIFTNet FINCopy or FINInform service:

LIVE

For a live system.

TEST

For a pilot (also called "test and training" or "T&T") system.

When a TPS FINCopy service is used, and if there is not a CO with a name of the form TPS_sessionBIC8_type that corresponds to the session BIC8 specified in the message, the CO with a name of the form TPS_type is used.
The following are examples of valid names for COs of type DnfFinCopyService:
```
TPS_LIVE
TPS_XXXXDEFF_LIVE
CPY_TEST
TGT_LIVE
```
For each SWIFTNet FINCopy service that is to be used, replace each of the placeholders with an appropriate value:

CentralInstitution <central_institution>

The central institution destination (CID) of the SWIFTNet FINCopy service TPS. The CID is a BIC8 that uniquely identifies the central institution.

TransferDirection <transfer_direction>

Indicates whether the FINCopy service can be used to send messages, receive messages, or both:

SR

This FINCopy service can be used to both send and receive messages. This is the default.

S

This FINCopy service can be used only to send messages. If a message is received from this service, FTM SWIFT issues an event message.

R

This FINCopy service can be used only to receive messages. If a local application attempts to send a message that specifies that this service is to be used, FTM SWIFT issues an event message.

TolerateSingleAuthentication

When a FINCopy service changes from using single authentication to using double authentication, you might still want to accept single-authenticated messages during a transition period. Specify this pseudo parameter if a FINCopy service is to accept messages that are to be authenticated using single authentication, even if its ASP specifies that double authentication is to be used.
If you do not use the SWIFTNet FINCopy service TPS, or if you use TPS but all of the CIDs for the OU use the same settings specified for TPS in step 4, skip this step. However, if you use TPS, and if there is more than one CID for the OU, and if one or more of these CIDs requires settings that differ from the settings specified for TPS in step 4, create, for each such CID, a separate CO of type DnfFinCopyService with a name of the form:
```
TPS_sessionBIC8_type
```
where:

sessionBIC8

The session BIC8 used for sending and receiving messages.

type

LIVE or TEST.

For example:
```
TPS_XXXXDEFF_LIVE
TPS_XXXXDEFF_TEST
```
Specify values for the attributes of each of these COs as appropriate.
Run the ou_dnfcfcfs.cli script. You must have the system configuration administrator (DniSA) role.
```
dnicli -i instance -ou SYSOU -s DNI_SYSADM -cft ou_dnfcfcfs.cli
```
Replace instance with the instance you are using.
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.