3.3 Entity Resolution Use Case

This section describes the post-installation steps for Entity Resolution use case.

To perform post-installation activity for Entity Resolution:
  1. Navigate to the <PATCH_HOME>/files/SQLScripts directory.

    Note:

    <PATCH_HOME> indicates the path where patch contents are extracted.
  2. Execute the SQL script ER_DROP_MVIEW_OT.sql in the ER/FSDF schema.

    Note:

    The above SQL script should be executed only when the following conditions are met:
    1. The base installation is done using MATCHING_MECHANISM as OT.
    2. Entity Resolution jobs are already executed using CSA_8128 pipeline before patch application.
    3. User will continue to execute Entity Resolution jobs under same matching mechanism (i.e. OT) using CSA_8128 pipeline.
    4. If migration is performed by changing the MATCHING_MECHANISM, a cleanup is necessary before executing the ER Batch.
  3. Navigate to the <COMPLIANCE_STUDIO_INSTALLATION_PATH>/deployed/candidate-selection/utility/bin directory.
  4. Before triggering the next ER batch, execute CreateMViewAndIndex.sh script.

Upload Data Model

Entity Resolution requires a set of pre-staging tables to be available in the OFSAA staging area and the pre-configured FSDF staging model.

The table definitions are available in terms of a data model file which can be uploaded to OFSAA with the help of AAI's Data model management.

Note:

The ER_81290.ODM file is applicable only for Behavior Detection 8.1.2.9.0 version and CSA_8129 pipeline.
To upload the data model:
  1. Copy ER_81290.ODM from <COMPLIANCE_STUDIO_INSTALLATION_PATH>/entity-resolution/datamodels to <AAI Application Server>/<FSDF_STG_INFODOM>/erwin/erwinXML.
  2. Model Upload Using JSON/Erwin XML.
  3. Select Upload Mode as Sliced.
  4. Select Object Registration Mode as Incremental Object Registration.
  5. Select Upload File Typeas JSON.
  6. Select the erwin XML or Database XMLor ODMfile for upload from the drop-down list. Other options can be set to default and proceed to Upload.
    For more information on uploading the Data Model, see the Upload Business Model section in the OFS Analytical Applications Infrastructure User Guide.

    Note:

    If ER jobs are run in CS 8.1.2.8.0 with the CSA_8128 pipeline, then users should continue with the same pipeline after upgrading to CS 8.1.2.9.0. If there is a need to upgrade the ER/FSDF schema, users should clean up all ER runs with the CSA_8128 pipeline and use the CSA_8129 pipeline for ER runs.

    If CSA_8128 pipeline needs to be used with upgraded ER/FSDF schema then contact My Oracle Support.