Jump to: navigation, search

Configure Logging


Revision as of 13:38, 25 March 2014 by KNO (Talk | contribs)

To document certain events (errors, warnings, etc.) that occur in the UBIK® system, a logging mechanism is provided to support the designer or programmer in finding issues in the design process or to identify the reason for problems at runtime. Logging in UBIK® can be configured for the Web Service as well as for the UBIKSTUDIO. The general configuration for logging is described here.

  • The logging in UBIK® Studio can be configured by editing the file UBIK.Studio.exe.config, which is located in the program folder of UBIK® Studio and also contains the section loggingConfiguration which can be configured in the same way like the UBIK® Web Service.

Logging Categories

UBIK has different types of categories configured for the logging mechanism. The following categories can be configured in the configuration files. Categories with the remark "internal" are available via customizing code, but are used to log internal UBIK events. As it is not recommended to mix logging of internal UBIK events together with others, the two additional categories "CUSTOMIZING" and "WORKFLOW" have been created.

Type Description
CUSTOMIZING Log for events that occured in the customizing. This method is available by adding "UBIKKernel.LogCustomizing(...)" to the customizing code.
WORKFLOW Log for events that occured when running workflows which is provided by the WriteLogEntry Activity
ASSERTION Log for failed Assertions (internal)
WARNING Log for events that created a warning (internal)
ERROR Log for events that created an error (internal)
DEBUG Log for events that have to be investigated in the development (internal)
SQL Log for events related to SQL queries (internal)
EXCEPTION Log for events that caused an exception (internal)

See also