This migration will require the following tasks to be performed:

iFIX Core

1. Copy data to ElasticSearch

   • Fiscal Events

2. Copy data to PostgreSQL

   • iFIX Master Data Service

     • Government

     • Chart of Accounts

   • Fiscal Events

iFIX Adapter

Apart from iFIX-Core, the other services relying on MongoDB were also migrated to PostgreSQL. So they will also need to be migrated.

1. Department Entity Service

   • Department Hierarchy Level

   • Department Entity

2. Adapter Master Data Service

   • Expenditure

   • Department

   • Project

Release Summary

iFIX Core v2.3 contains the following changes.

• The data stores have been shifted:

  1. From MongoDB to PostgreSQL

  2. From Druid to ElasticSearch

Enhancements

Document Resources and Links

​All content on this page by eGov Foundation is licensed under a Creative Commons Attribution 4.0 International License.

Migration to DIGIT architecture primarily involves the following changes to iFIX-Core:

1. Transactional DB is switched from MongoDB to PostgreSQL

2. Analytics DB is switched from Druid to ElasticSearch

   1. Correspondingly, the dashboard is switched from Metabase to the DSS dashboard

1. Deploy ifix-migration-toolkit-db:develop-2557812-9 to mgramseva environment.

2. Port forward to the ifix-migration-toolkit pod

Instruction

The following common request body is used to hit the ifix-migration-toolkit endpoints:

{
    "requestHeader": {}
    "tenantId": "<tenant-id>"
}

Migrate ifix-department-entity-service

1. First, deploy the latest image of the ifix-department-entity-service

   1. (So that the tables get created in PostgreSQL.)

2. Deploy plain search docker image of ifix-department-entity-service:

   Copy

   egovio/ifix-department-entity-service-db:mongodb-plainsearch-b12bf24-4

3. Ensure department-entity-persister.yml is configured in the egov-persister.

4. (Ensure department-entity-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. )

5. Hit the Department Hierarchy migrate endpoint of the migration-toolkit

   Copy

   /ifix-migration-toolkit/department_hierarchy/v1/_migrate

6. Hit the Department Entity migrate endpoint of the migration-toolkit

   Copy

   /ifix-migration-toolkit/department_entity/v1/_migrate

Migrate adapter-master-data-service

1. First, deploy the latest image of the ifix-department-entity-service

   1. (So that the tables get created in PostgreSQL.)

2. Deploy plain search docker image of ifix-department-entity-service:

   Copy

   egovio/adapter-master-data-service-db:mongodb-plainsearch-b12bf24-5

3. Ensure adapter-master-data-service.yml is configured in egov-persister.

4. Hit the Department migrate endpoint of the migration-toolkit

   Copy

   /ifix-migration-toolkit/department/v1/_migrate

5. Hit the Expenditure migrate endpoint of the migration-toolkit

   Copy

   /ifix-migration-toolkit/expenditure/v1/_migrate

6. Hit the Project migrate endpoint of the migration-toolkit

   Copy

   /ifix-migration-toolkit/project/v1/_migrate

With the iFIX v2.3-alpha update, some of the DIGIT core services also need to be deployed. The builds of the same are also listed below. These have been picked from DIGIT-v2.7.

​All content on this page by eGov Foundation is licensed under a Creative Commons Attribution 4.0 International License.

Release Summary

IFIX 2.3-alpha release details and highlights are available in the below release notes.

All content on this page by is licensed under a .

1. Deploy ifix-migration-toolkit-db:develop-b7a2050-13 to ifix environment

2. Port forward to the ifix-migration-toolkit pod

Instruction

The following common request body is used to hit the ifix-migration-toolkit endpoints:

{
    "requestHeader": {},
    "tenantId": "<tenant-id>"
}

Migrate ifix-master-data-service

Migrate Government

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.

Migrate Chart of Account

1. First, deploy the latest image of the ifix-master-data-service

   1. (So that the tables get created in PostgreSQL.)

2. Deploy plain search docker image of ifix-master-data:

   Copy

   ifix-master-data-service-db:mongodb-plainsearch-b12bf24-7

3. Ensure ifix-master-data-persister is configured in the egov-persister

4. Hit the Chart of Account migrate endpoint of the migration-toolkit

   Copy

   /ifix-migration-toolkit/coa/v1/_migrate

Migrate fiscal-event-service: Fiscal Events

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.

1. From there, the data will reach PostgreSQL using egov-persister.

2. 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.

Instructions:

1. First, deploy the latest image of the fiscal-event-service

   1. (So that the tables get created in PostgreSQL.)

2. Follow the instructions mentioned in the ifix-es-pipeline project's README to setup the ES mapping before performing the migration.

3. Deploy plain search docker image of fiscal-event-service:

   Copy

   egovio/fiscal-event-service-db:mongodb-plainsearch-1bca621-7

4. Deploy the latest image of ifix-es-pipeline

5. Ensure fiscal-events-persister is configured in egov-persister

6. Ensure ifix-fiscal-event-indexer is configured in egov-indexer

7. (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. )

8. Hit the Fiscal Event migrate endpoint of the migration-toolkit

   Copy

   /ifix-migration-toolkit/fiscal_event/v1/_migrate

With this update, the iFIX Adapter services now depend on some of the DIGIT Core services. egov-persister should be deployed and configured.

All content on this page by is licensed under a .

Release Summary

MGramSeva iFix Adapter v2.3 has the below changes.

• Data store moved from MongoDB to ElasticSearch

• Non-backward compatible minor change to the /_create and /_update of department-entity and project master.

​All content on this page by eGov Foundation is licensed under a Creative Commons Attribution 4.0 International License.