Setting Up Log Levels

You can configure a different log level for the plug-in and plug-in activities to trace different messages.

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 BusinessWorks Palette and Activity loggers area to specify a log level for the plug-in:

   <logger name="com.tibco.bw.palette.hadoop.runtime">
       <level value="DEBUG"/>
     </logger>

   <logger name="com.tibco.bw.palette.webhdfs.runtime">
       <level value="DEBUG"/>
     </logger>

   <logger name="com.tibco.bw.sharedresource.webhdfs.runtime">
       <level value="DEBUG"/>
     </logger>
   

   <logger name="com.tibco.bw.sharedresource.hadoop.runtime">
       <level value="DEBUG"/>
     </logger>
   

   The value of the level element can be ERROR, INFO, or DEBUG.

   Note: If you set the log level 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 BusinessWorks Palette and Activity loggers area to specify a log level for an activity. The node varies according to the activity and the palette that it belongs to.
   • For activities in the HDFS palette:

     <logger name="com.tibco.bw.palette.webhdfs.runtime.ActivityNameActivity">
        <level value="DEBUG"/>
     </logger>

   • For activities in the Hadoop palette:

     <logger name="com.tibco.bw.palette.hadoop.runtime.ActivityNameActivity">
        <level value="DEBUG"/>
     </logger>

   For example, you can add the following node to set the log level of the HDFSOperation activity to DEBUG:

   <logger name="com.tibco.bw.palette.webhdfs.runtime.HDFSOperationActivity">
      <level value="DEBUG"/>
   </logger>

   Likewise, you can add the following node to set the log level of the Hive activity to DEBUG:

   <logger name="com.tibco.bw.palette.hadoop.runtime.HiveActivity">
      <level value="DEBUG"/>
   </logger>

   Note: The activities that are not configured with specific log levels use the log level configured for the plug-in.
4. Save the file.