1. Administration Guide
  2. Run the ISO20022 Batch Screening
  3. Steps to Run a ISO20022 Batch

7.2 Steps to Run a ISO20022 Batch

  1. Create a file named <<BATCH_DATE>_RUN<<RUN_NUMBER>>_ STG_TRANSACTIONS_ENTRY_<<DIGIT>>.json.
    Where
    • <BATCH_DATE> is date used for “ISO20022BatchScreening” Batch run. Format:yyyyMMdd.
    • <RUN_NUMBER>is Any Positive number used for “ISO20022BatchScreening” Batch run.
    • <DIGIT> is Any Positive number to represent the uniqueness of file. E.g.20241017_RUN1_ STG_TRANSACTIONS_ENTRY_1.json

    Note:

    You can create multiple input json files for single batch run.
  2. File contents must be in valid json format.
    1. Example of Single Transaction in a file.
      [
      {
"rawMessage":"<<RAW_MESSAGE_STRING>>",
"businessDomainCode":"GEN",
"jurisdictionCode":"AMEA",
"messageDirection":"INBOUND",
"additionalData" :
        {         
        "MESSAGE_DIRECTION":"INBOUND" 
        }
    } 
]
    2. Example of Multiple Transactions in a file.
      [
      {
"rawMessage":"<<RAW_MESSAGE_STRING>>",
"businessDomainCode":"GEN",
"jurisdictionCode":"AMEA",
"messageDirection":"INBOUND",
"additionalData" :
        {         
        "MESSAGE_DIRECTION":"INBOUND" 
        }
},
{
"rawMessage":"<<RAW_MESSAGE_STRING>>",
"businessDomainCode":"GEN",
"jurisdictionCode":"AMEA",
"messageDirection":"INBOUND",
"additionalData" :
        {         
        "MESSAGE_DIRECTION":"INBOUND" 
        }
}
]
  3. Once the files are created, and place the input files inside the ISO20022_Batch_InputData_Upload_Utility folder.
  4. Create an empty filewatcher text file named “<<BATCH_DATE>>_filewatcher.txt" inside the utility folder.

    Where <BATCH_DATE> is date used for “ISO20022BatchScreening” Batch run. Format:yyyyMMdd.

    Note:

    1. The File Watcher text file with corresponding batch date is mandatory for the batch to run.
    2. If any input files created for a new date, filewatcher should also be created with same date.
  5. Add the prefix name of input json files in filename.txt. Refer to the Prerequisties section to add the file name prefixes.
  6. To upload the input data files to Object storage, Open the terminal, and run ./cto.sh <<BATCH_DATE>>
    For Example: ./cto.sh 20241017

    Note:

    1. The cto.sh file contains Object Storage PAR URL as a variable “objstore”. This URL get refreshed every day in admin console. Use the latest Object Storage PAR URL from admin console using Access the Object Storage Pre-authenticated URLAccess the Object Storage Pre-authenticated URL.
  7. Once the input file upload is successful, Open Application URL and Navigate to Batch Administration>Scheduler.
  8. In the Schedule Service Screen, click ‘Schedule Batch’ Navigation and under Execute Tab, then select the Batch as “ISO20022BatchScreening”.
  9. Click Edit Parameters button. The Edit Dynamic Params Dialog appears.
  10. Under the Batch Parameters, for Param $BATCHDATE$, enable MISDATE and select the date as <<BATCH_DATE>> which is given in the input file name.
  11. For Param $RUN$, enter the <<RUN_NUMBER>> which is given in input file name.
  12. Click Save.
  13. To run the batch, click the Execute button.
  14. A confirmation popup appears. Click the Monitor button to monitor the batch.
  15. Once the batch is successful, call the following API with appropriate headers to get the download URL.
    GET <<BASE_URL>>/feedback-service/iso20022-batch/getFeedbackParURL?runNumber=<<RUN_NUMBER>>&batchDate=<<BATCH_DATE>>
    Refer API Documentation for More Information.

    Note:

    The Download URL expiry date is 15 days. If any expiry happens, use the Following API to get the new Download URL.

    POST <<BASE_URL>>/feedback-service/iso20022-batch/ uploadFeedbackToObjectStorage?runNumber=<<RUN_NUMBER>>&batchDate=<<BATCH_DATE>>

  16. Using the URL, download the immediate feedback zip file which contains json file(s) with content as transaction token, input data, and feedback data for each transaction.
  17. Then, navigate to Schedule Batch and under Execute tab, select the batch as “ISOBatchScreeningToCaseManagement”.

    Note:

    1. Make sure the “$DATAORIGIN$” Batch Parameter used is same in both the batches.
    2. As a pre-requisite for ISOBatchScreeningToCaseManagement Batch, “Maintenance” batch must be executed once in a setup for corresponding “$DATAORIGIN$” before triggering the above batch. It is a one-time activity in the application.
  18. Then, click Execute.
  19. Click Monitor to monitor the batch.
  20. Once the batch is successful, cases are generated for given transactions.
  21. Use the Following Feedback API to get the feedback with case Id or to get the final feedback.
    GET <<BASE_URL>>/feedback-service/Feedback/findByID?messageType=3&transactionToken=<<TRANSACTION_TOKEN>>

    Where <TRANSACTION_TOKEN>> - It can be obtained in immediate Feedback json file for each transaction.

    Refer API Documentation for More Information.

    Table 7-1 Task Details for ISO20022BatchScreening

    Task ID Task Name Task Description
    Task1 StartDataLoad Starts the Batch
    Task2 DataLoadingFileTransfer Downloads Input Files from the Object Storage and Transfers it to the FSS (File Storage Service) location.
    Task3 DataLoadingFileScanner Scans the files in the FSS location for virus detection.
    Task4 TransFilterPipeline Reads the data from json files in the FSS location and insert the data into the batch repository and the batch transaction tables.
    Task5 TransactionInputProcess Fetches the input data from the batch transaction table, then processes it and insert them into pre-processing tables.
    Task6 ISO20022DataTransform Transforms the input data for provided rules under each webservice and persists them into transformed table.
    Task7 TransactionSourceDataLoad Loads the transformed data as indexes into Matching Engine.
    Task8 ISO20022BulkMatching Performs screening of data, scoring, decision making, generating Immediate Feedback, highlighting Raw data, and Creating TF Alerts.
    Task9 GatherStats Gathers statistics for the loaded tables.
    Task10 EndDataLoad Ends the Batch.

    Note:

    1. Both batches must be run successfully, one after the other.
    2. If the batch run fails because of the server down issue, you must try to restart the batch. It will re-start from the failed task.
    3. Re-run option will create a new run for the batch with new batch run Id.