Setting Up a Log Level

By default, the log level is Error. The plug-in allows you to 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 will be 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\6.3\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.twitter.runtime">
       <level value="DEBUG"/>
    </logger>

    The level tag defines the log level. The valid values are Info, Warn, Error, Debug, or Trace.

    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.twitter.runtime.ActivityNameActivity">
       <level value="DEBUG"/>
    </logger>
    For example, if you want to set the log level of the TwitterPublish activity to Debug, you need to add the following node:
    <logger name="com.tibco.bw.palette.twitter.runtime.TwitterPublishActivity">
       <level value="DEBUG"/>
    </logger>
    Note: The setup of the TwitterStreamListener activity is different from other activities. When you want to set up a log level for this activity, you need to add the following node:
    <logger name="com.tibco.bw.palette.twitter.runtime.eventsource">
       <level value="DEBUG"/>
    </logger>
    Note: For the activities that are not configured with specific log levels, they still use the log level configured for the plug-in or the BusinessWorks.
  4. Save the file.