DC 5.4 Core Service configuration

1 Logging
- 1.1 Note
2 Log server configuration
3 Integration Service
4 Internal Debouncing
5 Business Workflow

This page documents the available options for the services the DAM Center has in Dotnet Core. The services are in the “DigizuiteCore” and “AutomationWorkflows” folders.

Logging

All settings are reloaded on-the-fly when the appsettings.json file is changed. I.e there is no need to restart the processes. You need, however, to have the entire path to the log file (sans the log file) pre-created upon load. This typically is only an issue for when you change the log path.

The following keys are available in the “Logging” section of the appsettings.json.

Some of these settings might not be visible by default, regardless of this, they may all be used.

Option name	Description

Option name	Description
`LogLevel`	The amount of logging to be included. Valid values are: None ← Least Critical Error Warning Information Debug Trace ← Most With each log level has more info than the former (including the former).
`Overrides`	A dictionary that can be used to change the log level of certain namespaces. Usually not something you need to change. For example - the following: `"Overrides": { "Microsoft.EntityFrameworkCore": "Warning" },` reduces the LogLevel of Entity Framework to Warning, rather than the normal log level set for the rest of the service. Multiple keys can be set at the same time.
`EnabledCentralizedLogger`	By enabling this, you give access for people to look at the logs though MM
`LocalLogPath`	(Requires `EnableLocalLogging=true`to work) The path provided here will be used for local logging. Please note that: This does not clean up after itself, so this should only be enabled for the sake of debugging, and should be turned off once finished. Setting this to a folder that doesn’t exist upon load, will make both Centralized+local logging not work (the logs will be blank both places)
`EnableLocalLogging`	If you have`EnableLocalLogging=true`then this is enabled. Please note that this too does not clean up after itself - i.e. the above warning also applies here. Both this and `LocalLogPath` have to be set, for local logging to occur.

Note

There may be times when one or more applications fail to fully start. This is usually due to an issue with the environment. In case of this happening, it may be useful to access the failing services' Web.Config files, and enable stdout logging. Please be very cautious when enabling this, as it doesn’t clean up after itself. Once the service is up and running anew, there’s a real threat of it filling the disk entirely if not disabled again.

Log server configuration

The log server has the following configuration options:

Option name	Description

Option name	Description
`LogPath`	The location of the log files on disk (Can be either a relative or absolute path)
`LogFileSizeCutoff`	The size in MB that determines (roughly) how big each log file should be allowed to become
`LogStorageType`	Determines what kind of storage to use. Currently, only “Local” is supported.
`CleanupStrategy`	What cleanup strategy to use. Either `Duration` or `Count`. `Duration` will keep all log files in a certain period, no matter the count. `Count` will only ever keep a certain amount of log files, no matter the period.
`OldLogFileCount`	Determines how many old log files can be at the same time, if using the `Count` strategy
`KeepDuration`	How long the log files will be kept, if using the `Duration` strategy. Use the C# TimeSpan format.

All these settings can be changed on-the-fly, without requiring a restart of the LogServer process.

Integration Service

The Integration Service debounces messages before sending updates to subscribing integration endpoints. The debounce interval can be configured by adding a “Debouncing” section to the appsettings.json file for the Integration Service. This section has the following configuration options:

Option name	Description	Type	Default value

Option name	Description	Type	Default value
`Interval`	The debouncing interval to use when debouncing messages before sending them to subscribing integration endpoints.	Timespan	“00:00:07” (7 seconds)

Internal Debouncing

A lot of services are debouncing messages using the Debouncing Service. The Debouncing Service can be configured by adding a “InternalDebouncing” section to the appsettings.json file for the Debouncing Service. This section has the following configuration options:

Option name	Description	Type	Default value

Option name	Description	Type	Default value
`SleepInterval`	The Debouncing Service periodically checks if it has any messages that have been debounced and should be sent back to the origin. This parameter configures the sleep time between each check.	Timespan	“00:00:00.200” (200 milliseconds)
`ReturnLimit`	The maximum number of messages returned at each of the periodical checks.	Integer	10000

Note that all parameters above are optional. It is possible to configure one parameter without configuring the other.

Business Workflow

The Business Workflow Service can be configured by adding a “BusinessWorkflow” section to the appsettings.json file for the Business Workflow Service. This section has the following configuration options:

Option name	Description	Type	Default value

Option name

Description

Type

Default value

MigrationInstanceLimit

When an existing business workflow is updated, the existing workflow instances for this workflow are migrated to the new version. This parameter sets the maximum number of instances to migrate at a time.

Note that all instances using the previous version of the business workflow are always migrated. Thus, this parameter can primarily be used to tweak performance.

Integer

1000