Difference between revisions of "Category:Configuration"
Jump to navigation
Jump to search
m |
|||
| (One intermediate revision by the same user not shown) | |||
| 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. The low-level configuration is done using XML, through so-called ''app.config'' files (the true name of the file is actually different, and depends on the hosting scenario). |
| − | ; [[: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 JSON, through ''appsettings.json'' files. |
Latest revision as of 14:24, 18 January 2021
There are two types of QuickOPC configuration:
- Low-Level Configuration
- Used for configuring diagnostics, and internal workings of the QuickOPC software. The low-level configuration is done using XML, through so-called app.config files (the true name of the file is actually different, and depends on the hosting scenario).
- 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 JSON, through appsettings.json files.
Subcategories
This category has the following 2 subcategories, out of 2 total.
Pages in category "Configuration"
The following 10 pages are in this category, out of 10 total.
