Installation and setup

• Introduction
• R packages
• Backend
  • Windows Services
  • API
  • Virtual Directories
• Frontend
  • Micro Frontend
  • Web components
• Module specific steps

Introduction

MVDA uses the standard installation path, described in the DCP Framework. For the variables use the sections below.

R packages

DCP MVDA functionality is implemented in a single package, which depends on other acdc packages which are installed via the package dependencies.

Backend

Windows Services

Batch Database Service This service is used to transfer and recalculate batches in the batch database.

Cache Service This service implements the real-time cache layer used by notifications, dashboards, etc.

Clean Up Service This service implements the information compliance requirements to remove old records.

Event Bus Service This service is used to wire against the events emitted from dcp framework and have an implementation in the MVDA module.

Notifications Service This service is used to check real-time batches/events against the user specification and informs on model violations via e-mail.

API

The MVDA uses the .NET Core API path, all module specific functionality is provided by a single IIS site:

Virtual Directories

PHP extensions

N/A - using .NET Core route therefore this section does not apply.

Scheduled Tasks

N/A - no scheduled tasks required

Frontend

Micro frontends

All MVDA functionality is bundled in a single microfrontend, which uses the following configuration:

Web components

The MVDA module, provides one additional web-components

• the dashboard-model-presentation is read by the DCP framework and provides the dashboard tile implementation.

MVDA uses web-components provided by DCP Framework, therefore the framework components need to be installed prior to the MVDA module installation.

Module specific steps

MVDA does not require any module specific installation steps.