How to generate debug logs for BW 6 application
Article ID: KB0082763
Updated On:
| Products | Versions |
|---|---|
| TIBCO ActiveMatrix BusinessWorks | 6.x |
Description
TIBCO ActiveMatrix BusinessWorks 6.x and TIBCO BusinessWorks Container Edition Log file configuration follows the Logback standard. (Refer to the Logback Project at http://logback.qos.ch/ for detailed information on configuration parameters.)
As a part of standard installation, BW Appnode logback.xml provide many (23) loggers which impacts different area of product. Most of the time when there are requirements to identify the business logic issue and to find out the path execution followed by job and activities, support engineers (production) / consultants / customers uses 'DEBUG' at root which generates many traces in logs and ultimately that reveals nothing.
As a part of standard installation, BW Appnode logback.xml provide many (23) loggers which impacts different area of product. Most of the time when there are requirements to identify the business logic issue and to find out the path execution followed by job and activities, support engineers (production) / consultants / customers uses 'DEBUG' at root which generates many traces in logs and ultimately that reveals nothing.
Issue/Introduction
This article list out the logback loggers which are responsible to generate BW 6.x / BWCE job & activity life cycle
Resolution
While troubleshooting BW 6.x / BWCE application issues, if administrators need BW job life cycle / activity execution time to be printed in appnode.log file, following combination is extremely helpful from application / business logic troubleshooting perspective.
====================
<logger name="com.tibco.bw.core">
<!-- Default <level value="WARN"/> -->
<level value="DEBUG"/>
</logger>
<logger name="com.tibco.bw.palette.generalactivities.Log">
<!-- Default <level value="DEBUG"/> -->
<level value="DEBUG"/>
</logger>
<logger name="com.tibco.bw.palette">
<!-- Default <level value="ERROR"/> -->
<level value="DEBUG"/>
</logger>
====================
Alternatively, you can use below pattern to shorten the log entry length:
=============================================================
<appender name="STDOUT" class="ch.qos.logback.core.ConsoleAppender">
<encoder>
<!-- default <pattern>%d{HH:mm:ss.SSS} %-5level [%thread] %logger{36} - %msg%n</pattern> -->
<!-- Customized <pattern>%d{HH:mm:ss.SSS} %-5level - %msg%n</pattern> -->
<pattern>%d{HH:mm:ss.SSS} %-5level - %msg%n</pattern>
</encoder>
</appender>
=============================================================
These loggers generates the limited traces which prints the job > process instance > activity life cycle, exactly what support / consultant needs. Setting above loggers produces similar result as setting 'Trace.Task.*=true' in 5.x tra files, please take a look at attached test details.
====================
<logger name="com.tibco.bw.core">
<!-- Default <level value="WARN"/> -->
<level value="DEBUG"/>
</logger>
<logger name="com.tibco.bw.palette.generalactivities.Log">
<!-- Default <level value="DEBUG"/> -->
<level value="DEBUG"/>
</logger>
<logger name="com.tibco.bw.palette">
<!-- Default <level value="ERROR"/> -->
<level value="DEBUG"/>
</logger>
====================
Alternatively, you can use below pattern to shorten the log entry length:
=============================================================
<appender name="STDOUT" class="ch.qos.logback.core.ConsoleAppender">
<encoder>
<!-- default <pattern>%d{HH:mm:ss.SSS} %-5level [%thread] %logger{36} - %msg%n</pattern> -->
<!-- Customized <pattern>%d{HH:mm:ss.SSS} %-5level - %msg%n</pattern> -->
<pattern>%d{HH:mm:ss.SSS} %-5level - %msg%n</pattern>
</encoder>
</appender>
=============================================================
These loggers generates the limited traces which prints the job > process instance > activity life cycle, exactly what support / consultant needs. Setting above loggers produces similar result as setting 'Trace.Task.*=true' in 5.x tra files, please take a look at attached test details.
Additional Information
http://logback.qos.ch/
Attachments
Feedback
Yes
No
Powered by
