Setting global parameters and mapping message partners

You configure global parameters for the MSIF transfer services and map message partners to OUs for inbound messages and files by setting attributes for COs. To help you do this, FTM SWIFT generates, during customization, a script with a name of the form:

deployment_dir/instance/admin/dnfcocpy.cli

where:

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

This script contains the following commands:

add -ct DnfEfaParameters -ou DNFSYSOU -co DnfEfaParameters -attr SNLRequestExpiration -val 90
add -ct DnfEfaParameters -ou DNFSYSOU -co DnfEfaParameters -attr CleanupPeriod -val P7DT0H0M
add -ct DnfEfaParameters -ou DNFSYSOU -co DnfEfaParameters -attr NULLValue -val NULL
add -ct DnfEfaParameters -ou DNFSYSOU -co DnfEfaParameters -attr BatchSize -val 100
add -ct DnfEfaParameters -ou DNFSYSOU -co DnfEfaParameters -attr ReplBatchSize -val 100
;add -ct DnfEfaParameters -ou DNFSYSOU -co DnfEfaParameters -attr AutoCleanup

;add -ct DnfEfaParameters -ou DNFSYSOU -co DnfEfaParameters -attr EfaDataDirectory -val <EfaDataDirectory>
;add -ct DnfEfaParameters -ou DNFSYSOU -co DnfEfaParameters -attr EfaWorkDirectory -val <EfaWorkDirectory>

;Copy and edit the following line once for each message partner
;that is to process MSIF requests that use real-time delivery mode
;(not needed for message partners that process only SnF requests)
add -ct DnfEfaMPMap -ou DNFSYSOU -co <MessagePartner> -attr BOU -val <bou>
com -ou DNFSYSOU

To modify and run these scripts:

Copy the script into your home directory.
Specify the appropriate value for each of the attributes of the DnfEfaParameters CO:
SNLRequestExpiration
This attribute determines the following intervals:
- The value of this attribute specifies the maximum amount of time, in seconds, after the MSIF transfer service puts a SendFile, SendMsg, or RespondDownload request into the input queue of an SAG, by which the SAG must begin processing the request. If the SAG does not remove the request before this amount of time elapses, the message is deleted from the queue.
- After placing a SendFile, SendMsg, or RespondDownload request into the input queue of an SAG, or after responding to a FileReceived, MsgReceived, or DownloadFile request, the MSIF transfer service waits three times this number of seconds for a response from the SAG. If no response is received by this time, the request is flagged as being in error, that is, its transfer condition is set to InError.
- When the MSIF transfer service automatically attempts to recover an SnF FileReceived scenario, the value of this attribute determines how many seconds the MSIF transfer service waits between new attempts.
The default is 90 seconds
Note: This attribute applies only to requests or responses passed from the MSIF transfer service to the SAG. The MSIF transfer service must reply to requests passed from the SAG within 60 seconds.
CleanupPeriod
The value of this attribute specifies the minimum amount of time that the information associated with a finished scenario (that is, a scenario whose transfer condition was set to finished) is kept in the database. During this time, the information is available to help identify possible duplicate transmissions. After this time, the information is deleted during database cleanup (see Maintaining MSIF database tables). The value must have the form:
```
PdDThHmM
```
where:

d

The number of days.

h

The number of hours (0 - 23).

m

The number of minutes (0 - 59).

The minimum value is 1 minute (P0DT0H1M). The default is 7 days (P7DT0H0M).
Notes:
1. Due to implementation limitations, the actual cleanup period might be up to 1 hour longer than specified.
2. A delivery notification for a message or file that was transferred in SnF mode can arrive up to 15 days after the corresponding transfer completed. For this reason, if you transfer messages or files in SnF mode, to prevent a scenario from being deleted before its delivery notification arrives, set the cleanup period to at least 15 days (P15DT0H0M).
NULLValue

The value of this attribute specifies the system default flag. If the request or option set that is the source of a value for an option specifies this value for that option, the system default is used. The default is the string NULL.

BatchSize
The value of this attribute specifies the maximum number of scenarios that an MSIF service can process within a single transaction. The batch size is used during SnF system recovery, for restarting stopped transfers, for cleanup, for timed-out transfers, for transfers that expired from a business perspective, for monitoring the replication status of SnF transfers, and for monitoring the file transfer window to an SAG. The default value is 100. If the message broker issues an error message that indicates that the number of scenarios that an MSIF service tries to process in a single transaction is too large, then issue the following steps:
1. Reduce the value of this attribute.
2. Commit, approve, and deploy the change.
3. Retry the action.
ReplBatchSize
The value of this attribute specifies the maximum number of scenarios that the MSIF command service can alter in the MSIF database within a single transaction when determining SnF outbound transfers with an SnFInputTime that is earlier than the last replication time for the database in SIPN. The default is 100. If the message broker issues error message that indicates database timeouts:
1. Reduce the value of this attribute.
2. Commit, approve, and deploy the change.
3. Retry the action.
AutoCleanup

Specify this pseudo attribute if clean up processing for the internal database tables is to be done automatically every 60 minutes. This attribute does not affect manual cleanup.

EfaDataDirectory

The value of this attribute specifies the directory that contains the work and transfer directories. This applies only to FileAct file transfers.

EfaWorkDirectory

The value of this attribute specifies the subdirectory of the EfaDataDirectory in which the MSIF transfer service temporarily stores the files it is to send or has received. This applies only to FileAct file transfers.
If the MSIF transfer service is to process only requests that use SnF delivery mode, skip this step. Otherwise, for each message partner that is to process MSIF requests that use real-time delivery mode, map that message partner to a particular business OU. To do this:
1. In the copy of the script, for each message partner that is to process MSIF requests that use real-time delivery mode, create a copy of the following line:
```
add -ct DnfEfaMPMap -ou DNFSYSOU -co <MessagePartner> -attr BOU -val <BOU>
```
2. In each of the newly created lines, replace the following placeholders:
  
  <MessagePartner>
  
  The name of the message partner that is to be associated with a business OU. This name is case sensitive and must be identical to the name specified when the SAG was configured as described in Configuring message partners and Example: configuring an SAG for use by MSIF applications.
  
  <BOU>
  
  The name of the business OU with which the specified message partner is to be associated.
Ensure that all commands that are to be executed are activated, that is, that they are not preceded by a semicolon character (;).
Run the modified copy of the script. To do this, you must have the system configuration administrator (DniSA) role. Issue the following command:
```
dnicli -i instance -ou SYSOU -s DNI_SYSADM -cft dnfcocpy.cli -cp IBM-1047
```
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.