Configuring destinations for RM components

Before a relationship management component can carry out an action on behalf of a user for a particular destination, it must first determine whether that user has the necessary access rights. To do this, it must first determine to which business OU the destination belongs. For this reason, each destination 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

This applies also to synonym destinations, that is, destinations used by synonym LTs.

To help you configure COs of type DnfBic8Map, FTM SWIFT generates, during customization, scripts with names of the form:

deployment_dir/instance/admin/ou_dnfclcbm.cli

where:

deployment_dir

Directory specified in the CDP ini file.

instance

Name of the instance.

ou

Name of the OU.

These scripts contain the following commands:

add -ou DNFSYSOU -ct DnfBic8Map -co <BIC8> -attr BOU -val DNIvOU
com -ou DNFSYSOU

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

1. Copy the script into your home directory.
2. Copy the commands once for each destination that is to be configured.
3. Replace the following item in the copy of the script as required:

   <BIC8>

   The BIC8 of the destination.

4. Ensure that all commands that are to be executed are activated, that is, that they are not preceded by a semicolon character (;).
5. Run the modified copy of the script. This requires the access rights provided by the system configuration administrator (DniSA) role:

   dnicli -i instance -ou SYSOU -s DNI_SYSADM -cf ou_dnfclcbm.cli

6. 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.

If you plan to use the Relationship Management Application (RMA), in addition to configuring a CO of type DnfBic8Map, you must also configure, for each destination, a CO of each of the following types:

DnfRmAccessControl

This CO establishes the access rights for the RM data of the destination. Unless this CO is configured, no users are able to access the RM data. How to configure this CO is described in Authorizing use of the RMA.

DnfRmBic8

This CO specifies the parameters needed to transfer RMA messages to and from correspondents. Unless this CO is configured, no RMA messages can be exchanged for the destination. How to configure this CO and the other COs on which it depends is described in Configuring the RM transfer service.

Which BIC8 you specify as the name of each of these COs depends on whether the destination is a live or pilot (also called "test and training" or "T&T") destination: