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.ldap.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:

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

   Note: When setting up a log level for the LDAP Entry Listener activity, you have to change the activity name to MonitorEventSource. For other activities, you have to delete the word Entry from activity name.
   For example, add the following node to set the log level of the Search Entry activity to Debug:

   <logger name="com.tibco.bw.palette.ldap.runtime.SearchActivity">
      <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. For the AzureADOperation activity, you can enable the debug log by adding the following elements:

   <logger name="com.tibco.bw.palette.ldap.cloud.runtime.crud">
       <level value="DEBUG"/>
     </logger>
     
      <logger name="com.tibco.bw.sharedresource.ldap.cloud.runtime">
       <level value="DEBUG"/>
     </logger>
5. Save the file.