4.13 Scheduling the Customer Screening Run Job
To execute a Customer Screening Run job, follow these steps:
- Navigate to the
FCI_DB_HOME/bin
directory. - Execute the command
/EDQInsert.sh <INFODOM NAME>
.This step is used to register the EDQ server details. You must replace the INFODOM NAME placeholder with your domain name. - Enter the following details in the console where the command is run:
- EDQ Server IP
- EDQ Server Direct Port number (JMX port number). This value must be 8090.
- EDQ Server User Name
- EDQ Password details
Figure 4-24 EDQ Details
- Create and authorize a new ECM user who has no case privileges. For example,
CSConnect
. For information on how to create or add and authorize a user, see the User Administrator section in the Oracle Financial Services Analytical Applications Infrastructure User Guide.Note:
In the first login as a new user, you are prompted to change the password. - Execute the command
/EDQInsert.sh <INFODOM NAME>
again only if you are doing a pack- on-pack installation of Enterprise Case Management (ECM) on Sanctions and the ECM URL is unavailable. An entry is made in the ATOMIC schema in thecs_appln_params
table. - Copy the following run profiles from the
<domain_name>/edq/oedq.local.home / runprofiles/
directory in the WinSCP server to theFIC_DB_HOME/conf
directory:watch list-management.properties
customer-screening.properties
external-entity-screening.properties
customer-screening-real-time.properties
- Load the stage table data for the customer-related tables. For more information, see Loading Data.
- In the Run page, select the
CS_Data_Load_Event_Generation
run and click Fire Run. The batches must be run in the order mentioned in the following table. It is not mandatory to run all the batches.Table 4-2 Sequence of Batches to be Run
Sequence Batch Name Description 1 CS_EDQ_Watchlist_Management This job is used to run the watch list management project and start real-time screening in EDQ based on the run profile parameters.
This job must be run daily.
2 CS_EDQ_Watch list_Analyze This job is used to check the data quality of the downloaded watch list. 3 CSBusinessDataLoad This job is used to load data from the staging tables to the business tables. 4 CS_Data_Load_Event_Generation This job is used to match customer data with the downloaded watch list data and to generate alerts. 5 Oracle_CS_Zipper_Processing This job will move the data from the source database to the consolidated database and create an alert based on the Customer.
NOTE: The Oracle_CS_Zipper_Processing batch is only applicable in the L1 Investigation.
Figure 4-25 Run page