tia Viewer Core provides many configuration parameters An instance is a set of these configurations and has a instance name. Repositories are mapped to a specific instance.
All instance settings are below parent tia.instances.
Mapping repositories to instances
Repositories are mapped to instances. The tia Viewer Core allows each instance to be configured separately.
In SAP-side customized tia Viewer Core configuration, the mapping to an instance resides on SAP-side. For more information read about column Viewer Conf in https://kgs-software.atlassian.net/wiki/spaces/WIKI/pages/3257106464/SAP+Customizing+Vc#%2FKGS1%2FVIEWER_CUST-Transaction .
In Content Server Viewer (CSV) configuration, the mapping is specified in the tia Viewer configuration using parameter
tia.repositoryinstancemapping, see also https://kgs-software.atlassian.net/wiki/x/B4C1wg.
tia Viewer Core maps repositories to instance default, if no explicit mapping exists.
Applying instance settings
Instance settings must reference a specific instance, so
when setting via environmental variable, the variable name must always contain following prefix
tia.instances.<instance name>.
when using a viewer YAML configuration file, the correct location is important (below the instance name and with two spaces more intend).
The instance default is the template for all instances: If a parameter is not specified for a specific instance, the setting of default is applied.
If also for instance default no setting was applied, tia Viewer uses built-in default values (global default).
The more specific setting overrules the the more general.
E.g., tia.instances.finance.documentNote overrules for instance finance the default
specified for the installation by tia.instances.default.documentNode for all instances
which overrules the global default value of true.