HCM Master Promotion Guide

Overview

This document is a step-by-step promotion guide to setup/promote Health Campaign Manegement (HCM) to higher environments. The guide can be used by implementation teams or other external teams to set up the product.

Table of Contents

1. Release Notes for HCM

  • Release features

  • List of Core DIGIT services used

  • Services built for HCM

  • Environment variables for HCM services

- Individual

- Household

- Product

- Facility

- Project

- Stock

- Service request

- Complaints Management

- User Management

2. Promotion guide

  • DIGIT environment production setup & deployments

  • HCM promotion

  • Steps to create a tenant for HCM

  • Steps to add localisation using Rest API

  • Deploy Digit Core services

  • Deploy HCM services

  • UI/APK promotion guide

1. Release Notes: HCM

Release Features: List of Core DIGIT services used

Services built for HCM

Environment Variables for HCM services

Individual: Click here to know more.

Household: Click here to know more.

Product: Click here to know more.

Facility: Click here to know more.

Project: Click here to know more.

Stock: Click here to know more.

Service Request: Click here to know more.

Complaints - PGR: Click here to know more.

User Management - HRMS: Click here to know more.

Promotion guide

This section will detail out the promotion guide steps for HCM Product

Digit Environment Production Setup & deployments

Digit Environment setup refer documentation here.

HCM Promotion

Steps to Create a tenant for HCM

Refer to the document for creating a tenant in DIGIT.

Steps to add localisation using Rest API

Refer to this document for more details

curl --location --request POST 'https://health-dev.digit.org/localization/messages/v1/_upsert' \
--header 'Content-Type: application/json' \
--data-raw '{
   "RequestInfo": {
       "apiId": "Rainmaker",
       "ver": ".01",
       "ts": "",
       "action": "_create",
       "did": "1",
       "key": "",
       "msgId": "20170310130900|en_IN",
       "authToken": "052c8e95-35c1-4f97-b366-c5f23e23ce05"
   },
   "tenantId": "default",
   "messages":[
 {
   "code": "ABG_COMMON_TABLE_COL_ACTION",
   "message": "Action",
   "locale": "en_IN",
   "module": "rainmaker-common"
 },{
   "code": "ABG_COMMON_TABLE_COL_ACTION",
   "message": "Action",
   "locale": "en_IN",
   "module": "rainmaker-common"
 }
]
}'

Steps to configure MDMS configs

  1. Create Common Masters

a. Create IdFormat.json which will be used by egov-id-gen service.

b. Create StateInfo.json which will configure eligible languages for tenant

  1. Create sample boundary data. Refer for to this document for more details

  2. Create field-app-configuration.json which will be used for drop-down values or select options to be presented in the HCM app

  3. Create project-types.json which will be used as Health campaign configuration

  4. Create service-registry.json which has a list of APIs that HCM app will call.

  5. Create configs for Access Control Sevices

  1. Configure map-config for the tenant

Restart MDMS server and restart Zuul api gateway.

Note: Any modifications in the above configuration, needs to restart the MDMS server. Any modifications to action-test.json and roleactions.json requires restart of Zuul api gateway

Steps to configure health campaign configs

Step 1: Create persister config for each backend service which will be picked by the persister service

Step 2: Create indexer config for each backend service which will be picked by the indexer service

Note: Any changes to indexer and persister configs, requires restart of indexer and persister.

Deploy Digit Core Services

Refer to section for list of core services to be deployed

Deploy HCM services

Refer to section for list of HCM services to be deployed

UI/APK promotion guide

https://health.digit.org/product/setup/apk-installation

Last updated

https://creativecommons.org/licenses/by/4.0/