Deploy ifix-migration-toolkit-db:develop-b7a2050-13
to ifix
environment
Port forward to the ifix-migration-toolkit pod
The following common request body is used to hit the ifix-migration-toolkit endpoints:
Government master data is moved to MDMS. Please manually copy the government(tenant) data to the tenants
master of tenant
module. Here is a link to a sample tenants master.
First, deploy the latest image of the ifix-master-data-service
(So that the tables get created in PostgreSQL.)
Deploy plain search docker image of ifix-master-data:
Ensure ifix-master-data-persister is configured in the egov-persister
Hit the Chart of Account migrate endpoint of the migration-toolkit
With this, we will be performing migration from MongoDB to both, PostgreSQL and ElasticSearch. Data will be read from MongoDB using fiscal-event-service's plain search api, and pushed to a kafka topic.
From there, the data will reach PostgreSQL using egov-persister.
From kafka-topic data will pass through ifix-es-pipeline. After that ifix-es-pipeline will post the processed data to the next kafka topic in the pipeline. From there, egov-indexer will read from the topic and index the data onto ElasticSearch.
First, deploy the latest image of the fiscal-event-service
(So that the tables get created in PostgreSQL.)
Follow the instructions mentioned in the ifix-es-pipeline project's README to setup the ES mapping before performing the migration.
Deploy plain search docker image of fiscal-event-service:
Deploy the latest image of ifix-es-pipeline
Ensure fiscal-events-persister is configured in egov-persister
Ensure ifix-fiscal-event-indexer is configured in egov-indexer
(Ensure ifix-migration-progress is configured in egov-persister to record the progress of the migration. In case of any failures during migration, with this, it will resume the migration from where it left off. )
Hit the Fiscal Event migrate endpoint of the migration-toolkit