Setting Up a Log Level

By default, the log level is Error . You can change the log level to trace different messages.

Note: If neither the plug-in log nor the BusinessWorks log is configured in the logback.xml file, the error logs of the plug-in are displayed in the Console view by default.

If the plug-in log is not configured but the BusinessWorks log is configured in the logback.xml file, the configuration for the BusinessWorks log is implemented by the plug-in.

Procedure

  1. Navigate to the TIBCO_HOME/bw/version_number/config/design/logback directory and open the logback.xml file.
  2. Add the following node in the User loggers area to specify the log level for the plug-in.
    <logger name="com.tibco.bw.palette.mft.runtime">
       <level value="DEBUG"/>
    </logger>

    The level tag defines the log level and the value is Error or Debug.

    Note: When the level is set to Debug, the input and output for the plug-in activities are also displayed in the Console view. See Log Levels for more details regarding each log level.
  3. Optional: Add the following node in the User loggers area to specify the log level for an activity.
    <logger name="com.tibco.bw.palette.mft.runtime.ActivityNameActivity">
       <level value="DEBUG"/>
    </logger>
    Note: For each activity , the ActivityName is:
    • Request Platform Server Transfer: PSTransfer
    • Wait for Platform Server Completion: PSTransferWaiter
    • Request Platform Server Transfer: ISTransfer
    • Wait for Platform Server Completion: ISTransferWaiter
    • Retrieve Audit Records: AuditMessage
    For example, to set the log level of the Request Platform Server Transfer activity to Debug, add the following node:
    <logger name="com.tibco.bw.palette.mft.runtime.PSTransferActivity">
       <level value="DEBUG"/>
    </logger>
    Note: If you do not configure a specific log level for an activity, the activity applies the log levels that you configured for the plug-in.
  4. Save the file.