> For the complete documentation index, see [llms.txt](https://docs.digit.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.digit.org/health/v1.5/setup/configuration/service-configuration/product-registry.md).
# Product Registry
## Overview
The product service provides APIs to create products and product variants for HCM. This document provides the configuration details for setting up products and product variants.
## 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
1. Provides APIs to create, update, and search products.
2. Provides APIs to create, update, and search product variants.
### Setup details
The source code for a [Product](https://github.com/egovernments/health-campaign-services/tree/v1.1.0/health-services/product) 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: [Product.yaml](https://github.com/egovernments/health-campaign-services/blob/v1.1.0/docs/health-api-specs/contracts/registries/product.yml)
**Application.properties file information*****:***
Kafka topics persister configs for eGov persister
```
product.kafka.create.topic=save-product-topic
product.kafka.update.topic=update-product-topic
product.variant.kafka.create.topic=save-product-variant-topic
product.variant.kafka.update.topic=update-product-variant-topic
```
#### URLs for the external API references:
* eGvo mdms :-> egov.mdms.host =[ https://health-dev.digit.org](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**
[**Action-test.json**](https://github.com/egovernments/health-campaign-mdms/blob/v1.1.0/data/default/ACCESSCONTROL-ACTIONS-TEST/actions-test.json)
```
{
"id": 1536,
"name": "Product Variant Create",
"url": "/product/variant/v1/_create",
"displayName": "Product Variant Create",
"orderNumber": 0,
"parentModule": "",
"enabled": false,
"serviceCode": "product",
"code": "null",
"path": ""
},
{
"id": 1537,
"name": "Product Create",
"url": "/product/v1/_create",
"displayName": "Product Create",
"orderNumber": 0,
"parentModule": "",
"enabled": false,
"serviceCode": "product",
"code": "null",
"path": ""
},
{
"id": 1541,
"name": "Product Update",
"url": "/product/v1/_update",
"displayName": "Product Update",
"orderNumber": 0,
"parentModule": "",
"enabled": false,
"serviceCode": "product",
"code": "null",
"path": ""
},
{
"id": 1542,
"name": "Product Search",
"url": "/product/v1/_search",
"displayName": "Product Search",
"orderNumber": 0,
"parentModule": "",
"enabled": false,
"serviceCode": "product",
"code": "null",
"path": ""
},
{
"id": 1543,
"name": "Product Variant Update",
"url": "/product/variant/v1/_update",
"displayName": "Product Variant Update",
"orderNumber": 0,
"parentModule": "",
"enabled": false,
"serviceCode": "product",
"code": "null",
"path": ""
},
{
"id": 1544,
"name": "Product Variant Search",
"url": "/product/variant/v1/_search",
"displayName": "Product Variant Search",
"orderNumber": 0,
"parentModule": "",
"enabled": false,
"serviceCode": "product",
"code": "null",
"path": ""
},
```
**Access to role-based actions**
[**Roleaction.json**](https://github.com/egovernments/health-campaign-mdms/blob/v1.1.0/data/default/ACCESSCONTROL-ROLEACTIONS/roleactions.json)
```
{
"rolecode": "SYSTEM_ADMINISTRATOR",
"actionid": 1536,
"actioncode": "",
"tenantId": "default"
},
{
"rolecode": "SYSTEM_ADMINISTRATOR",
"actionid": 1537,
"actioncode": "",
"tenantId": "default"
},
{
"rolecode": "SYSTEM_ADMINISTRATOR",
"actionid": 1541,
"actioncode": "",
"tenantId": "default"
},
{
"rolecode": "SYSTEM_ADMINISTRATOR",
"actionid": 1542,
"actioncode": "",
"tenantId": "default"
},
{
"rolecode": "SYSTEM_ADMINISTRATOR",
"actionid": 1543,
"actioncode": "",
"tenantId": "default"
},
{
"rolecode": "SYSTEM_ADMINISTRATOR",
"actionid": 1544,
"actioncode": "",
"tenantId": "default"
}
```
**Persister configuration**
[Product Persister Yaml](https://github.com/egovernments/health-campaign-config/blob/v1.1.0/egov-persister/product-persister.yml)
**Indexer configuration**
[Product Indexer Yaml](https://github.com/egovernments/health-campaign-config/blob/v1.1.0/egov-indexer/product-indexer.yml)
#### Database schema
**Postman collection**
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.digit.org/health/v1.5/setup/configuration/service-configuration/product-registry.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
