Logback has been chosen as the logging framework because it supports all the functionality that had been implemented in the SSO proprietary logging system.
Logback configuration files have been organized in the following way:
Each web application has in its class path a similar kind of
logback.xml
file which simply defines the context name for the application and includes the actual logger configurationThe logger configuration shared by all web applications is named
include-logback.xml
and it contains all the definitions required by SSO logback configuration
There is normally no need for the customers to modify these configuration files but in the following examples we go through the interesting parts in them.
Main logback.xml
files
The logback.xml
files reside in these location for each web application in the default installation (<webapp>
is the name of the web application like uas
, logviewer
, sso-api
etc.):
Linux:
/usr/local/ubisecure/ubilogin-sso/ubilogin/webapps/<webapp>/WEB-INF/classes
from where it is copied to/usr/local/ubisecure/ubilogin-sso/tomcat/webapps/<webapp>/WEB-INF/classes
during the installation processWindows:
C:\Program Files\Ubisecure\ubilogin-sso\ubilogin\webapps\<webapp>\WEB-INF\classes
from where it is copied toC:\Program Files\Ubisecure\ubilogin-sso\tomcat\webapps\<webapp>\WEB-INF\classes
during the installation process
Expand | ||
---|---|---|
| ||
Notes:
|
Shared include-logback.xml
file
….
Note about Windows console log
Links: