Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Prior Knowledge of Java/J2EE.

  • Prior Knowledge of Spring Boot.

  • Prior Knowledge of REST APIs and related concepts like path parameters, headers, JSON, etc.

  • Prior knowledge of Git.

  • Advanced knowledge on how to operate JSON data would be an added advantage to understand the service.

Key Functionalities

Add 2-3 lines to highlight the use and applications in context.

  • Add functional aspects for the topic (Use bullets to build the list)

  • Tables can be inserted for certain topics.

...

Title 

...

Description

Deployment Details

  1. Deployment Steps (Use numbered bullet lists to define the sequence)

Configuration Details

  1. Configuration steps (Use numbered bullet lists to define the sequence)

Integration

 

Integration Scope

 

Integration Benefits

 

Steps to Integration

...

  • The MDMS service reads the data from a set of JSON files from a pre-specified location.

  • It can either be an online location (readable JSON files from online) or offline (JSON files stored in local memory).

  • The JSON files will be in a prescribed format and store the data on a map. The tenantID of the file serves as a key and a map of master data details as values.

  • Once the data is stored in the map the same can be retrieved by making an API request to the MDMS service. Filters can be applied in the request to retrieve data based on the existing fields of JSON.

Deployment Details

  • For deploying the changes in MDMS data, the service needs to be restarted.

  • The changes in MDMS data could be adding new data, updating existing data, or deletion.

Configuration Details

The config JSON files to be written should follow the listed rules

  • The config files should have JSON extension

  • The file should mention the tenantId, module name, and the master name first before defining the data 

Code Block
{
  "tenantId": "uk",
  "moduleName": "BillingService",
  "{$MasterName}":[ ]
}

Title

Description

tenantId

Serves as a Key

moduleName

Name of the module to which the master data belongs

MasterName

The Master Name will be substituted by the actual name of the master data. The array succeeding it will contain the actual data.

 Example Config JSON for “Billing Service”

Code Block
{
  "tenantId": "pb",
  "moduleName": "BillingService",
 "BusinessService": 
 [
    {
      "businessService": "PropertyTax",
      "code": "PT",
      "collectionModesNotAllowed": [ "DD" ],
      "partPaymentAllowed": true,
      "isAdvanceAllowed": true,
      "isVoucherCreationEnabled": true
    }
]
}

Reference Docs

Title 

Link

Reference Doc Link 1

MDMS-Service

Reference Doc Link 2

MDMS-Rewritten

API List