Splitting Jobs Using Multiple EDQ Servers

D Splitting Jobs Using Multiple EDQ Servers

You can split jobs across multiple servers to reduce the time taken to process many customers, for example, one million or more.

Note:

These steps are applicable only if you plan to use multiple EDQ servers for customer screening. If you want to use the default setup, that is, only a single EDQ server, see Scheduling the Customer Screening Run Job.

Some examples are as follows:

If one server is used to process the watch lists and another server is used to process the entity names.
If one server is used to process data of individuals and another server is used to process data of entities during different times of day.
Note:
1. Provide the EDQ user name and password in the cs_appln_params table.
2. Run the select * from cs_edq_servers query in your SQL query tool to verify the server details.

To split jobs using multiple servers, follow these steps:

Navigate to the FIC_DB_HOME/bin directory.
Execute ./EDQServerInsert.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 Name
- EDQ server IP
- EDQ Server Direct Port number (JMX port number). This value must be 8090.
- EDQ Server User Name
- EDQ Password details
Figure D-1 EDQ Details
Duplicate the CS_Data_Load_Event_Generation batch in the Run page. To do this, copy the CS_Data_Load_Event_Generation batch and create another batch.
Follow these steps to access the Run page:
1. Login as the administrator. The Financial Services Analytical Applications Customer Screening home page appears.
  
  Figure D-2 Financial Services Analytical Applications Customer Screening Home Page
2. Click the hamburger icon to view the Application Navigation List.
  
  Figure D-3 Application Navigation List
3. From the Application Navigation List, select Common Tasks, then select Rule Run Framework, and then select Run. The Run page appears.
In the Run page, follow these steps to create a duplicate batch:
1. Select the CS_Data_Load_Event_Generation run and click Copy. The Run page opens in copy mode.
  
  Note:
  You must select the segment folder for the Sanctions pack in the Folder field to proceed.
  
  Figure D-4 Run Page in Copy Mode
2. Enter a new run code or alter the existing value in the Code field. For example, code can be CS_Data_Load_Event_GenerationD.
3. Enter a new run name or alter the existing value in the Code field. For example, name can be CS Data Load And Event Generation.
  
  Note:
  The run name and run code values can be the same.
4. Click Next to go to the next page and confirm the name.
5. Click Save.
After you click Save, the new run name appears in the Run page.

Figure D-5 New Run Name in Run Page
Duplicate the CS_E2E_Start_Batch, CS_Call_Customer_Screening, and CS_E2E_End_Batch processes in the Process page.

Figure D-6 Process Page
Follow these steps to access the Process page:
1. Login as the administrator. The Financial Services Analytical Applications Customer Screening home page appears.
  
  Figure D-7 Financial Services Analytical Applications Customer Screening Home Page
2. Click the hamburger icon to view the Application Navigation List.
  
  Figure D-8 Application Navigation List
3. From the Application Navigation List, select Common Tasks, then select Rule Run Framework, and then select Process. The Process page appears.
To duplicate each process, follow these steps:
1. For the CS_E2E_Start_Batch process:
  1. In the Process page, select CS_E2E_Start_Batch and click Copy. The Process page opens in copy mode.
    
    Note:
    You must select the segment folder for the Sanctions pack in the Folder field to proceed.
  2. Enter a new process code in the Code field and a new process name in the Name field. You can also alter the existing process code or name. For example, CS_E2E_Start_Batch_den.
  3. Click Save.
2. For the CS_Call_Customer_Screening process:
  1. In the Process page, select CS_Call_Customer_Screening and click Copy. The Process page opens in copy mode.
  2. Enter a new process code in the Code field and a new process name in the Name field. You can also alter the existing process code or name. For example,CS_Call_Customer_Screening_den.
  3. Click Save.
3. For the CS_E2E_End_Batch process:
  1. In the Process page, select CS_E2E_End_Batch and click Copy. The Process page opens in copy mode.
  2. Enter a new process code in the Code field and a new process name in the Name field. You can also alter the existing process code or name. For example, CS_E2E_End_Batch_den.
  3. Click Save.
  After you click Save, the new process names appear in the Process page.
  
  Figure D-9 New Process Names in Process Page
Update the group name for the CS_E2E_Start_Batch_den and CS_E2E_End_Batch_den processes. To do this, run the following query:
```
select * from cs_processing_group
```
Change the parameter for the CS_E2E_Start_Batch_den process. To do this, follow these steps:
1. Select the duplicated process created in the earlier step and click Edit. The Process page opens in edit mode.
2. Click Component. The Component Selector window appears.
3. Click the drop-down list in line with the F_CS_BATCH_RUN task. The Parameters window appears.
  
  Figure D-10 Parameter for the CS_E2E_Start_Batch Process
4. Change the ORACLECS parameter to the applicable data origin or processing name.
Change the parameter for the CS_E2E_End_Batch_den process. To do this, follow these steps:
1. Select the duplicated process created in the earlier step and click Edit. The Process page opens in edit mode.
2. Click Component. The Component Selector window appears.
3. Select the drop-down list in line with the F_CS_BATCH_RUN task. The Parameters window appears.
  
  Figure D-11 Parameter for the CS_E2E_End_Batch Process
4. Change the ORACLECS parameter to the data origin or processing name.
To change the parameters for the CS_Call_Customer_Screening_den process, follow these steps:
1. Select the duplicated process created in the earlier step and click Edit. The Process page opens in edit mode.
2. Click Component. The Component Selector window appears.
3. Select the drop-down list in line with the CallEDQ task. The Parameters window appears with the following values:
```
"runprofileName=customer-screening1.properties","RunLabel=customerscreening","
JobName=MAIN","ProjectName=Customer-
Screening","edqServerName=SERVER_2","condition=and AGE_YR_CT>20 and
BIRTH_DT <= @$~20 June 1972@$~"
```
  Figure D-12 Parameters for the CS_Call_Customer_Screening_den Process
4. Change the following parameters:
  1. Run profile name
    Example: runprofileName=customer-screening1.properties"
  2. EDQ server name. If you do not change the server name, it is replaced with the server name in thecs_appln_params table.
    Example: "edqServerName=SERVER_2"
  3. Condition. By default, a single condition is provided. Use and to give more than one condition.
    Example: "condition=and AGE_YR_CT>20 and BIRTH_DT <= @$~20 June 1972@$~"
Note:
1. It is not mandatory to provide a condition.
2. Provide the expression @$~ to use alphanumeric characters for fields such as customer birth date. For example, "condition=and AGE_YR_CT>20 and BIRTH_DT <= @$~20 June 1972@$~".
Replace the new batches in the Run page. To do this, follow these steps:
1. Select CS_Data_L_Event_Generation_Den and click Edit. The Run page opens in edit mode.
2. Click the Selector drop-down list and select Job. The Component Selector window appears.
  
  Figure D-13 Parameters for the CS_Call_Customer_Screening_den Process
3. In the List hierarchy window, expand the Transformation Rules node.
4. Expand the Processes node and then the TFLSEGMENT node.
5. In the Tasks table, select the original processes, which areCS_End_To_End_Start_Batch, CS Customer Screening Call, and CS_End_To_End_End_Batch. These processes must be selected one at a time.
6. Click Move . The selected batches are displayed in the TFLSEGMENT node.
7. In the List table, select the new processes, which are CS_End_To_End_Start_Batch_den, CS Customer Screening Call den, andCS_End_To_End_End_Batch_den.
8. Click Remove . The selected batches are displayed in the Tasks table.
9. Click OK.

The duplicate jobs are now split across servers using the CS_End_To_End_Start_Batch, CS Customer Screening Call, and CS_End_To_End_End_Batch batches.