Requirements to enable FSM Module in a new evironment
Was this helpful?
Was this helpful?
To enable FSM module in any new environment, we would need to perform certain steps. Considering an AWS account is already setup, following are the steps to be followed:
Update the with the following requirements:
Indexer config: We will need following indexer files for setting up any module
Persister config Persister files required:
Searcher config
Pdf config Data config: Format config:
Reports Also mention the path of the above report file .
Dashboard configs => =>
Add all configs required
Add all Actions/endpoints required for fsm as mentioned in this . Add all actions with respect to core and business-services as well, like those of - egov-user, egov-mdms-service, apportion-service, collection-service, billing-service, egov-location, egov-common-masters, egov-idgen, egf-master, egov-user-event, otp services, access, egov-workflow-v2, data-uploader, egov-hrms, filestore-service, pdf-service, egov-pdf, report, localization-service, egov-persister, egov-indexer, egov-searcher, eg-pg-service, dasboard-analytics, dashboard-ingest, digit-ui, fsm, fsm-calculator, vendor, vehicle.
Add Role-Action mapping in file
Add required Roles for the respective FSM module in
Add , , , , , , , , , , , folders with their respective files.
Also add ULB/city specific data in their respective folders, for instance, create a folder and add the respective data files like Slum.json, UrcConfig.json, ZeroPricing.json required.
Note: The data sepecific to any ULB needs to be collected from the ULB officials and need to be present in mdms level. Refer the ULB specific data documentation and updation/upsertion
Deploy all required core-services builds to support this municipal-services(FSM and its dependent services). The core-services include: egov-accesscontrol, egov-common-masters, egov-data-uploader, egov-document-uploader, egov-enc-service, egov-filestore, egov-idgen,egov-indexer, egov-localization, egov-location, egov-mdms-service, egov-notification-mail, egov-notification-sms, egov-otp, egov-persister, egov-pg-service, egov-searcher, egov-url-shortening, egov-user, egov-workflow-v2, pdf-service, report, user-otp, zuul
Deploy all required business-services builds to support this municipal-service(FSM and its dependent services). The business-services include: billing-service, collection-services, dashboard-analytics, dashboard-ingest, egf-instrument, egf-master, egov-apportion-service, egov-hrms.
Deploy this municipal-service “fsm” as well as dependent municipal-services: fsm-calculator, vendor, vehicle, inbox, egov-user-event.
Add all the helm charts with respect to the business-services, core-services and municipal-services. Refer .
Add DevOps level changes in the evironment file. Refer . Add all the paths for files in the configs in the environment file. For instance, add the the path of indexer, persister and searcher files, etc. Make sure to add required properties at each service level as defined in the above mentioned environment file.
Upsert the required localizations. Refer for detailed steps.
Upsert the workflows as mentioned in the .
Upsert the SMS templates as localizations in your environment as well as update them in the SMS portal being used by the state. For detailed infomation,