3.2 OFS Know Your Customer (KYC)

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

If OFS KYC is installed:

  1. Import all assessments under $FIC_HOME/IPE/KYC.

    For example: ./RTIImport.sh $FIC_HOME/IPE/KYC/OFS_KYC_RTIExport_AcceleratedRereview.xml ##AMINFODOM## OFS_KYC false

  2. If you are executing DI / KYC Daily batch, enter the following values in the Parameters option.

    [MODELID]=PROD,[VERSION]=0,[APP_ID]=OFS_KYC

  3. 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/OFS_KYC_RTIExport_AcceleratedRereview_WithAomalyDetectionML.xml ##AMINFODOM## OFS_KYC false

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

  6. If RAOR deployment is required, navigate to aFIC_HOME/raor_processing and run ./ant.sh and deploy the RAOR war file.
  7. Execute the following script in BD Atomic Schema and then replace the placeholders.
    <USER_PATCH_DIR>/<unzipped_folder>/post_scripts/KYC_ECM_Synonyms.sql
  8. Ignore the this step if you are applying patch on top of 8.1.2.8.0 or higher 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
  9. To configure and deploy the internal watchlist-related Services, follow these steps:
    1. Create the WAR file by changing to the FIC_HOME/ingestion_manager/scripts directory and executing createWatchListWAR.sh. This will create the mantas.war file which contains the watch list service.
    2. Deploy the mantas.war file to the web application server. Any context path can be used, but the KYC application expects it to be at /mantas. The full path leading to the exploded WAR file will be referred to as <Service Deployed Directory> below.
    3. Modify the file: <Service Deployed Directory>/WEB-INF/fuzzy_ match/mantas_cfg/install.cfg and change the path in the fuzzy_ name.B.stopword_file and fuzzy_name.P.stopword_file properties from: <FIC_ HOME>/ingestion_manager to: <Service Deployed Directory>/WEB-IN.
    4. Modify the file: <Service Deployed Directory>/WEB-INF/config/install.cfg and change the Creating and Deploying the Applications Pack Web Archive Post Installation Configuration path in the log.message.library, log.categories.file.path, and log4j.config.file properties as specified in step 3.
      1. For WebLogic, copy the following contents into setDomainEnv.sh located under $WL_HOME/user_projects/ domains/<user_domain>/bin/setDomainEnv.sh after replacing the placeholders - <WATCHLIST_DEPLOYED_AREA> and <ORACLE_ HOME>. 
        FIC_HOME=<WATCHLIST_DEPLOYED_AREA> ORACLE_HOME=<ORACLE_HOME>
export FIC_HOME export ORACLE_HOME
KDD_PRODUCT_HOME=${FIC_HOME}/WEB-INF/fuzzy_match export KDD_PRODUCT_HOME
JAVA_LIB_HOME=${KDD_PRODUCT_HOME}/lib/kddcore.jar:${KDD_ PRODUCT_HOME}/
lib/log4j-1.2.12.jar
export JAVA_LIB_HOME
LD_LIBRARY_PATH=${KDD_PRODUCT_HOME}/lib:${ORACLE_ HOME}/
lib:${LD_LIBRARY_PATH}
export LD_LIBRARY_PATH
      2. For Tomcat, create file setenv.sh under <TOMCAT_INSTALLED_AREA>/bin/ and copy the following contents after replacing the place holders - <WATCHLIST_DEPLOYED_AREA> and <ORACLE_ HOME>. 
        FIC_HOME=<WATCHLIST_DEPLOYED_AREA> ORACLE_HOME=<ORACLE_HOME>
export FIC_HOME export ORACLE_HOME
KDD_PRODUCT_HOME=${FIC_HOME}/WEB-INF/fuzzy_match export KDD_PRODUCT_HOME
JAVA_LIB_HOME=${KDD_PRODUCT_HOME}/lib/kddcore.jar:${KDD_ PRODUCT_HOME}/
lib/log4j-1.2.12.jar
export JAVA_LIB_HOME
LD_LIBRARY_PATH=${KDD_PRODUCT_HOME}/lib:${ORACLE_ HOME}/
lib:${LD_LIBRARY_PATH}
export LD_LIBRARY_PATH
      3. For WebSphere, copy the following contents into .profile file (create a .profile file if it is not already existing) of the user after replacing the placeholders - <WATCHLIST_DEPLOYED_AREA> and <ORACLE_ HOME>. 
        FIC_HOME=<WATCHLIST_DEPLOYED_AREA> ORACLE_HOME=<ORACLE_HOME>
export FIC_HOME export ORACLE_HOME
KDD_PRODUCT_HOME=${FIC_HOME}/WEB-INF/fuzzy_match export KDD_PRODUCT_HOME
JAVA_LIB_HOME=${KDD_PRODUCT_HOME}/lib/kddcore.jar:${KDD_ PRODUCT_HOME}/
lib/log4j-1.2.12.jar
export JAVA_LIB_HOME
LD_LIBRARY_PATH=${KDD_PRODUCT_HOME}/lib:${ORACLE_ HOME}/
lib:${LD_LIBRARY_PATH}
export LD_LIBRARY_PATH
    5. Restart the web application server.

      Note:

      Update the proper LD_LIBRARY_PATH based on your OS:
      • For Linux: 
        export LD_LIBRARY_PATH=$KDD_PRODUCT_HOME
      • For Solaris SPARC:
        export LD_LIBRARY_PATH=/usr/lib/
lwp:$KDD_PRODUCT_ HOME/lib:$ORACLE_ HOME/
lib:/usr/ucblib/sparcv9:/scratch/JAVA_7/
jdk1.7.0_ 75/jre/lib/sparcv9/server:/
scratch/JAVA_7/jdk1.7.0_ 75/jre/lib/
sparcv9:/scratch/JAVA_7/jdk1.7.0_ 75/jre/
lib/sparcv9/native_ threads:/usr/local/lib/
sparcv9:/scratch/JAVA_ 7/jdk1.7.0_75/jre/
lib/:$LD_LIBRARY_PATH