This note explains how to set the debugging level for the following files and components:

• SAS Digital Marketing 6.3, 6.4 and 6.5 log file
• SAS Digital Marketing 6.3, 6.4 and 6.5 BESS.WAR file
• SAS^® Digital Marketing Studio 6.3, 6.4 and 6.5 log file
• Other SAS^® Customer Intelligence 6.3, 6.4 and 6.5 components

Setting the Debugging Level in the SAS^® Digital Marketing 6.3, 6.4 and 6.5 Log File

To set the debugging level in the SAS Digital Marketing Server 6.3, 6.4 and 6.5 log file, follow these steps:

1. Locate the SASDigitalMarketingServer-log4j.xml file. This file resides in a location similar to D:\opt\sasinside\SAS-configuration-directory\Lev1\Web\Common\LogConfig\.


2. In SASDigitalMarketingServer-log4j.xml, set the value for the <level value=""/> parameter to DEBUG, as shown in the following example:
   <?xml version="1.0" encoding="UTF-8" ?>
   <!DOCTYPE log4j:configuration SYSTEM "log4j.dtd">
   
   <log4j:configuration xmlns:log4j="http://jakarta.apache.org/log4j/">
   
      <!-- %username and %X{sessionid} are the MDC keys for user name and session ID respectively -->
      <appender name="sdm_mid" class="org.apache.log4j.FileAppender">
         <param name="file" value="${config.lev.web.appserver.logs.dir}/SASDigitalMarketingServer6.3.log" />
         <param name="Threshold" value="DEBUG" />
         <param name="Encoding" value="UTF-8" />
         <layout class="org.apache.log4j.PatternLayout">
    
            <param name="ConversionPattern" value="%d{ISO8601} %p [%X{sas.session.id}] [%X{sas.user.name}]
                                                                  [%X{sas.local.session.id}] %c{1} %m %n"/>
   
         </layout>
      </appender>
   
      <appender name="sdm_migration" class="org.apache.log4j.FileAppender">
         <param name="file"     value="${config.lev.web.appserver.logs.dir}/SASDigitalMarketingMigration6.*.log" />
         <param name="Threshold" value="DEBUG" />
         <param name="Encoding" value="UTF-8" />
         <layout class="org.apache.log4j.PatternLayout">
   
            <param name="ConversionPattern" value="%d{ISO8601} %p [%X{sas.session.id}] [%X{sas.user.name}]
                                                                  [%X{sas.local.session.id}] %c{1} %m %n"/>
   
         </layout>
      </appender>
   
      <logger name="JSP">
         <level value="DEBUG"/>
         <appender-ref ref="sdm_mid"/>
      </logger>
   
      <logger name="com.sas.email">
         <level value="DEBUG"/>
         <appender-ref ref="sdm_mid"/>
      </logger>
   
      <logger name="com.sas.migration">
         <level value="DEBUG"/>
         <appender-ref ref="sdm_migration"/>
      </logger>
   
   </log4j:configuration>
3. Then, ensure that you have set the debugging level in the same manner as for other components in SAS Customer Intelligence 6.3, 6.4 and 6.5. Set the logging level on the Environment Variables workspace page, as described in the "Set Logging Level" section of "Chapter 2: Administration" for example, in the SAS^® Marketing Automation 6.3: Administrator’s Guide

    

Setting the Debugging Level for the SAS^® Digital Marketing BESS.WAR File

To set the debugging level for the BESS.WAR file, follow these steps:

1. Locate the SASDigitalMarketingTracking-log4j.xml file on the middle tier. This file resides in a location similar to D:\SAS\SAS-configuration-directory\Lev1\Web\Common\LogConfig\.
2. In SASDigitalMarketingTracking-log4j.xml, set the value for the <level value=""/> parameter to DEBUG, as shown in the following example:
   <?xml version="1.0" encoding="UTF-8" ?>
   <!DOCTYPE log4j:configuration SYSTEM "log4j.dtd">
   
   <log4j:configuration xmlns:log4j="http://jakarta.apache.org/log4j/">
   
   <!-- %username and %X{sessionid} are the MDC keys for user name and session id respectively -->  
       <appender name="sdm_mid" class="org.apache.log4j.FileAppender">
          <param name="file"    value="${config.lev.web.appserver.logs.dir}/SASDigitalMarketingTracking6.3.log" />   
         <param name="Threshold" value="DEBUG" />
         <param name="Encoding" value="UTF-8" />
         <layout class="org.apache.log4j.PatternLayout">
   
            <param name="ConversionPattern" value="%d{ISO8601} %p [%X{sas.session.id}] [%X{sas.user.name}]
                                                                  [%X{sas.local.session.id}] %c{1} %m %n"/>
   
         </layout>
      </appender>
   
      <logger name="JSP">
         <level value="DEBUG"/>
         <appender-ref ref="sdm_mid"/>
      </logger>
   
      <logger name="com.sas.email">
         <level value="DEBUG"/>
         <appender-ref ref="sdm_mid"/>
      </logger>
   
   </log4j:configuration>
3. Restart the SAS Digital Marketing BESS server so that these modifications take effect.

Setting the Debugging Level in the SAS^® Digital Marketing Studio 6.3, 6.4 and 6.5 Log File

To set the debugging level for the SAS Digital Marketing Studio, follow these steps:

Note: When you download the sample log file, rename it to log4j_studio.xml.

1. Right-click this link and select Save target as to download a sample log file to your LogConfig directory. The LogConfig directory resides in a location similar to this one: D:\opt\sasinside\SAS-configuration-directory\Lev1\Web\Common\.
2. Locate the studio.ini files in both of the following directories:
   • D:\opt\sasinside\SAS-configuration-directory\Lev1\Applications\SASCustomerIntelligence\SASDigitalMarketing\
   • D:\opt\sasinside\SAS-configuration-directory\Lev1\Applications\SASCustomerIntelligence\SASDigitalMarketingClient\
3. In these files, modify the following FILE path in the JavaArgs_nn= parameter to match the log4j_studio.xml filename, as shown below:
   JavaArgs_nn=-Dlog4j.configuration="file:D:\opt\sasinside\Config\Lev1\Web\Common\LogConfig\log4j_studio.xml"

   Note: In this example, nn represents the Java argument number in the sequence of numbers as they appear in your files.

4. Restart the SAS Digital Marketing web server (for example SASServer6) so that these modifications take effect.

Setting the Debugging Level for Other SAS Customer Intelligence 6.3, 6.4 and 6.5 Components

To set the debugging level for other components in SAS Customer Intelligence 6.3, 6.4, and 6.5, you need to set the logging level on the Logging page in the Environment Variables workspace, as described in the "Set Logging Level" section of "Chapter 2: Administration" in the SAS^® Marketing Automation: Administrator’s Guide for your release.

Operating System and Release Information