Configuration

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

Introduction

Frontend

Managing environment variables is crucial during the build process, as they ensure the correct configuration and seamless execution of tasks. In this context, environment variables are consumed and set dynamically to tailor the build to specific requirements. The build task reads a settings.json file, which contains essential configuration details, allowing it to adapt and perform its functions accurately. The script below can be used to set variables during the CI build.

sed -i "s|CLI_DEPLOY_URL|https://${DCP_SERVER}/${APP_NAME}/|g" ${CI_PROJECT_DIR}/angular.json
sed -i "s|CLI_DEPLOY_URL|https://${DCP_SERVER}/${APP_NAME}|g" ${CI_PROJECT_DIR}/src/fonts-build.scss
jq -n --arg api "https://${DCP_SERVER}" \
    --arg baseapp "https://${DCP_FE_SERVER}/"  \
    --arg production false  \
    --arg apiEnv true  \
    --arg policy "https://www.roche.com/privacy_policy.htm" \
    --arg gateway "https://${DCP_GATEWAY_HOST}" \
    --arg portcheck "roche.com:" '{"apiUrl":$api, "baseAppUrl":$baseapp, "apiEnv": $apiEnv, "production": $production, "privacyPolicyUrl":$policy, "backendPortCheckUrl":$portcheck, "apiServiceUrl":$gateway}' > settings.json
npx kendo-ui-license activate
npm run build

The used variables have the following meaning:

Backend

Core - API

Core - Email Processor Windows Service

Core - Active Batches Windows Service

Core - Clean Up Windows Service

Core - EventBus

Basic - API

Basic - EventBus

Basic - Notifications

Configuration Sources

Every DCP component has two main configuration locations:

• Module specific configuration object in ConfigurationItems.json file in the Core file
• Specific web.config file
• Service specific app config files
• ocelot.{moduleName}.json (see the gateway filebuilder on how to easily generate this file for .NET projects)

WebConfig Transformers

The DCP components uses publish profiles to transform the web.config files for the environments. For each environment, a dedicated build profile is created. Build profiles are automatically selected by the CI based on the branch. Per environment, the following transformations are created:

• {Web/App}.Dev.config
• {Web/App}.Stage.config
• {Web/App}.Test.config
• {Web/App}.Prod.config

Web.config sections containing sensitive information are encrypted using a key container during the publish process. For encrypting aspnet_regiis utility is used. Every component has it's one web.config files. Inside the components there

Configuration Items

ConfigurationItems is the mapping file, used by the core service, to enable a central maintenance and administration of different DCP components. This file is part of the core repository and only configured once, centrally. Each Module is configured using an object in the following format: Example, MVDA configuration object:

{
    "Name": "MVDA",
    "IsValidated": false,
    "DataTypes": [1],
    "Resources": [{
    "Port": "8188",
    "ResourceURL": "api/BatchEvent/GetBatchEvents",
    "Type": 1,
    }],
    "RPackages": ["acdcMvda"],
    "AdminActions": [{ "Value": "mvda-batchDatabase", "Text": "Batch Database Backfill" } ]
}

The modules in this file is used to provide the available modules, their names for administration purposes. The keys have the following context:

• Name: The name of the module used for reference in code and in RADA Groups, roles, etc.
• IsValidated Boolean validation status of the current module
• DataType An array of data types required by the module, based on this mappings need to be created by the user, used are the values from DataType.cs Resources Sometimes it can't be avoided that shared services (e.g. ActiveBatches) require entities from other dependent services. In these cases Resources are mapped using this property, request URL is build dynamically based on Origin-Header , the fields Port and Resource URL: Origin-Header-{IsValidated ? gxp : nongxp}:{Port}{ResourceUrl} Resources to be checked are filtered by the Type, property. This uses the MicroservicesMapType.cs enumeration
• AdminActions An array of available admin actions, all admin actions have two properties Value and Text, the Value contains the web component from the FE implementing the action and the Text the display string for the user
• RPackages The R package Name used for the module