Creating local addresses

To create a new local address you must create a CO of type DnqERLocalAddress for each OU which is to use the address. To help you do this, FTM SWIFT generates, during customization, a script with a name of the form:

deployment_dir/instance/admin/ou_dnqcecoo.cli

where:

deployment_dir

Directory specified in the CDP initialization file.

instance

Name of the instance.

ou

Name of the OU.

This script contains the following commands:

add -ct DnqERLocalAddress -ou DNIvOU -co <LocalAddr> -attr AddressType -val <Type>
add -ct DnqERLocalAddress -ou DNIvOU -co <LocalAddr> -attr Address     -val <Address>
;add -ct DnqERLocalAddress -ou DNIvOU -co <LocalAddress> -attr DisplayName  -val <DisplayName>
com -ou DNIvOU

The customization process substitutes the placeholder DNIvOU in the script with the name of the OU. To modify and run the script for the OU you are going to change:

1. Copy the script for the OU to change into your home directory.
2. Copy the commands once for each local address that is to be created.
3. Ensure that all commands that are to be executed are activated, that is, that they are not preceded by a semicolon character (;).
4. Replace the following items in the copy of the script as required:

   <LocalAddr>

   A name used to identify the local address definition. This name can be up to 30 characters long and can contain only:

   • Characters of the set [A-Za-z0-9]
   • Periods (.)
   • Hyphens (-)
   • Underscore characters (_)

   Do not use a DN as a logical name because DNs contain other characters.

   <Type>

   The type of the local address:

   DN

   Distinguished name.

   LT

   Logical terminal.

   <Address>

   The DN or LT that is the local address. This address must be unique among all local addresses that are configured for the OU. For FIN, this must be a 12-character LT address, that is, an LT address that includes the branch code.

   <DisplayName>

   The name that is to appear in the user interface of the MER Facility. It is displayed in the local address column of the message list, and in the list of possible senders when creating a new message. The default is the value of the Address attribute.

5. The file ou_dnqcecoo.cli also contains commands to create MER queues and custom actions. As needed, you can either:
   • Customize these commands as described in Creating new queues and Creating custom MER Facility actions.
   • Deactivate them by placing a comment symbol (;) at the beginning of each line.
6. Run the modified copy of the ou_dnqcecoo.cli script. This requires the access rights provided by the system configuration administrator (DniSA) role:

   dnicli -i instance -ou SYSOU -s DNI_SYSADM -cft ou_dnqcecoo.cli -cp IBM-1047

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

After you deploy a new local address:

• Ensure that appropriate access is granted to the users that are to use this local address (see Creating MER Facility roles).
• Wait for approximately 5 minutes to allow the MER enterprise application to pick up the configuration change.
• Logout and login again the sessions of all users who are to have access to the new local address.
• If criteria is based on local addresses, deploy adapted MER Routing message flows.