Overriding the Default Logging Mode
You can disable the default logging mode and use the log4j mode for logging.
After the default logging mechanism is disabled, the log4j mode for logging is automatically activated. The default log4j configuration is located at
BE_HOME\lib\ext\tpcl\apache\log4j2.xml. You can also specify your custom log4j file location to be used for logging in the
be-engine.tra file.
- Procedure
- On the
Collections tab of the project's CDD, select an existing log configuration under the Log Configurations.
For details on how to add a log configuration, see Configuring Log Configurations.The log configuration properties are displayed.
- Clear the
Enable check box to disable the default logging mechanism.
Log Configurations Properties
- Save the CDD file.
- To use your custom log4j configuration, add the following property in the
be-engine.tra file. This property is specified in the be-rms.tra file for RMS and in the log4j.properties file for TIBCO BusinessEvents Enterprise Administrator Agent as shipped.
java.property.log4j.configurationFile=[custom_log4j_path]Note: If the file is not in the classpath but located elsewhere on your device, use the following path:java.property.log4j.configurationFile=file:///[custom_log4j_file_path]
Note: In TIBCO BusinessEvents, HTTP response logs are by default set to
Info level. To get the HTTP response debug logs for JSON and similar services, you must update the org.apache.http logger and set its log level to Debug in the log4j2.xml file.