Jump to content

Logging in tibco BE

Neha Kathuria 2

Recommended Posts

  • 2 months later...

Hello - Please try the following:

1. Disable the default BE logging configuration. In the CDD editor in Studio, go to the 'Collections' tab, and select logConfig'. In the configuration options, UN-check the 'Enable' checkbox. This will disable the default logging configuration, which you must now replace with a custom logging configuration. Note that a logging configuration is already provided in your BE installation under %BE_HOME%/lib/ext/tpcl/apache/.

2. Although you may edit the BE-provided logging configuration in-place, it is recommended that you instead specify the path to your custom logging configuration using the following property in your be-engine.tra (under %BE_HOME%/bin/be-engine.tra):


For BE 5.6: java.property.log4j.configuration=file:C:/logconfigs/log4j.xml

For BE 6.1: java.property.log4j.configurationFile=file:///C:/logconfigs/log4j2.xml


3. For BE 5.6, no further configuration is needed, as the necessary slf4j-log4j bridge is already provided in your installation under %BE_HOME%/lib/ext/tpcl/slf4j-log4j12-1.7.28.jar. For BE 6.1, you will need to obtain the updated binding for log4j v2 from Maven Central:


4. Add the log4j-slf4j-impl-2.0.2.jar to the front of the classpath. You can do this with the 'tibco.env.CUSTOM_EXT_PREPEND_CP' property in your BE engine TRA file:

tibco.env.CUSTOM_EXT_PREPEND_CP=C:/jars/log4j-slf4j-impl-2.0.2.jarYou are now configured to emit slf4j logging messages via log4j.

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Create New...