1. Administration and Configuration Guide
  2. Entity Resolution
  3. Executing the ER Jobs
  4. Perform Matching

4.4.2 Perform Matching

Job

The ER_Run_Bulk_Similarity_Job.sh triggers the matching engine to generate the matches in the match output table for rulesets saved against a pipeline-id argument for fetching rulesets.

Steps

Note:

Make sure to check the fcc_er_matching and fcc_er_manual_match tables before proceeding. Check the logs accordingly if there are no records in fcc_er_matching and fcc_er_manual_match generated.
  1. Navigate to <COMPLIANCE_STUDIO_INSTALLATION_PATH>/deployed/ficdb/bin directory.
  2. Run the following command:
    nohup ./ER_Run_Bulk_Similarity_Job.sh "<PIPELINE_ID>"
"<ER_SCHEMA_WALLET_ALIAS>" "<MATCH_TYPE>" "<BATCH_GROUP>" "<RUN_TYPE>" &

    Note:

    <BATCH_GROUP> refers to FCC_PROCESSING_GROUP table in the Compliance Studio schema.

    For example, you can use the following command for CSA_8128 pipeline.

    FSDF 8128 version: nohup ./ER_Run_Bulk_Similarity_Job.sh "CSA_8128" "ER_SCHEMA_PP_ALIAS" "FullLoad" "CSA_812" "RUN" &

    For more information about parameters, see the Parameters for Entity Resolution Job execution section.

    Note:

    If the Bulk Similarity Edge job fails internally due to Incorrect schema details and then returns a success message. You can check the log file in <COMPLIANCE_STUDIO_INSTALLATION_PATH>/deployed/logs for more details on the failure.