Introduction
This document mainly covers all the steps that one needs to do for setting up a new instance of eDCR (Development Control Regulations). Say when a new State is to be set up, there are some activities to be executed in a defined order. Setting up an instance of an application server and configuring customer-specific rules, and data, etc are a few of the key activities.
Prerequisites
eDcr service set up needs to be done.
Centralized Server hosting all the ULBs within a state
All ULBs access the software over the browser or over API call.
Uniform code base supporting all the ULBs for the state. City-specific changes are maintained using client-specific implementation repositories.
A separate schema for each ULB in the Databasedatabase.
Configurations and Setup
How to set up a client implementation repository
Branch out and create a client edcr implementation repository from https://github.com/egovernments/digiteGov-dcr-bpaservice master repository. For example, you can refer Refer https://github.com/egovernments/eGovegov-dcrclientdcr-implementation how client for the client implementation setup has been done.
After creating a client implementation repository, If you want to over-ride override rules processing for features, then have to create a project under egov directory like egov-client-impl.
How to override rule processing across the state, citydistrict, ULB, and grade wise for a feature Please refer the document, Development Control Rules (Digit-DCR)
The client-specific rules are configurable in the individual client implementation module. Here the rules are fetched by state wise, district wise, ULB wise, or grade-wise. The EG_CITY table, master data used to decide these values. Eg: https://github.com/egovernments/egov-dcr-client/blob/master/egov/egov-client-impl/src/main/java/org/egov/client/edcr/Far_Client.java Here filename to be add as Far_Assam.java for assam state rules.
How to Setup New State and ULB’s
...
The following API’s are used in the integration of eDCR system,
Extract Plan API
Purpose: This API will extratc the building plan drawing(dxf) file send along and gives the extracted data.
-
Scrutinize Plan API
Purpose: This API will scrutinize the building plan drawing(.dxf) file send along and gives the plan scrutiny result as response along with a unique eDCR number on successful processing.
Fetch scrutinized plan details API
Purpose: This API is used to fetch the details of the plan that is already scrutinized in the system by providing a transaction number or a eDCR number.
Extract Plan API
Purpose: This API will extract the building plan drawing(.dxf) file send along and gives the extracted data.
Refer YAML definition API contracts https://github.com/egovernments/digit-bpa/blob/master/egov/egov-edcr/dcrasservice.yaml
Note:
For the above APIs one must use state domain URL and in the contract tenantId of concern city have to send be passed to scrutinize multiple cities.
Should One should not use city domain URL to scrutinize or fetch , still if you use and scrutinize won’t get any response and will failplan if used that way, the response will be empty.
The tenantId , if you are using used should follow {state_name.city_name} naming convention, then the state_name what you are sending passed in the request and city code in the state schema must be the same.