8.1 Post Implementation Steps for Data Migration from OWS to CS

Follow the subsequent steps to migrate/import customer data from OWS to OFS CS after installing the Sanction Application Pack:
  1. Create a DBLINK from the Sanctions Atomic Schema to the Enterprise Data Quality (EDQ) Config Schema. DBLINK act as a connection between the sanctions atomic schema and EDQ Config Schema.
    Sample DBLINK format:
    CREATE DATABASE LINK {dblinkname} CONNECT TO {edqconfiguser} IDENTIFIED BY {password} USING '(DESCRIPTION =(ADDRESS =(PROTOCOL = TCP)(HOST = {DBServername})(PORT = {portnumber}))(CONNECT_DATA =(SERVER = DEDICATED)(SERVICE_NAME = {servicename})))';
  2. Login into Sanction Config Schema.
  3. Run the following script in the Config Schema.
    select * from PR2_PROCESS_TASK_PARAMETER where V_PROCESS_ID='1672874121911' and N_TASK_ID =18;
  4. After running the script, in the PR2_PROCESS_TASK_PARAMETER table, update the DBLINK name in the V_TASK_PARAMETER_VALUE column with the DBLINK name created in step 1. See the below screen.

    Figure 8-1 PR2_PROCESS_TASK_PARAMETER table


    This image displays the PR2_PROCESS_TASK_PARAMETER table.

  5. To move the file data from OWS Server to the CS server, you need to run the OWSFileInsert.sh, which is present in ficdb/bin path.
    If you run the OWSFileInsert.sh shell script, it will be inserted in to the CS_APPLN_PARAMS table.
    Once the entries for the OWS_CS_URL attribute are done in CS_APPLN_PARAMS, if you run the OWS Migration batch from the Run Screen, the OWS File Migration task will read the details from CS_APPLN_PARAMS table and move the files from OWS Server to CS server.

    Figure 8-2 OWSFileInsert.sh shell script


    This image displays the OWSFileInsert.sh shell script.

  6. Go to the fichome folder in the Sanctions server.
    Sample file path:
    /scratch/ofsaabuild/BUILD_HOME/8.1.2.4.0/OFS_CMBT/packs/OFS_SANC/ dist_GENERIC/OFS_SANC/build/partial/fichome
  7. Open the OWSMIGRATION folder.
  8. Open DXI folder.
    The following files are available in the DXI folder:
    • OWSCS case migration utility.dxi
    • OWS_CS_Case_Migration.properties 9.
  9. Move the OWSCS case migration utility.dxi and OWS_CS_Case_Migration.properties file to local directory.
  10. Upload the OWSCS case migration utility.dxi file to the EDQ application from the local directory.
    For more information on Importing the OFS Customer Screening Projects, see Oracle Financial Services Sanctions Pack Installation and Configuration Guide.
  11. Upload the OWS_CS_Case_Migration.properties file to the following path in the EDQ server:
    /scratch/devuser/Oracle/Middleware/Oracle_Home/user_projects/domains/ base_domain/config/fmwconfig/edq/0edq.local.home/runprofiles
  12. After uploading the DXI file to the EDQ application. Open the DXI from EDQ director and select the Data Stores folder the Project Browser.
  13. Click AtomicDatasource.
    The Edit Data Store window is displayed.
  14. Update the sanctions data base details in the Edit Data Store configuration window and click OK.

    Figure 8-3 Edit Data Store


    This image displays the Edit Data Store.

  15. Click System Information in the Data Stores folder and select Sentry as source name.

    Figure 8-4 System Information page


    This image displays the System Information page.

  16. Go to the EDQ server and login to the Server Console from the Launchpad menu.
  17. Select OWS>CS case migration utility folder in the Server Console page.
  18. Run OWS > STAGE LOADING by using the OWS_CS_Case_Migration.properties file by Right-clicking OWS > STAGE LOADING.
  19. Select OWS_CS_Case_Migration from the Run Profile drop-down and click Ok to run the project. With the execution, the results will be populated inside a temporary setup table.

    Figure 8-5 Server Console page


    This image displays the Server Console page.

    Note:

    If there is a break or failure in running the OWS > STAGE LOADING, truncate the following tables and re-run step 17.
    • OWS_CS_CASE_ATTACHMENTS;
    • OWS_CS_CASE_COMMENTS;
    • OWS_CS_CASE_HISTORY;
    • OWS_CS_CASE_MASTER;
    • OWS_CS_CASE_ISSUES;
    • OWS_CS_CASE_RELATION;
    • OWS_CS_COUNTRY_PRHB;
    • OWS_CS_ENTITY_WL_DATA;
    • OWS_CS_ENT_CUST_DATA;
    • OWS_CS_IND_CUST_DATA;
    • OWS_CS_IND_WL_DATA;
    • OWS_CS_IND_CUST_ISSUES;
    • OWS_CS_ENT_CUST_ISSUES;
  20. After running the job, log in to Oracle Financial Services Customer Screening (OFS CS) application.
  21. Click Common Tasks, then click Rule Run Framework, and then click Run.
    The Run page is displayed.
  22. In the Run page, select the OWS_Migartion check box from the table and click Fire Run.
    The Fire Run page is displayed.

    Figure 8-6 Run page


    This image displays the Run page.

  23. Select single as the Request Type in the Run Definition section.
  24. Select the Batch value as Create & Execute and select the MIS Date in the Execution Mode section.
  25. Select Wait as No to create & execute the batch without any delay.
  26. Click Ok to execute the OWS_Migration batch.
    A message is displayed after successful batch execution. Click Close to go back to the Run page.

    Figure 8-7 Fire Run page


    This image displays the Fire Run page.

    After the successful execution, the OWS data will get migrated to CS and alert will be generated in the Customer Screening Alert List if there are matches. For more information on Alert List, see Alerts for Migrated OWS Watchlist data section in OFS Customer Screening User Guide.