Skip to main content

Configuration Manager

There are parameters that must be added to the SYSTEMCONFIGURATIONS table before Configuration Manager can be used by the Synergy system. These settings are kept with the "System.ConfigurationManager" key. Below is an example config setting.

{
"ConfigurationManagement": {
"RestService": {
"Url": "https://dev-configuration.bimser.net/",
"DeadLine": "60"
},
"GrpcService": {
"Url": "https://dev-configuration.bimser.net/GrpcConfigurationManagement",
"DeadLine": "60"
},
"ServiceDecider": {
"ServiceType": "Rest"
},
"SignalRConnection": {
"SignalRHubUrl": "https://dev-configuration.bimser.net/ConfigurationManagerAPIServiceHub"
}
}
}

ConfigurationManagement

It is the name of the main tag where the parameters are kept.


RestService / GrpcService

It is the config where RestService/GrpcService information is kept when communicating with Configuration Manager via RestService/GrpcService. This config contains the URL and DeadLine Parameters.

Url

Rest determines the address to which requests are sent.

DeadLine

Determines the timeout time of discarded requests


ServiceDecider

ServiceType parameter. ServiceType decides how Synergy and Configuration Manager communicate. Gets the Rest and Grpc values.


SignalRConnection

Contains SignalR information. SignalRHubUrl parameter. SignalRHubUrl: The address of the Configuration Manager SignalR Hub that is standing.


Instances.*

There are Instance Keys in the SYSTEMCONFIGURATIONS table. For example; Like Instances.Dev. The value of this Key includes Enviroment and ConfigurationManagementPublicKey.

Enviroment

Environment information in Configuration Manager. Ex. Dev, Prod, etc.

ConfigurationManagementPublicKey

PublicKey information is retained to ensure that incoming requests to Configuration Manager are made by the correct person/application. If this PublicKey information and PrivateKey can resolve each other on the Configuration Manager side, the Configuration Manager application makes a healthy return to the client.