Setting Up Log Levels

You can configure different log levels for the plug-in and plug-in activities to trace different messages. By default, the plug-in uses the log level configured for TIBCO ActiveMatrix BusinessWorks. The default log level of TIBCO ActiveMatrix BusinessWorks is Error.

1. Navigate to the TIBCO_HOME\bw\<version>\config\design\logback directory and open the logback.xml file.
2. Add the following node in the Console Appender area to specify the log level for the plug-in:

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

   The level tag defines the log level and the value of the level element can be Trace, Info, 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.
3. Optional: Add the following node in Console Appender area to specify the log level for an activity:

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

   See the following examples:
   • To set the log level of the Data Event Poller activity to Debug, you must add the following node:

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

   • To set the log level of the Data Merger activity to Debug, you must add the following node:

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

   • To set the log level of the Data Requester activity to the Debug options, you must add the following node:

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

   • To set the log level of the ADB Configuration shared resource to Debug, you must add the following node:

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

   Note: For the activities that do not configure with specific log levels, they still inherit log level configured for the plug-in or BusinessWorks.
4. Save the file.