19.1 Prerequisites

1. Ensure you have a separate Compliance Studio instance with bug 38066664 - ORACLE FINANCIAL SERVICES COMPLIANCE STUDIO 8.1.2.9.2 applied. For more information, see the Oracle Financial Services Compliance Studio Installation Guide.
   1. Model Training : Model Training happens in Sandbox schema.
      1. Ensure that you have a ECM schema that has proper historical data(events) and you create a Sandbox schema in the same database as that of ECM Schema.
      2. Ensure the Client selects the required Scenarios, Focus, and Jurisdiction from the historical data and train the Model.
   2. Create production workspace in Compliance Studio with same name as that of Production ECM infodom.
   3. Ensure that the BD source schema used for BD-ECM Batches is either same as that of ECM Schema or another schema in same database as that of ECM schema.

      If BD and ECM schema are in same DB and different schema then execute the below scripts:

      • Run this script in BD atomic schema.
        Replace ##ECM_ATOMIC_USER## with ECM atomic schema name.

        grant select on AMLES_EVENT_SCORE_DETAILS to ##ECM_ATOMIC_USER## 
        / 
        grant select on AMLES_EVENT_SCORE to ##ECM_ATOMIC_USER## 
        /

      • Run this script in ECM atomic schema.

        Replace ##BD_ATOMIC_SCHEMA## with BD atomic schema name.

        Create or replace synonym AMLES_EVENT_SCORE_DETAILS for ##BD_ATOMIC_SCHEMA##.

        AMLES_EVENT_SCORE_DETAILS
        /
        create or replace synonym AMLES_EVENT_SCORE for ##BD_ATOMIC_SCHEMA##.AMLES_EVENT_SCORE
        /
        

2. After the model is trained and deployed into production, configure the following:
   1. Create one user in Compliance Studio same as that of Production ECM.
      For example: ECMADMN
   2. Login to Configuration Schema and Update MMG_SERVICE_URL in nextgenemf_config table with BASE_URL value from nextgenemf_config table present in studio schema.
      For example: https://ofss-mum-873.snbomprshared1.gbucdsint02bom.oraclevcn.com:7002/cs
   3. If the target Compliance Studio is using secured connection, import the target server certificate to the ECM application java keystore and restart the services.
      Import the studio_server certificate to ECM java key store path.

      1. Copy the studio_server.cer (Present at <COMPLIANCE_STUDIO_INSTALLATION_PATH>/mmg-home/mmg-studio/conf) to ECM server.
      2. Run the below command by replacing the placeholders: keytool -importcert -keystore <JAVA_HOME>/lib/security/cacerts -storepass changeit -alias studio_ml -file <studio_certificate_path>/studio_server.cer

         Note:

         Note: studio_ml is the alias name used while creating the certificate.

         For example: keytool -importcert -keystore /scratch/ecm81210dev/jdk-11.0.10/lib/security/cacerts -storepass changeit -alias studio_ml -file /scratch/ecm81210dev/CompStudioCertificate/studio_server.cer

3. Restart all servers.
   A new component named MMG Pipelines is available in Components in Process Add or Edit screens for selecting the batches present in Compliance Studio.