• Enrichers are used to enrich or fetch a value for a given field. Let’s say the field is Debit Account Id and enricher is Account Currency, so it means that the currency for that debit account Id needs to be fetched or enriched.
• Enricher can have enricher arguments. These arguments are passed when the enricher is invoked.
• Enrichers are of 2 types
  • Upload File Enrichers
  • Static arguments (enricherArgs) – Value is passed directly from template to enricher as label string
  • Dynamic arguments (enricherDynArgs) – Value is derived from a previous field of the record
• Extract (Response) File Enrichers

How Enrichers are used in File Upload ?

• In File Upload XML template, the field which will enrich other fields must have ‘enricher’ attribute. This attribute must not be specified for the fields which would be enriched.
• The value of this ‘enricher’ attribute is the ENRICHMENT_ID which is a column in table DIGX_FW_ENRICHMENTS_B. Currently OBAPI support only Java enrichers. Enrichers can be in any package but must implement the ‘IEnrichment’ interface.
• On the basis of the ‘enricher’ attribute value mapping is done from table DIGX_FW_ENRICHMENTS_B and the corresponding ENRICHMENT_VALUE column value is fetched and enrich() method of the specified Java class is invoked.

  Eg. Refer to the following figure of File Template : InternalFT.xml .

  
  
  
  Description of the illustration fileupld5.png
  
  

Static Enrichers

• In above template, the field name ‘debitAccountId’ has a enricher ACCTCURR with no enricherArgs. In this case DIGX_FW_ENRICHMENTS_B will be queried and search for ACCTCURRand ‘AccountCurrencyEnricher’ class is invoked.

  This enricher derives the debitAccountCurr. Hence this attribute must be present in the record DTO with its setters defined.

  
  
  
  Description of the illustration fileupld6.png
  
  
• The field name ‘valueDate’ has static enricherArgs ‘dd-MM-yyyy’ meaning that the date has to be specifically in ‘dd-MM-yyyy’ format. This value is simply available to the enricher for processing purpose. This enricher does not add any new field but simply modifies the value of the current field.
  
  
  Description of the illustration fileupld7.png
  
  

Dynamic Enrichers

If ‘enricherDynArgs’ is specified,

Eg. enricherDynArgs=”beneId~beneName” on beneficiary address field, the parser simply invokes getters on beneId and beneName fields and passes the values to the enricher in a map. It should be noted that these fields must be defined previously/above the beneficiary address field, so that parser has already completed the setter operation.

<Field name="beneId"/> 
 <Field name=" beneName"/>
<Field name="beneAddr" enricher="ADDRESSENRICHER" enricherDynArgs=" beneId~beneName "/>

Eg. Extract (Response) File Enrichers

Description of the illustration fileupld8.png

Enrichers can be added to response file templates. The enricher class is invoked in the same way as upload templates. Eg, in above case, localized error message need to be added to extracts from ‘errCode’. Extract enrichers do not support dynamic arguments

File Copy Configuration

In case of FCR/OBPM as host, for file level uploads in OBAPI, the files are generated in FCR/OBPM formats after approval at OBAPI end is complete. These files are stored in a directory on OBAPI server. For record level, service is used same as of single screen transactions.

FCR configs

1. Set this path as the value for prop_id = ‘FCORE_HANDOFF_FILE_PATH’ in the DIGX_FW_CONFIG_VAR_B table against the required entity (Empty folder with full permission).
2. Copying the file to host system using FTP (to rjsin folder).

   Provide the values for the below properties in the MSTPROPERTIES table of host schema:

   FU_IPADDRESS	IP of FCR machine
   FU_FTPFILEPATH	Filepath of rjsin where FCR will poll and pick files for further processing
   FU_USERNAME	FTP username of FCR machine. Needs to encrypted using AES key as in connecter.
   FU_PASSWORD	FTP password of FCR machine. Needs to encrypted using AES key as in connecter.

OBPM configs

1. Set this path as the value for prop_id = ‘UBS_HANDOFF_FILE_PATH’ in the DIGX_FW_CONFIG_VAR_B table against the required entity (Empty folder with full permission).
2. Copying the file to host system using FTP.

   Provide the values for the below properties in the MSTPROPERTIES table of host schema:

   FU_IPADDRESS	IP of OBPM machine
   FU_FTPFILEPATH	Filepath of folder where files need to be copied on OBPM machine. Files will be picked by invoking OBPM restful service(from OBAPI adapter) with configs given below
   FU_USERNAME	FTP username of OBPM machine. Needs to encrypted using AES key as in connecter.
   FU_PASSWORD	FTP password of OBPM machine. Needs to encrypted using AES key as in connecter.

3. OBPM file upload Restful service configurations.
   1. Set the value of the host IP and Port for which the REST API is to be invoked against the prop_id = ‘HOST_IP_UBSFU’ and ‘HOST_PORT_UBSFU’ in the DIGX_FW_CONFIG_VAR_B table against the required entity.
   2. Provide the values for the below properties in the MSTPROPERTIES table of host schema:
      • propname = ‘FU_FILETYPE’ - the type of file.
      • propname = ‘FU_HOSTCODE’ - the host code.
      • propname = ‘FU_RESTFILEPATH’ - the filePath provided in the rest payload as on OBPM machine.
      • propname = ‘FU_SRCCODE’ - the source code.
      • propname = ‘FU_TXNBRANCH’ - the transaction branch code.
4. Debtor BIC FI Configuration
   1. Provision to set Debtor BIC has been provided at entity level.
   2. The same can be configured in the following path by System Administrator user:
      1. Toggle menu → Configuration → System Configuration → Click on Continue → Select Entity → Dynamic Module Tab → File Upload
      
      
      
      Description of the illustration fileupld9.png