I API to create the Alerts in the Zipper Alerts table (FCC_ZCS_ALERTS)

Multiple CS Instances are used for an ad-hoc Screening of Customer and External Entity from the Real-time Screening UI. Following are the steps to configure these systems to create zipper alerts in separate Zipper UI Instances:
  1. Navigate to ##FIC_HOME##/ficdb/bin folder of CS instance, used for ad-hoc screening of Customer and External Entity from Real-time Screening UI.
  2. Execute EDQInsert.sh bypassing infodom along with it.

    Example: ./EDQInsert.sh TFLTINFO

  3. Initially, enter the EDQ server details.
  4. If you want to use the Enterprise Case Management Application (ECM) or Customer Screening Alert Management (CSAM) as an L1 investigation for Real-Time Screening, enter CSAM.
  5. Enter the URL of the Zipper UI instance used for Zipper alerts, and if the Customer Screening Alert Management (CSAM) application is in the same installation, enter N.
  6. Enter the user name and password to access the Zipper UI instance URL.
  7. Now, if you perform an ad-hoc screening of Customer and External Entity from Real-time Screening UI from CS instance, it will create zipper alerts in Zipper UI instance.
  8. Follow the above steps 1 to 7 in all the multiple CS instances used for ad-hoc screening of Customer and External entity from Real-time Screening UI.

    Note:

    The source systems are configured with the Rest URL of the CS Instance used for ad-hoc screening of Customer and External Entity from the Real-time Screening UI. In this case, it will still use the same configuration done in the above steps 1 to 7 and creates zipper alerts in the Zipper UI instance.