3.1.8 Data Transfer Job
This topic provides information about the Data Transfer Job process.
All the records processed in the above batches with its status i.e success or failure (with failure reason) will be informed to the source system via this job. Source system can then analyze the records with failed status, correct the same and re-send again for processing.
This Job having two categories such as app configuration and trigger endpoint. Through the App configuration job, source and destination schema tables and column details are mapped. And Trigger endpoint job will transfer data from the source driver tables to destination system.
Table 3-16 Mandatory Headers
Parameter Name | Value | Mandatory | Description |
---|---|---|---|
appld | PLATOFDT | Yes | The application ID of the host service. |
Source Schema: CR_ENTITY
- DM_INBOUND_ENTITY_CREATION_DRIVER
- DM_ACCOUNT_UPDATE_DRIVER
- DM_ACCOUNT_PARTY_REL_UPDATE_DRIVER
- DM_PAYMENT_UPDATE_DRIVER
- DM_REPAYSCH_UPDATE_DRIVER
- DM_BILL_DETAIL_UPDATE_DRIVER
Destination Schema: As provided by the host system.
Destination Tables: As provided by the host system.
Specify following parameters while executing this batch:
Table 3-17 Data Transfer sample configuration:
Endpoint | Configurations |
---|---|
Host location | http://host:port/plato-fast-data-transfer-service/configurations/applications/ObrlDataResponse/ObcrDataAck |
Method | POST |
Header |
|
Request Body |
|
Trigger endpoint
Table 3-18 Trigger endpoint
Endpoint | Configurations |
---|---|
Host location | http:// host:port/obcr-data-exchange-services/transfers/ObrlDataResponse/ObcrDataAck?runDate=02042018&operation=T&branchCode=BCR |
Method | POST |
Header |
|
Request Body |
|
Parent topic: Entity Creation