Consolidated Event Layer (CEL) Schema Creation and Configuration

For customers that do not use Enterprise Case Management (ECM), the application takes events that were generated for the Behavior Detection (BD), KDD_, tables and the Studio, FCC_AM, tables and then consolidates them into a new common structure that is the same as the ECM event layer. From there, the connectors can be built into third-party case management systems or the data can be used for overall reporting. The point of the Common Event Layer (CEL) is that all the event data from Anti-money laundering (AML) PE, that combines Studio and AML generated events, is in a common table structure.

Note:

This feature is applicable for release versions 8.1.2.9.4 and above.

Create the CEL Schema

Create the CEL schema:
CREATE USER <CEL_SCHEMA> 
IDENTIFIED BY <PASSWORD>
DEFAULT TABLESPACE AIF_USER_TS 
TEMPORARY TABLESPACE TEMP 
PROFILE DEFAULT   
QUOTA UNLIMITED ON AIF_USER_TS 
QUOTA UNLIMITED ON AIF_USER_TEMP_TS;

Grants for the CEL Schema

GRANT CONNECT TO <CEL_SCHEMA>; 
GRANT CREATE SESSION TO <CEL_SCHEMA>; 
GRANT CREATE PROCEDURE TO <CEL_SCHEMA>; 
GRANT CREATE SEQUENCE TO <CEL_SCHEMA>; 
GRANT CREATE TABLE TO <CEL_SCHEMA>; 
GRANT CREATE TRIGGER TO <CEL_SCHEMA>; 
GRANT CREATE VIEW TO <CEL_SCHEMA>; 
GRANT CREATE MATERIALIZED VIEW TO <CEL_SCHEMA>; 
GRANT CREATE SYNONYM TO <CEL_SCHEMA>; 
GRANT CREATE RULE TO <CEL_SCHEMA>; 
GRANT CREATE ANY TRIGGER TO <CEL_SCHEMA>; 
GRANT DROP ANY TRIGGER TO <CEL_SCHEMA>; 
GRANT CREATE ANY TYPE TO <CEL_SCHEMA>; 
GRANT EXECUTE ON DBMS_SCHEDULER TO <CEL_SCHEMA>; 
GRANT CREATE JOB TO <CEL_SCHEMA>;

Configure Consolidate Event Layer (CEL)

Note:

Event Layer can be deployed only after successful installation.
Perform the following steps to deploy the event layer:
  1. Update the value of DEPLOY_EVENT_LAYER in additional_config.sh from N to Y.
  2. Create a new workspace, datastore, and target schema. Add the target schema to wallet.
  3. Update the CEL configuration values in the <COMPLIANCE_STUDIO_PATH>/bin/config.sh file.
  4. Navigate to <COMPLIANCE_STUDIO_PATH>/bin and execute the update command: ./compliance-studio.sh --update or ./ compliancestudio.sh -u
  5. Once Compliance Studio is updated:

    Execute the command in the following location:

    <COMPLIANCE_STUDIO_PATH>/deployed/event-service/bin

    To trigger the ODM upload, execute the following command:

    ./deployEventLayer.sh "Y" "{APP_USERNAME}" "{WORKSPACE_ID}" "{DATASTORE_ID}" "{USER_ACTION}" Example: ./deployEventLayer.sh "Y" "APP_USERNAME" "WORKSPACE_ID" "DATASTORE_ID" "UPLAD" "CEL_TARGET_ALIAS"

    To receive the ODM upload status, execute the following command:

    ./uploadODM.sh "{APP_USERNAME}" "{WORKSPACE_ID}" "{DATASTORE_ID}" "GET_STATUS" "{MODEL_ID}" Example: ./uploadODM.sh "APP_USERNAME" "WORKSPACE_ID" "DATASTORE_ID" "GET_STATUS" "2001"

Population of the Event Layer

Before executing the batch, confirm that the ODM upload was successful by using the following commands:
  1. To receive the ODM status, run the following query : ./uploadODM.sh "{APP_USERNAME}" "{WORKSPACE_ID}" "{DATASTORE_ID}" "GET_STATUS" "{MODEL_ID}" APP_USERNAME, WORKSPACE_ID, DATASTORE_ID, USER_ACTION. The attributes are explained in the Parameters of config.sh file table in the Configure the config.sh file topic. topic.
  2. When the ODM upload is triggered, it returns a model ID. Use that model ID here to fetch the ODM upload status. For example: ./uploadODM.sh "APP_USERNAME" "WORKSPACE_ID" "DATASTORE_ID" "GET_STATUS" "2001"
To execute the batch to populate or consolidate the events into the CEL:
  1. Click Launch Workspace where the event layer is deployed on the UI.
  2. Navigate to the Orchestration menu and click Schedule Batch.
  3. Select the required batch from the drop-down list.:
    • CEL_TABLE_POPULATION_BATCH: This batch orchestrates the CEL connector; from FCC_AM* to CEL.

      CEL can source the data from the schema in which the behavioral models or custom scenarios have generated events to a schema which can be connected to any third party case management systems

    • BD_TABLE_POPULATION_BATCH: This batch orchestrates the Business Detection (BD) connector to CEL. This is for customers who do not have ECM but want to export the events to a third-party case management system. This will be the desired layer for the third-party case management system to build a connector on.

      BD connectors can source the business data from the BD schema to the target BD schema in the third party case management systems

  4. Click Edit Parameter and update the required parameters. You can change the param value and save the changes to the batch.
    For CEL the following parameters must be edited:
    • $BATCHDATE$ : This must be set to the MIS date for which the Behavioral Model or Custom Scenario was executed.
    • EVENTTYPELIST: If it has no other default value, then it must be set to AML
    • DATAORIGINLIST: If it has no other default value, then it must be set to SGDLY;DLY.

    You can also schedule it as per the FIC_MIS_DATE via the Scheduler Service UI.

  5. Click Save.
  6. Click Execute to run the batch.

    To monitor the batch, see the Monitor Batch or Batch Groups topic in the OFS CS User Guide on the Oracle Help Page.

Redeploying the Event Layer

Redeploying the event layer is performed during two scenarios;
  • If the initial deployment is performed with incorrect CEL parameters or configurations, then, redeployment is required after correcting these parameters.
  • In cases where the database is unavailable or the schema is inaccessible, redeployment is required once the issue has been resolved.
Perform the following steps to redeploy the event layer:
  1. Create a new workspace, datastore, and target schema.

    Note:

    Ensure the names for workspace and datastore are different from the previous deployment.
  2. Update the configuration values in the <COMPLIANCE_STUDIO_PATH>/bin/config.sh file.
  3. Execute the update command: ./compliance-studio.sh --update or ./compliancestudio. sh -u.
  4. Once Compliance Studio is updated:

    Execute the command in the following location:

    <COMPLIANCE_STUDIO_PATH>/deployed/event-service/bin

    To trigger the ODM upload, execute the following command:

    ./deployEventLayer.sh "Y" "{APP_USERNAME}" "{WORKSPACE_ID}" "{DATASTORE_ID}" "{USER_ACTION}" Example: ./deployEventLayer.sh "Y" "APP_USERNAME" "WORKSPACE_ID" "DATASTORE_ID" "UPLAD" "CEL_TARGET_ALIAS"

    To receive the ODM upload status, execute the following command:

    ./uploadODM.sh "{APP_USERNAME}" "{WORKSPACE_ID}" "{DATASTORE_ID}" "GET_STATUS" "{MODEL_ID}" Example: ./uploadODM.sh "APP_USERNAME" "WORKSPACE_ID" "DATASTORE_ID" "GET_STATUS" "2001"

  5. Perform the steps mentioned in the Population of the Event Layer section to execute the batch.