The bw.logger value from “=;tibco.home;/bw/5.10/lib/log4j.xml “ is not picked up as expected in BWSE.
Article ID: KB0090024
Updated On:
| Products | Versions |
|---|---|
| TIBCO ActiveMatrix BusinessWorks Service Engine | - |
| Not Applicable | - |
Description
Resolution:
Description:
========
The bw.logger value from “=<tibco.home>/bw/5.10/lib/log4j.xml “ is not picked as expected in BWSE.
Resolution:
=======
In AMX BWSE we, by default, rely on common logging (Node logger) and do not directly use BW SDK logging or log4j logging (bw.logger). In Classic BW, the log4j.xml file is located in the Engine CLASS PATH. This is the reason it will be able to load and use the log4j configuration. In BWSE, you may have to set/add the following engine properties to enable and refer to log4j logging.
Engine.Log.Type = log4j
bw.log4j.configuration=<tibco.home>/bw/5.10/lib/log4j.xml
Description:
========
The bw.logger value from “=<tibco.home>/bw/5.10/lib/log4j.xml “ is not picked as expected in BWSE.
Resolution:
=======
In AMX BWSE we, by default, rely on common logging (Node logger) and do not directly use BW SDK logging or log4j logging (bw.logger). In Classic BW, the log4j.xml file is located in the Engine CLASS PATH. This is the reason it will be able to load and use the log4j configuration. In BWSE, you may have to set/add the following engine properties to enable and refer to log4j logging.
Engine.Log.Type = log4j
bw.log4j.configuration=<tibco.home>/bw/5.10/lib/log4j.xml
Issue/Introduction
The bw.logger value from “=;tibco.home;/bw/5.10/lib/log4j.xml “ is not picked up as expected in BWSE.
Feedback
Yes
No
Powered by
