Facility Registry
Overview
The facility service provides APIs to create facilities for HCM. This document provides the configuration details for setting up the facility.
Pre-requisites
Knowledge of Java/J2EE (preferably Java 8 version).
Knowledge of spring boot and spring-boot micro-services.
Knowledge of Git or any version control system.
Knowledge of RESTful web services.
Knowledge of the Lombok library is helpful.
Knowledge of eGov-mdms service, eGov-persister, eGov-idgen, eGov-indexer, and eGov-user will be helpful.
Functionalities
Provides APIs to create, update, delete, and search facilities.
Provides APIs to bulk create, bulk update, and bulk delete facilities.
Setup Details
The source code for Facility is present in the health-campaign-services Git repo. The spring boot application needs the Lombok* extension added to the IDE to load it. Once the application is up and running, the API requests can be posted to the URL and the IDs can be generated.
*In the case of IntelliJ, the plugin can be installed directly. For eclipse, the Lombok jar location has to be added in the eclipse.ini file in this format javaagent:lombok.jar.
API details
Refer to the Swagger API for YAML file details: Facility.yaml
Application.properties file information:
Kafka topics persister configs for Facility
URLs for the external API references:
eGvo mdms :-> egov.mdms.host = https://health-dev.digit.org/
eGov -idGen :-> egov.idgen.host = https://health-dev.digit.org/
eGov-User Service -> egov.user.host = https://health-dev.digit.org/
Configuration Details
Access MDMS configurations
Action test: URL actions adding
Access to role-based actions