Setting Up Log Levels

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

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 BusinessWorks Palette and Activity loggers area to specify a log level for the plug-in.
   For the activities in the SWIFT MT palette, add the following node:

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

   For the activities in the SWIFT MX palette, add the following node:

   <logger name="com.tibco.bw.palette.swiftmx.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. Add the following node in the BusinessWorks Palette and Activity loggers area to specify a log level for an activity:
   For the activities in the SWIFT MT palette, add the following node:

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

   Note: For each activity, the ActivityName is:

   • Parse SWIFT MT: Parser
   • Render SWIFT MT: Renderer
   • Route SWIFT MT: Router
   • Generate SWIFT BICPlusIBAN: BICPlusIBANGenerator
   • Validate SWIFT BICPlusIBAN: BICPlusIBANValidator

   For the activities in the SWIFT MX palette, add the following node:

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

   Note: For each activity, the ActivityName is:

   • Parse SWIFT MX: Mxparser
   • Render SWIFT MX: Mxrenderer
   For example, add the following node to set the log level of the Parse SWIFT MT activity to Debug:

   <logger name="com.tibco.bw.palette.swift.runtime.ParserActivity">
      <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.