Chapter 27 Configuring Logging Settings : Configuring BusinessEvents Logging Settings

Configuring BusinessEvents Logging Settings
To Make Logs Easier to Use
It's a good idea to use a separate log directory for each server running on a machine. You can do this by running the BusinessEvents servers with the -name option, or by setting a log directory name in the TRA files (or both). For example, in the TRA file for a specific inferencing node, you could set the directory as follows:

 
# Trace Properties
Engine.Log.Dir Inference1

 
The rest of this section provides a reference to the properties you can use to define logging behavior.
Number of log files to keep. When be.trace.log.maxsize is reached, a new log file is created for the next log entries. Files are created up to the be.trace.log.maxnum. The oldest file is deleted when a new file is added after this value is reached.
Note: BusinessEvents uses this property (and not engine.Log.MaxNum).
Note: BusinessEvents uses this property (and not engine.Log.Maxsize).
Default is tcp:7500.
Enable tracing to TIBCO Rendezvous. When enabled, log information is published as Rendezvous messages.
Default is be.engine.trace.
Allowed values: infoRole, errorRole, warnRole, userRole, debugRole
Default is infoRole, errorRole, warnRole, userRole.
Enables tracing to terminal.
(The property be.trace.log.dir is not used).
Default is logs (that is, a directory called logs under the working directory).