Configuring FMT routing information to route messages to a particular LT

Each FIN message contains the BIC8 of the destination to which it is to be sent. For FIN messages that are sent using FMT, you can configure rules that cause each message to be routed to a particular LT (BIC9) of that destination, depending on the FIN service identifier (field 103) and FIN message type specified in the message. The name of the LT corresponds to a CO of the type DnfLTApplicationSettings. This CO specifies the name of the queue and queue manager to which the message is passed, and from which the receiving application retrieves the message.

You create each routing rule by configuring a CO of type DnfFmtfRouting that specifies exactly one destination, but can specify more than one FIN service identifier (field 103) and FIN message type. The FMT service checks these COs by name in ascending alphanumeric order (0,1,...,9,A,B,...Z), and the first CO that matches the destination, FIN service identifier, and FIN message type of the message is used to determine the name of the LT to which the message is to be routed (the target LT). The name (BIC9) of this LT is composed of the BIC8 of the destination plus the one-character LT ID specified by the CO.

To help you configure the COs that specify the routing rules, FTM SWIFT generates, during customization a script with a name of the form:

deployment_dir/instance/admin/dnfcpcro.cli

where:

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

This script contains the following commands:

add -ou DNFSYSOU -ct DnfFmtfRouting -co <fmt_routing_info> -attr enabled
add -ou DNFSYSOU -ct DnfFmtfRouting -co <fmt_routing_info> -attr Destination            
                                                           -val <target_dest>
add -ou DNFSYSOU -ct DnfFmtfRouting -co <fmt_routing_info> -attr TargetLtId             
                                                           -val <target_lt_id>
add -ou DNFSYSOU -ct DnfFmtfRouting -co <fmt_routing_info> -attr LtAssignedServices     
                                                           -val <assigned_services>
add -ou DNFSYSOU -ct DnfFmtfRouting -co <fmt_routing_info> -attr LtAssignedMessageTypes 
                                                           -val <assigned_msg_types>
com -ou DNFSYSOU

To modify and run this script:

Copy the script into your home directory.
In the copy of the script, copy the set of add commands once for each routing rule to be defined, and replace the following items as appropriate:
<fmt_routing_info>

The name of the CO that corresponds to the routing rule. The recommended naming scheme is the BIC8 of the destination, followed by a two-digit number, followed by the one-character LT ID. For example, the CO with the name XXXXUSNY01A would specify the destination XXXXUSNY and the target LT ID A, and would cause a FIN message to be routed to the LT XXXXUSNYA.

Destination <target_dest>

The name (BIC8) of the target destination. Wildcard characters cannot be used.

TargetLtId <target_lt_id>

The LT ID (ninth character) of the name (BIC9) of the target LT. For example, the LT ID of the LT name XXXXUSNYA is A.

LtAssignedServices <assigned_services>
A list, separated by commas, of FIN service identifiers. A message is routed to the target LT only if the value in its field 103 is among those specified in this list. Wildcard characters cannot be used. For example:
```
CPT,CPY,XYZ
```
LtAssignedMessageTypes <assigned_msg_types>
A list, separated by commas, of FIN message types. A message is routed to the target LT only if its message type is among those specified in this list. The underscore (_) can be used as a wildcard character to represent a single character. For example:
```
103,999,2__,__4,_5_
```
Run the modified copy of the script. To do this, you must have the system configuration administrator (DniSA) role. Enter the following command:
```
dnicli -i instance -ou SYSOU -s DNI_SYSADM -cft dnfcpcro.cli
```
Approve and deploy the changes:
```
dnicli -i instance -ou SYSOU -s DNI_SYSADM 
app -ou DNFSYSOU
dep -ou DNFSYSOU
```
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.