Re- index IFIX master data from mGramseva to Ifix

Owned by Taniya
Feb 13, 2024
7 min read

BackUp Data for Reindex : -

  • Take backup of existing data present in Index - ifix-fiscal-events

    GET ifix-fiscal-events/_search
    POST _reindex { "source": { "index": "ifix-fiscal-events" }, "dest": { "index": "ifix-fiscal-events-backup" } }

    Delete the data of existing index as the backup data is added in index - ifix-fiscal-events-backup

    POST /ifix-fiscal-events/_delete_by_query { "query": { "match_all": {} } }

  • Take backup of Db tables - event_posting_detail(mgramseva) and eg_ifix_fiscal_event(ifix)

    Delete the data from existing tables

  • Take backup of Currently running services builds

Added searchCriteria as fromDate and toDate according to transactiondate

Deploy the builds related to these services

Collection-Service : collection-services-db:v1.1.6-c46e2315-1

mgramseva-ifix-adapter service : mgramseva-ifix-adapter:PFM-4575-Taniya-455d7f45-77

Billing-service : billing-service-db:PFM-4575-93241a5c-35

Previous Builds:

Collection-Service: egovio/collection-services-db:v2.5-log4j-f0f010a-19

Mgramseva-ifix-adapter : dwssio/mgramseva-ifix-adapter:v1.1.0-17f8fe75-74

Billing-service : egovio/billing-service-db:v1.4.0-7fa6bc51-34

  • Increase the pods of Collection-Service,mgramseva-ifix-adapter service and Billing-service.

 

Payment Data Push :-

  • Check the count of payment data in egcl_payment table according to transactiondate.

  • Port-forwarding mgramseva-ifix-adapter.

  • Hit the payment data transfer api by provide fromDate and toDate to push the data wrt transactiondate.

  • check the logs of mgramseva-ifix-adapter for failures.

  • the data will be saved in event_posting_detail table where all the entries will show whether it's a success or failure.

  • the data which is success/pushed will be seen into eg_ifix_fiscal_event table.

 

  • The data which is success will be having tenantid - pb

  • The payment data will be pushed in event_type - Payment and Receipt

  • The count should match in both the tables event_posting_detail and eg_ifix_fiscal_event.

  • Check the data pushed in kibana index

Demand Data Push :-

  • The demand data is pushed according to tenant id’s and businesservice.

  • The data will push in two types of eventtype : Demand and Bill.

  • For ‘WS' businessservice,the eventtype will be Demand and for 'EXPENSE’ businessservice,the eventtype will be Bill.

  • In demand table,check all the demands wrt businesservice where status is ACTIVE.

    The businessservice includes :
    EXPENSE.CHLORINATION , EXPENSE.ELECTRICITY_BILL , EXPENSE.INCENTIVES ,EXPENSE.MACHINERY_REPAIR, EXPENSE.NEW_MACHINERY , EXPENSE.NEW_PIPELINE EXPENSE.OTHERS , EXPENSE.PIPELINE_REPAIR , EXPENSE.SALARY EXPENSE.WATER_TREATMENT , WS

  • Check the data for each of the tenant wrt businessservice.

  • Add businessservice and tenantid’s in api.

  • Port-forward mgramseva-ifix-adapter service and hit the api.

  • Check the count is matching with the tenants count.Also match the count in event_posting_detail table and eg_ifix_fiscal_event table.

  • Check the data pushed in kibana index.

  • Follow the same steps for other businessservices.