...
After creation of payment response with receipt data, it has been pushed into kafka topic “egov.collection.migration” migration-batch” and with the persister, payment data is inserted into tables egcl_payment, egcl_paymentdetail, egcl_bill, egcl_billdetial, egcl_billaccountdetail .
...
https://github.com/egovernments/configs/blob/master/egov-indexer/payment-indexer.yml
persister config -
https://githubraw.githubusercontent.com/egovernments/configs/blob/master/egov-persister/collection-migration-persister.yml?token=AGAOX7TAAE6QPRZBXU3QZV266URNW
Please get these promoted before initiating the migration process. Migration happens through an API call, add role-actions based on your requirement. Otherwise, port-forwarding should work.
Find the API details below:
Endpoint: /collection-services/payments/_migrate?batchSize=20100&offset=
Body:
{
"RequestInfo": {
"apiId": "Rainmaker",
"action": "",
"did": 1,
"key": "",
"msgId": "20170310130900|en_IN",
"ts": 0,
"ver": ".01",
"authToken": "a6ad2a1b-821c-4688-a70e-4322f6c34e54"
} Collection-service build:- collection-services-db:16-COLLECTION_MIGRATION-0a5e432Billing
While restarting migration due to any failure, take the value of offset and tenantId printed in the logs and resume the migration process where it ended.
/collection-services/payments/_migrate?batchSize=100&offset=200&tenantId='pb.tenantId'
Collection-service build:- billing collection-serviceservices-db:89-COLLECTION_BULK_BILLSMIGRATION-8744cdc e9701c4