7.20 Configurations for ECM Integration (Applicable only for Promote to Case Action in KYC

Perform the following procedure to integrate Enterprise Case Management (ECM) with OFS BD application.

The process varies when OFS ECM and OFS BD are installed in different databases and OFS ECM and OFS BD are installed within the same database.

Note:

If you are performing pack on pack installation of OFS ECM v8.0.7.0.0 on existing OFS BD v8.0.7.0.0, the following columns with provided values are generated in the KDD_PRCSNG_BATCH_CONTROL table. For further Batch Execution and Ingestion, these columns must be truncated.

  • PRCSNG_BATCH_ID --1
  • DATA_DUMP_DT - 11/16/2017 3:16:07PM
  • PRCSNG_BATCH_NM -ECM
  • EOD_PRCSNG_BATCH_FL -Y

ECM and BD Installed in Different Databases

If the ECM and BD are installed in different databases, follow these steps:

  1. Replace placeholders with corresponding values and execute the following SQL query. This has to be executed by the AM sys user, who has SYSDBA role:
    Create public database link AMDBLINK connect to <ECM_ATOMIC_USER> IDENTIFIED BY <ECM_ATOMIC_PWD> using '<CM_TNS_ENTRY>'
    • <ECM_ATOMIC_USER> - This variable must be replaced with ECM atomic schema User ID.
    • <ECM_ATOMIC_PWD> - This variable must be replaced with ECM atomic User Password.
    • <CM_TNS_ENTRY> - This variable must be replaced with the ECM Database TNS Entry.
  2. Update the file install.cfg available in the location <FIC_HOME>/database/db_tools/mantas_cfg with the correct values for the following variables:
    • casemng.schema.owner - ECM Atomic schema user
    • caseschema.schema.owner - ECM Atomic schema user
    • extract.schema.case - ECM Atomic schema user
    • load.schema.case - ECM Atomic schema user
  3. Update the file db_variables.cfg available in the location <FIC_HOME>/database/db_tools/ mantas_cfg with the correct values for the following variables:
    • case_schema_owner - ECM Atomic schema user
    • AMINFODOM - Alert Management Infodom name.
  4. Add the path of the SQL files in the DB_LINK.cfg and DB_LINK_CASE.cfg files. The path for DB_LINK.cfg file is installer/OFS_BD_PACK/OFS_BD/BDPostScripts/differentDB. If not, an error is displayed.
    For example, in the.cfg file one of the SQL files is called TABLE_SYNONYM_DBLINK.sql, so in front of this file user has to mention the path of the SQL file. So the value in the .cfg file will be as follows: 
    /scratch/ofsaaapp/BE85E87/installer/OFS_BD_PACK/OFS_BD/BDPostScripts/differentDB/TABLE_SYNONYM_DBLINK.sql
  5. Execute the following commands using the DB builder utility:
    1. Navigate to the differentDB folder mentioned above.
    2. Run the following command to execute the .cfg file using the db builder utility:
      ../../../../../<FIC_HOME>/database/db_tools/bin/run_dbbuilder_utility.sh
        /installer/OFS_BD_PACK/OFS_BD/BDPostScripts/differentDB/DB_LINK.cfg
    ../../../../../ indicates that you need to go back to the <FIC_HOME> path from the differentDB
      folder.
  6. To run the DBLink_CASE.cfg file, modify the utils.database.urlName=parameter name in the install.cfg file with the ECM JDBC URL.
  7. In the utils.database.urlName= parameter, replace the existing JDBC URL with the Enterprise Case Management (ECM) JDBC URL and execute.
    ../../../../../<FIC_HOME>/database/db_tools/bin/ run_dbbuilder_ utility.sh
        /installer/OFS_BD_PACK/OFS_BD/BDPostScripts/differentDB/DB_LINK_CASE.cfg

    Note:

    If After you execute the above command, replace the ECM JDBC URL with the Alert Management (AM) JDBC URL.

ECM and BD Installed in the Same Database

If the ECM and BD are installed in the same database, follow these steps:

  1. Update the install.cfg file available in the location <FIC_HOME>/database/db_tools/mantas_cfg with the correct values for the following variables:
    • casemng.schema.owner - ECM Atomic schema user
    • caseschema.schema.owner - ECM Atomic schema user
    • extract.schema.case - ECM Atomic schema user
    • load.schema.case - ECM Atomic schema user
  2. Updatethe db_variables.cfg file available in the location <FIC_HOME>/database/db_tools/ mantas_cfg with the correct values for the following variables:
    • case_schema_owner - ECM Atomic schema user
    • AM_INFODOM - Alert Management Infodom name.
  3. Add the path of the SQL files in the SAME_DB.cfg file. The path for SAME_DB.cfg file is

    <download_dir>/OFS_BD_PACK/OFS_AML/BDPostScripts/sameDB. If not, an error is displayed.

    For example: in the .cfg file one of the SQL files is called TABLE_SYNONYM.sql, so in front of this file you must mention the path of the SQL file. So the value in the .cfg file will be as follows: <download_dir>/OFS_BD_PACK/OFS_AML/BDPostScripts/sameDB/ TABLE_SYNONYM.sql

  4. Execute the following commands using the DB builder utility:
    1. Navigate to the same DB folder mentioned above.
    2. Run the following command to execute the .cfg file using the db builder utility:
      ../../../../../<FIC_HOME>/database/db_tools/bin/ run_dbbuilder_utility.sh /installer/OFS_BD_PACK/OFS_BD/BDPostScripts/ sameDB/SAME_DB.cfg
../../../../../ indicates that you need to go back to the <FIC_HOME> path from the sameDB folder.