Difference between revisions of "Category:Configuration"

From OPC Labs Knowledge Base
Jump to navigation Jump to search
m
Line 1: Line 1:
 
There are two types of QuickOPC configuration:
 
There are two types of QuickOPC configuration:
; [[:Category:Low-Level Configuration|Low-Level Configuration]]:  
+
; [[:Category:Low-Level Configuration|Low-Level Configuration]]: Used for configuring diagnostics, and internal workings of the QuickOPC software.
 
; [[:Category:High-Level Configuration|High-Level Configuration]]: Used for configuring parameters of main QuickOPC components (e.g. {{Style=Identifier|EasyUAClient}}). There is a built-in, always present mechanism that allows such configuration be made externally, and also a programmatic component configuration, used when you need a finer control over how the components are configured. There are various ways the high-level configuration is provided, but most frequently, it is done using ''appsettings.json'' files.
 
; [[:Category:High-Level Configuration|High-Level Configuration]]: Used for configuring parameters of main QuickOPC components (e.g. {{Style=Identifier|EasyUAClient}}). There is a built-in, always present mechanism that allows such configuration be made externally, and also a programmatic component configuration, used when you need a finer control over how the components are configured. There are various ways the high-level configuration is provided, but most frequently, it is done using ''appsettings.json'' files.

Revision as of 14:15, 18 January 2021

There are two types of QuickOPC configuration:

Low-Level Configuration
Used for configuring diagnostics, and internal workings of the QuickOPC software.
High-Level Configuration
Used for configuring parameters of main QuickOPC components (e.g. EasyUAClient). There is a built-in, always present mechanism that allows such configuration be made externally, and also a programmatic component configuration, used when you need a finer control over how the components are configured. There are various ways the high-level configuration is provided, but most frequently, it is done using appsettings.json files.