Configuration of logging framework in WAR file deployments.
- Armin Franke
Analytics
tia® Content Server is the only product of the tia® Core product line that ships as both container and WAR-file.
By end of 2025, the shipment of WAR-files stops and tia® Core product line will follow a container-only strategy.
By default, the tia® Content Server Core, when deployed as WAR-file for a web application server, logs to: core-of-tia.log file in <web application server>/WEB-INF/<web context>/logs directory.
Also log rotation is activated by default:
tia® Content Server core writes the log file
core-of-tia.loginto thelogssubdirectory of the web context directory.At 0:00am and in case the log file exceeds 1GB, it is gz-compressed and renamed to
core-of-tia-<n>.log.gz.Up to 10 compressed log files will be kept before removal.
Custom configuration
The log level can be configured for the complete product (parameter logging.level.root), or for a special module only (parameter logging.level.<package>).
The log row format, the log location, and other can be configured in a log configuration file (the default file shipped with the product is logback-spring.xml). It is recommended to create a new logging configuration file. Use parameter logging.config to point to the custom configuration file
The logging framework included in tia® Content Server Core is SLFJ4-compliant. For documentation refer to the https://www.slf4j.org/manual.html. Since tia® Content Server Core Release 3.0.0 this is Logback framework (see Logback Home).
tia® Content Server Core parameters for logging:
Parameter | Description | Supported Values | Required | Default value |
| Log Level for all logging. If log level for package is configured, package configuration will overrule. Recommended for Production is WARN or ERROR. |
| no |
|
Example:
| Definition of the log level for the package.
|
| no |
|
| Specifies a location for the configuration file of the logging framework. | Path and filename | no |
|
For more information how to apply these parameters, please read Application wide settings.
For example logging configuration files see: