Migrate Old Boundary Data - Steps

Overview

This document provides information on migrating location data from an older JSON-based configuration to a newly developed boundary service. A boundary-migration service has been created to facilitate this process. Users can migrate the data to the new boundary service by calling a single API.

Steps

Below is the step-by-step procedure for the same:-

  1. Import the boundary migration service from here in an IDE (preferably IntelliJ) and start the service after building it.

  2. Copy the boundary-data JSON that needs to be migrated as an example we are taking boundary-data of Phagwara (Punjab). and adding RequestInfo inside this as shown below.

{
	“RequestInfo”: {} ,
	“tenantId”: ”default” ,
    “moduleName”: “egov-location” ,
    “TenantBoundary”: []
}
  1. Open Postman and create a new HTTP endpoint with a path as

http://localhost:8081/boundary/_migrate

and the above as the endpoint request body.

PS: The boundary-migration service is assumed to run on port 8081. If it is running on a different port, check the active port and update the path accordingly.

  1. Send the request and if the endpoint path and request body are correct the response would be 200 OK.

Below is a reference CURL:

Last updated

Was this helpful?