Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

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:

  1. Update the Configs repo with the following requirements:

  2. Add all mdms configs required

    • Accesscontrol-Actions-Test
      Add all the actions required for fsm as mentioned in this file.
      Add all those actions with respect to user-service, egov-mdms-service, apportion-service, collection-service, billing-service, egov-location, egov-common-masters, egov-idgen, egf-master, 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.

    • Accesscontrol-Role Action:
      Add all the roleaction mappings in roleactions.json file

    • Accesscontrole-roles:
      Add all the required roles for the respective FSM module in roles.json

    • Add BillingService, DIGIT-UI, DataSecurity, FSM, Vehicle, Vendor, Workflow, common-masters, dss-dashboard, egf-master, egov-hrms , tenant folders with their respective files.

    • Also add ULB/city specific data in their respective folders, for instance, create a folder angul and add the respective content required.

  3. Deploy allCore-services builds to support this municipal-service(FSM)

  4. Deploy this municipal-service(fsm) as well as depedent municipal-services(fsm-calculator, vendor, vehicle, inbox).







  • No labels