Jump to: navigation, search

Difference between revisions of "Configuration Files"


(Specific Configuration Files)
Line 1: Line 1:
{{PageStatus/Draft}}
 
 
Configuration files of all {{UBIK}} components have to comply with syntax and other guidelines as stated in [https://msdn.microsoft.com/en-us/library/1xtk877y%28v=vs.110%29.aspx Configuring Apps by using Configuration Files].
 
Configuration files of all {{UBIK}} components have to comply with syntax and other guidelines as stated in [https://msdn.microsoft.com/en-us/library/1xtk877y%28v=vs.110%29.aspx Configuring Apps by using Configuration Files].
  

Revision as of 15:04, 12 May 2015

Configuration files of all UBIK® components have to comply with syntax and other guidelines as stated in Configuring Apps by using Configuration Files.

Each component has a main configuration file containing basic settings not to be changed by the user. Additionally, specific configuration files are available as separate files, whose content is also included in the configuration.

Main Configuration Files

The main configuration files for the UBIK® Studio and UBIK® Enterprise Service are located within the installation folder, the one of the web service is located in the service's physical path. Respective examples files are

The configuration file of the web service additionally needs to obey rules as given in Configuring Services.

Common sections, existing in all main configuration files and should not be changed in general, are

  • <configSections>: these settings include general logging and exception handling
  • <exceptionHandling>: detailed configuration of exception handling
  • <loggingConfiguration>: detailed configuration of logging
  • <system.serviceModel>: behaviours for services and endpoints

Specific Configuration Files

The specific configuration files are considered in the configuration via inclusion. For example, the tag <bindings configSource="Logging.config" /> in the main configuration file adds all settings of Logging.config to the configuration.

Specific files are available for:

  • Bindings: different configurations for data services and endpoints
  • Clients: definitions used by the data service for connecting to the session management service
  • Logging: configuration of destination paths, etc.
  • Runtime: runtime specific configurations
  • Services: used by the data service and the session management service
  • Application Settings: configuration of the data and session management service of the web service

This table shows by which component the specific files are used.

DescriptionExample fileWeb serviceStudioEnterprise Service
Application settingsAppSettings.configIC Bullet Full.png--
BindingsBindings.configIC Bullet Full.pngIC Bullet Full.pngIC Bullet Full.png
ClientsClient.configIC Bullet Full.pngIC Bullet Full.pngIC Bullet Full.png
LoggingLogging.configIC Bullet Full.pngIC Bullet Full.pngIC Bullet Full.png
Runtime settingsRuntime.configIC Bullet Full.pngIC Bullet Full.pngIC Bullet Full.png
ServicesServices.configIC Bullet Full.png--