Run Alert Suppression API

Follow these steps to run the Alert Suppression API service.

  1. Configure the Alert Suppression API using the Alert Suppression configurator:
    1. Login to APP Server and navigate to $FIC_HOME/database/db_tools/
    2. Open log4j2.xml file with a notepad and update the String from @ORION_DB_DBTOOLS_PATH@ to {FIC Home Path}/database/db_tools

      Note:

      {FIC Home Path} should be replaced with the exact FIC Home path (For example: /scratch/ofsaaapp/BDECM812/BDECM812)
    3. Login to APP Server and navigate to $FIC_HOME/database/db_tools/bin (For example, cd $FIC_HOME/database/db_tools/bin)
    4. Executealsup_configurator.sh (Step: .alsup_configurator.sh )

      Note:

      Run the script only once to configure API URL, username, password, and other parameters.
    5. Provide the URL, Username, Password, and BICTypeLength of the Alert Suppression REST Service as received from AML Case Management System. It will update the alert suppression configuration file, serviceconfig.xml (Located at $FIC_HOME/database/db_tools/mantas_cfg/ in APP Server)

      Note:

      BICTypeLength in serviceconfig.xml should be same as in BDF.xml(File is located at path $FIC_HOME/bdf/config/BDF.xml in APP Server)
    6. The Behavior Detection Alert Suppression API provides the option to filter by Business domain(s). TUser can configure the serviceconfig.xml by updating the tag <Domain> with Business domain(s). When configured, only filtered data as per specified Business Domain(s) will flow into Behavior Detection Alert Suppression Tables (kdd_auto_suppr_alert) from AML Case Management System.
      • <Domain>d</Domain> for single domain
      • <Domain>d,a</Domain> for multiple domains

      Note:

      Multiple domains should be comma delimited.
    7. The Behavior Detection Alert Suppression API provides the option to filter according to Jurisdiction. The tpconfig.xml can be configured by updating the tag <Jurisdiction> with Jurisdiction(s). When configured only filtered data as per specified Jurisdiction(s) will flow into Behavior Detection Alert Suppression Tables (kdd_auto_suppr_alert) from the AML Case Management System.
      • <Jurisdiction>AMEA</Jurisdiction> for single Jurisdiction,
      • <Jurisdiction>AMEA,IN</Jurisdiction> for multiple Jurisdictions

      Note:

      Multiple Jurisdictions should be comma delimited.
  2. After configuring Alert Suppression, navigate to $FIC_HOME/database/db_tools/bin directory of APP Server and Execute alsup_dataload.sh.
    For example,
    1. cd $FIC_HOME/database/db_tools/bin
    2. ./alsup_dataload.sh

    Note:

    • Before running the 507 post processing jobs, run the alsup_dataload.sh script everyday which populates alert suppression data and it is full load.
    • The template 507 (for alert suppression) must be run every day for suppressing alerts based on the active suppression rules created during the previous script execution (alsup_dataload.sh).
    On successful execution, the console will display the message "Job Completed Successfully…" and return code will be 0 in $FIC_HOME/database/db_tools/logs/alertsuppression.log file. The Alert Suppression information will flow from the AML Case Management System to Behavior Detection data base tables (kdd_auto_suppr_alert).
    If any error occurs during execution of tp_dataload.sh, the status code will be -1 in the $FIC_HOME/ database/db_tools/logs/alertsuppression.log file.

    Note:

    After execution the rejected records will be archived at each execution in a separate log file whose complete details with path will be given in $FIC_HOME/database/db_tools/logs/ alertsuppression.log file.
    Each alert suppression record received from REST Service with status codes Approved and Expired (SUPAPP and SUPEXP) will get stored as AC, IAC respectively in Behavior Detection Alert suppression table.