3.2 OFS Know Your Customer (KYC)

This section describes the KYC-related post-installation steps.

Note:

  • For new BD/KYC installation, follow these steps:
    • Import all assessment (xml) files located in $FIC_HOME/IPE/KYC, then run the DI batch.
    • Once the DI batch is completed successfully, import all assessments (xml) files located in $FIC_HOME/IPE/KYC/8.1.2.6.0/Simulation.
    • Start executing the regular batches.

If OFS KYC is installed:

  1. Navigate to $FIC_HOME/ficapp/common/FICServer/bin and execute the following executables after replacing the INFODOM placeholder:
    1. ./RTIImport.sh $FIC_HOME/IPE/KYC/8.1.2.6.0/Simulation/OFS_KYC_RTIExport_AcceleratedRereview.xml ##AMINFODOM## OFS_KYC false
    2. ./RTIImport.sh $FIC_HOME/IPE/KYC/8.1.2.6.0/Simulation/OFS_KYC_RTIExport_ChangeInRiskModel.xml ##AMINFODOM## OFS_KYC false
    3. ./RTIImport.sh $FIC_HOME/IPE/KYC/8.1.2.6.0/Simulation/OFS_KYC_RTIExport_ModelBasedAssessment.xml ##AMINFODOM## OFS_KYC false
    4. ./RTIImport.sh $FIC_HOME/IPE/KYC/8.1.2.6.0/Simulation/OFS_KYC_RTIExport_RAOR_ModelBasedAssessment.xml ##AMINFODOM## OFS_KYC false
    5. ./RTIImport.sh $FIC_HOME/IPE/KYC/8.1.2.6.0/Simulation/OFS_KYC_RTIExport_RAOR_RuleBasedAssessment.xml ##AMINFODOM## OFS_KYC false
    6. ./RTIImport.sh $FIC_HOME/IPE/KYC/8.1.2.6.0/Simulation/OFS_KYC_RTIExport_RuleBasedAssessment.xml ##AMINFODOM## OFS_KYC false
  2. Perform this step only if Oracle Financial Services Compliance Studio is installed. Do not import it if Compliance Studio is not installed. Navigate to $FIC_HOME/ficapp/common/FICServer/bin and execute the following executable after replacing the INFODOM placeholder.

    ./RTIImport.sh $FIC_HOME/IPE/KYC/8.1.2.6.0/Simulation/OFS_KYC_RTIExport_AcceleratedRereview_WithAomalyDetectionML.xml ##AMINFODOM## OFS_KYC false

  3. Execute the following utility to synchronize data in SMS tables:
    1. Go to $FIC_HOME/utility/AppPckMastSynch/bin.
    2. Open putty session and run the following commands one by one:
      1. ExportPackName=OFS_BD_PACK
      2. ./AppPckMastSynch.sh
  4. To add a new task in KYC daily batch:
    1. Log in as an Admin user.
    2. Navigate to the Common Tasks section, select the Rule Run Framework, and then select Process.
    3. Select IPEPopulateIP from the table list and click Edit.
    4. Click Component in the new window.
    5. Expand Transformation Rules from Available Components.
    6. Click Database Functions-Transformations and expand it.
    7. Move POPULATE_CUST_PROCESSING_IP to the right into Tasks in ROOT.
    8. In the right box, move the new task POPULATE_CUST_PROCESSING_IP after POPULATE_IP_KYC.
    9. Click OK.
    10. Click Precedence.
    11. Select POPULATE_CUST_PROCESSING_IP from the drop down.
    12. Select POPULATE_IP_KYC in the Available Precedence object and move it to the right.
    13. Click OK and Save.
  5. Enter the following values while executing the IPEKYCRun daily batch in the Parameters option.
    1. [MODELID]=PROD
    2. [VERSION]=0
    3. [APP_ID]=OFS_KYC
  6. Once the above steps are done, create the following EAR/WAR file and redeploy this new WAR on the web application server. See Oracle Financial Services Behavior Detection Applications Pack Installation Guide Release 8.1.2.0.0 for steps related to deployment.
    1. JSONToTablePersistenceUtility
    2. TabletoJSONService
    3. InitiateOnboardingService
    4. GenerateCaseInputService

      Note:

      For using Websphere Server, remove all the jackson* Jars from the following folder before creating OFSAAI EAR/WAR file:

      $FIC_HOME/ficweb/webroot/externalib/WEB-INF/lib

  7. If RAOR deployment is required, navigate to aFIC_HOME/raor_processing and run ./ant.sh and deploy the RAOR war file.
  8. Execute the following script in BD Atomic Schema and then replace the placeholders.
    <USER_PATCH_DIR>/<unzipped_folder>/post_scripts/KYC_ECM_Synonyms.sql
  9. Ignore the this step if you are applying patch on top of 8.1.2.8.0 and 8.1.2.9.0 ML patches.
    1. Replace V_JRSDCN_CD ('#JR#') column value in APPLN_PARAMS table for V_PARAM_IDENTIFIER = 'KYC_SAR_ACTN_CTGRY';
    2. Replace V_JRSDCN_CD ('#JR#') column value in APPLN_REREVIEW_PARAMS table for N_RULE_ID = '1070';

      Note:

      Replace the #JR# value with Jurisdiction value
  10. Execute the following scripts in Compliance Studio schema:

    insert into mmg_app_menu_mapping(V_APP_ID,V_MENU_CODE) select 'KYC',V_MENU_CODE from MMG_MENU;

  11. Execute the following scripts in Behavior Detection schema:
    1. update aai_setup_props set V_PROP_VALUE = 'TRUE' where V_PROP_NAME = 'REFERRER-POLICY-ENABLED';
    2. update aai_setup_props set V_PROP_VALUE = '##Studio Server IP:Port##/ ' where V_PROP_NAME = 'ALLOWED-REFERRER-URLS';

      For example:

      update aai_setup_props set V_PROP_VALUE = 'http://10.34.110.111:8001/' where V_PROP_NAME = 'ALLOWED-REFERRER-URLS';

      Note:

      You must enter / after the port number.
    3. Update aai_validator_expression SET v_reg_expression = '[A-Za-z0-9_.]*' WHERE V_EXP_TYPE_CODE = 'data_source_exp' AND v_reg_expression = '[A-Za-z0-9_]*';