Service configuration file - Multiple configurations

[ConfigurationName].json

For every instance, a separate configuration file must be created with the exension “.json”. The filename must have the same name as the DigaSystem configuration name. This name must also get used for the argument “\configuration” on the Windows service installation.

Hint. By the first installation you can rename the file template_AppSettings.json to your individual configuration name. This file contains all parameters required for service configuration and requires only to fill with the real values (e.g. URLs for the DPE services)

Properties

This file has the same format as standard configuration file appsettings.json for .NET 6 Core applications. It may be case-insensitive on Windows, depending on specific Windows configurations. As a standard configuration file, there are many .NET Core options which need or can be specified. Worth mentioning, the "AllowedHosts" needs to be configured in this file. (Typically, if no security worries, we can simply specify it as "*". For more, check the following link https://docs.microsoft.com/en-us/dotnet/api/microsoft.aspnetcore.hostfiltering.hostfilteringoptions.allowedhosts?view=aspnetcore-6.0)

This file also contains parameters to get access to the external services & configuration used for the current service instance.

Configuration name

The parameter “ConfigurationName” is ignored by using multiple configurations. Can get deleted on multiple instance configurations.

External services

Credentials encryption

Warning!

• All credentials used for access to external services (login & password) are encrypted in the configuration file at service start.

• To change the credentials, just enter new login and / or password in plain text. Service read the new unencrypted credentials and encrypted it at the next start

• Login and password must not be started from *1* sequence

Parameter service

Service get access to the parameters stored in the DigaSystem registry via DPE Parameter service. All registries are read in followed sequence

• Global registry

• Local registry (overwrite parameters from global registry)

• User registry (overwrite parameters from global & local registry)

To provide access to the Parameter service, add the configuration section "ParameterService" to the corresponding file [ConfigurationName].json. E.g.

"ParameterService": {
  "Host": "http://localhost/DpeWebApplication/",
  "Username": "",
  "Password": ""
}

Rights service

Service get access to the user rights via DPE Rights service. To provide access to the Rights service, add the configuration section "RightsService" to the file [ConfigurationName].json. E.g.

"RightsService": {
  "Host": "http://localhost/DpeWebApplication/",
  "Username": "",
  "Password": ""
}

Log service

The service uses the DPE Log service to log all errors. If the log service isn't available, the file log will be used. To provide access to the DPE Log service, add the configuration section "LogService" to the file [ConfigurationName].json. E.g.

"LogService": {
  "Host": "http://localhost/DpeWebApplication/",
  "Username": "",
  "Password": ""
}