Configuration

• Introduction
• Frontend
• Backend
  • Configuration Sources
  • WebConfig Transformers

Introduction

Frontend

Frontend configuration is using the angular default configuration set-up, which is outlined in the getting started section.

Backend

MVDA - API

The API is configured using appsettings.json. The configuration keys and their meanings are shown below:

Batch Database Worker

The batch database worker is configured using appsettings.json. The configuration keys and their meanings are shown below:

Cache Worker

The cache worker is configured using appsettings.json. The configuration keys and their meanings are shown below:

CleanUp Worker

The clean up worker is configured using appsettings.json. The configuration keys and their meanings are shown below:

EventBus Worker

The event bus worker is configured using appsettings.json. The configuration keys and their meanings are shown below:

Notification - Worker Service

The notification worker is configured using appsettings.json. The configuration keys and their meanings are shown below:

Configuration Sources

In addition to the appsettings.json the MVDA module uses the following configuration objects:

The MVDA section inside the ConfigurationItems.json file inside the core project, has the following values. With the configuration, MVDA requires the following mandatory datatypes:

• Equipment Data (DataTypes.Type: 1)
• EDMS Data (DataTypes.Type: 4)

And supports resources, for:

• Audit trail implementation (Resources.Type: 2)
• Admin actions (Resources.Type: 3)
• Signing up for batch subscription (Resources.Type: 1)

{
        "Name": "MVDA",
        "Host": "https://#Env#-#IsValidated#.domain.com",
        "IsValidated": false,
        "DataTypes": [
            {
                "Type": 1,
                "Mandatory": true,
                "AllowMultiselection": false
            },
            {
                "Type": 4,
                "Mandatory": true,
                "AllowMultiselection": false
            }
        ],
        "Port": "8188",
        "Resources": [
            {
                "ResourceURL": "api/BatchEvent/GetBatchEvents",
                "Type": 1
            },
            {
                "ResourceURL": "api/AuditTrail/GetModuleAuditTrail",
                "Type": 2
            },
            {
                "ResourceURL": "/mvda/administration/actions/create",
                "Type": 3
            }
        ],
        "RPackages": [
            "acdcMvda"
        ]
    }

The following admin actions, are available in the MVDA module, configured by AdminActions.json at the root level in the project. All admin actions are implemented in the SiteController, the intended business implementation can be taken from the requirement specification.

[
  {
    "Path": "mvda-batchDatabase",
    "DisplayText": "Batch Database Backfill",
    "Permissions": [ "GLOBAL_ADMIN" ]
  },
  {
    "Path": "get-all-pi-web-ids-per-site",
    "DisplayText": "Get All PI Web Ids Per Site",
    "Permissions": [ "GLOBAL_ADMIN" ]
  },
  {
    "Path": "replace-all-global-filters",
    "DisplayText": "Replace All Global Filters",
    "Permissions": [ "GLOBAL_ADMIN" ]
  },
  {
    "Path": "replace-all-web-ids",
    "DisplayText": "Replace All Web Ids",
    "Permissions": [ "GLOBAL_ADMIN" ]
  },
  {
    "Path": "replace-sensor-names",
    "DisplayText": "Replace All Sensor Names",
    "Permissions": [ "GLOBAL_ADMIN" ]
  }
]