Jump to: navigation, search

Difference between revisions of "Logging"


(Created page with "Internal, system driven events of different types (debug messages, errors, warnings, etc.) occuring within in {{UBIK}} are recorded by a logging mechanism. This information su...")
(No difference)

Revision as of 18:25, 11 May 2015

Internal, system driven events of different types (debug messages, errors, warnings, etc.) occuring within in UBIK® are recorded by a logging mechanism. This information supports the user in finding issues in the design process or to identify the reasons for problems at runtime. The mechanisms can be configured for the Web Service, the UBIK® Studio as well as for the UBIK® Enterprise Service. A general description of the technique used can be found on the Microsoft page for Configuring Services.

Since Version 2.4.3 - Server the configuration has to be done in the Logging.config file. For older versions the configuration has to be done in one of the main [[configuration files.

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 events. As it is not recommended to mix logging of internal events together with others, the two additional categories CUSTOMIZING and WORKFLOW have been created.

Type Description Access
CUSTOMIZING Log for events that occured in the customizing. This method is available by calling UBIKKernel.LogCustomizing(...) from the customizing code. public
WORKFLOW Log for events that occured when running workflows which is provided by the WriteLogEntry Activity public
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