Usage Note 54926: Setting the debugging levels for logging in SAS® Digital Marketing 6.1_M1
To set the debugging level on the SAS Digital Marketing server and on platform log files, locate the log4j_rmi.xml file (in a directory location similar to SAS-configuration-directory\Lev1\Applications\SASCustomerIntelligence\SASDigitalMarketing\etc\) and set level values 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/">
<appender name="sdm_log" class="org.apache.log4j.DailyRollingFileAppender">
<param name="File" value="D:/SAS/Config/Lev1/Applications/SASCustomerIntelligence/SASDigitalMarketing/logs/sdm_server.log" />
<param name="Threshold" value="DEBUG" />
<param name="DatePattern" value="'.'yyyy-MM-dd" />
<layout class="org.apache.log4j.PatternLayout">
<param name="ConversionPattern" value="%d{ISO8601} [%-5p] %-40.40c - %m%n" />
</layout>
</appender>
<appender name="platform_log" class="org.apache.log4j.DailyRollingFileAppender">
<param name="File" value="D:/SAS/Config/Lev1/Applications/SASCustomerIntelligence/SASDigitalMarketing/logs/sdm_platform.log" />
<param name="Threshold" value="DEBUG" />
<param name="DatePattern" value="'.'yyyy-MM-dd" />
<layout class="org.apache.log4j.PatternLayout">
<param name="ConversionPattern" value="%d{ISO8601} [%-5p] %-40.40c - %m%n" />
</layout>
</appender>
<logger name="com.sas.email">
<level value="DEBUG"/>
<appender-ref ref="sdm_log"/>
</logger>
<logger name="com.sas.services">
<level value="DEBUG"/>
<appender-ref ref="platform_log"/>
</logger>
<logger name="CIExtension">
<level value="DEBUG"/>
<appender-ref ref="sdm_log"/>
</logger>
</log4j:configuration>
To increase the debugging level for the bess.war file, locate the SASDigitalMarketingWebReporting-log4j.xml file on the middle tier. That file is located in a directory similar to the following: SAS-configuration-directory\Lev1\Web\Common\LogConfig\. Then set the level values to DEBUG, as shown in this 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_bess_log" class="org.apache.log4j.FileAppender">
<param name="File" value="D:/SAS/Config/Lev1/Web/Logs/SASDigitalMarketingWebReporting6.1.log" />
<param name="Threshold" value="DEBUG" />
<layout class="org.apache.log4j.PatternLayout">
<param name="ConversionPattern" value="%d{ISO8601} [%-5p] %-30.30c{1} - %m%n" />
</layout>
</appender>
<logger name="JSP">
<level value="DEBUG"/>
<appender-ref ref="sdm_bess_log"/>
</logger>
<logger name="com.sas.email">
<level value="DEBUG"/>
<appender-ref ref="sdm_bess_log"/>
</logger>
</log4j:configuration>
After you set the levels, you need to restart SAS Remote Services, which also includes restarting all of the web servers (for example, SASServer1, SASServer2, and so on) in order for the modifications to take effect.
For instructions about setting the debugging level for the following SAS Customer Intelligence components, see SAS Note 50483, "Enabling debug logging in SAS Customer Intelligence 6.1 GA and 6.1_M1"
- SASCustintelReporting (logs updates to the Common Data Model)
- SASDigitalMarketingWeb(SDM.WAR for ebtool commands)
- SASCustIntelCore (SAS® Marketing Automation)
- SASCustIntelStudio (SAS® Customer Intelligence Studio)
- SASMarketingOptimization (SAS® Marketing Optimization)
Operating System and Release Information
| SAS System | SAS Digital Marketing | Solaris for x64 | 6.1 | | 9.3 TS1M2 | |
| Linux for x64 | 6.1 | | 9.3 TS1M2 | |
| HP-UX IPF | 6.1 | | 9.3 TS1M2 | |
| 64-bit Enabled Solaris | 6.1 | | 9.3 TS1M2 | |
| 64-bit Enabled HP-UX | 6.1 | | 9.3 TS1M2 | |
| 64-bit Enabled AIX | 6.1 | | 9.3 TS1M2 | |
| Microsoft® Windows® for x64 | 6.1 | | 9.3 TS1M2 | |
*
For software releases that are not yet generally available, the Fixed
Release is the software release in which the problem is planned to be
fixed.
| Date Modified: | 2015-02-04 12:30:30 |
| Date Created: | 2014-12-30 10:18:16 |
