2.5 File Processing

This topic describes about the instructions to trigger the file process.

Inbound File Processing done through Interface Definition and bulk file processing in ODT will now have pre-defined file formats (flat file or JSON) for each service. The inbound files (adhering to the corresponding formats) needs to be placed in a folder (configuration setting provided for the path) for processing. A scheduler job will pick up these files on scheduled intervals based on a pre-configured frequency and process the files. Errors if any will be written to a file in the 'Error' folder in the same path. For Outbound extracts, a service endpoint is exposed which needs to be invoked manually to generate the extracts.

A flatfile template for each maintenance service will be placed in the server path. For example: /scratch/work_area/ELCM148/Files/FileTemplate

Users should create a data file with the service name itself (eg: Liability,Collateral,Facility,etc.) and provide the data in the given flatfile template format.

The service name to be used for each maintenance screen will be available in the common schema table name OBELCM_PP_TM_CO_BULK_OPERATIONS.

The data file should be placed in the server path which is a plato configuration property (For example: /scratch/work_area/ELCM148/Files/Import). This file can be a flatfile(.txt) or a json(.json) file.

A scheduler batch job will run at the configured frequency and process the files placed in the above configured path.

Any failures in the file processing will be written to an error file and placed in the Error folder the same path mentioned above (For example: /scratch/work_area/ELCM148/Files/Errors).

Processed files will be moved to the Processed folder adjacent to the data filin the same path mentioned above (For example: /scratch/work_area/ELCM148/Files/Processed).

The scheduler job has to be configured as below:

  1. Click Task Management, and under Task Management, click Create Task.

    Table 2-64 FileProcessingJob

    Task Name Task Definition
    FileProcessingJob appId:::OBELCMCOLLAT;microServiceName:::obelcm-pp-collateral-batch-services;contextRoot:::obelcm-pp-collateral-batch-services;invokeBatchFrm:::Y;isFacilityRevalReq:::N;jobName:::obelcm-pp-collateral-batch-services;targetJob:::obelcm-files;runDate:::01012000;branchCode:::ELCMBr;
  2. Click Task Management, and under Task Management, click Configure Tasks.
    Select Schedule Radio button

    Task Name: FileProcessingJob

    Cron Expression: Based on the frequency required [Sample: 0 * * * * *(for every one minute)]

    For exporting the data as a file, an endpoint is provided which should be triggered to get the file in the export folder of the server path which is a plato configuration property (For example: /scratch/work_area/ELCM148/Files/Export).

    The service for which the data needs to be exported should be provided in the request param. (For Example: ?serviceName=Liability)

    This service name for the maintenance screen will be available in the common schema table name OBELCM_PP_TM_CO_BULK_OPERATIONS.

    Endpoint Details:

    HTTP METHOD: POST

    URL: https://hostname:portname/api-gateway/obelcm-common-maintenance-services/service/v14.8.1.0.0/commons/export?serviceName=Liability

    Sample Curl:

    curl --location 'https://hostname:portname/api-gateway/obelcm-common-maintenance-services/service/v14.8.1.0.0/commons/export?serviceName=Liability' \

    --header 'appId: OBELCMCOMMON' \

    --header 'userId: OBELCMUSER1' \

    --header 'Content-Type: application/json' \

    --header 'entityId: DEFAULTENTITY' \

    --header 'branchCode: B01' \

    --header 'multiEntityAdmin: N' \

    --header 'Accept: application/json' \

    --header 'Authorization: ••••••' \

    --header 'sourceCode: ELCM'\

    --data ''

Parent topic: Limits and Collateral