This note explains how to enable SAS Model Manager debugging options that you can use to troubleshoot issues in SAS Model Manager. These instructions apply to releases 12.3,13.1, and 14.1 of SAS Model Manager.

• Dynamic Logging
• Using log4j Files

Dynamic Logging

For SAS Model Manager 14.1 and SAS^® Enterprise Decision Manager 3.1 and later, you can enable logging dynamically so that you do not need to restart the middle-tier web application servers.

To enable dynamic logging for the SAS Model Manager middle tier, follow these steps:

1. Log on to SAS Web Administration Console by navigating to http://host:port/SASAdmin. In this URL, host and port represent your specific host name and port number.
2. Select SAS Web Administration Console ► Application Management to display the list of applications.
3. Click Decision Manager Common Mid release-number.
4. Expand the Logging section in the right pane.
5. Select DEBUG for the com.sas.analytics.crm.ccs, com.sas.ci.saslogging, com.sas.dcm.workflow.impl, and org.springframework contexts.
6. Select Set Options.
7. Click Decision Manager release-number.
8. Expand the Logging section in the right pane.
9. Select DEBUG for the com.sas.analytics.crm.ccs, com.sas.ci.saslogging, com.sas.decisionbuilder, and org.springframework contexts.
10. Select Set Options.
11. Click Model Manager JavaSvcs release-number.
12. Expand the Logging section in the right pane.
13. Select DEBUG for the com.sas.analytics.modelmanager, com.sas.analytics.modelmanager.datastepclient, com.sas.analytics.modelmanager.server, and com.sas.modelmanager contexts.
14. Click Set Options.

The logging changes in the steps above on SAS Web Administration Console do not persist after you restart the SAS Decision Manager and Model SAS Manager web application server. If you want the changes to be permanent, you need to follow the steps in the section Using Log4j Files.

After you re-create the problem, send the following log files to SAS Technical Support:

• SASModelManagerrelease-number.log (from the SAS-configuration-directory/Levn/Web/Logs/SASServer11_1 directory)
• SASDecMgrShellrelease-number.log (from the SAS-configuration-directory/Levn/Web/Logs/SASServer7_1 directory)
• SASDecMgrCommonrelease-number.log (from the SAS-configuration-directory/Levn/Web/Logs/SASServer7_1 directory)
• server.log (from the SAS-configuration-directory/Levn/Web/WebAppServer/SASServerX_Y/logs directory, where SASServerX_Y specifies either SASServer7_1 and SASServer11_1)

Using log4j Files

Follow these instructions when SAS Technical Support requests that you enable SAS Model Manager debugging on the middle tier. These steps require that you restart SAS Web Application Server.

1. Log on to the middle-tier machine using the SAS installer account.
2. Stop the SAS Web Application Server instance where SAS Model Manager and SAS Decision Manager Common components are deployed. Typically, this server is either SASServer11_1 or SASServer7_1.
3. In the SAS-configuration-directory/Levn/Web/Common/LogConfig directory, create a backup of the SASModelManager-log4j.xml, SASDecMgrShell-log4j.xml, and SASDecMgrCommon-log4j.xml files.
4. In the SASModelManager-log4j.xml file, locate the following loggers:
   
   <category additivity="false" name="com.sas.modelmanager"> <category additivity="false" name="com.sas.analytics.modelmanager"> <category additivity="false" name="com.sas.analytics.modelmanager.datastepclient"> <category additivity="false" name="com.sas.analytics.modelmanager.server">
   Within each logger, change <category value="WARN"> to <category value="DEBUG">. Then, save the SASModelManager-log4j.xml file.
5. In the SASDecMgrCommon-log4j.xml file, locate the following loggers:
   
   <category additivity="false" name="com.sas.analytics.crm.ccs"> <category additivity="false" name="com.sas.ci.saslogging"> <category additivity="false" name="org.springframework"> <category additivity="false" name="com.sas.dcm.workflow.impl">
   Within each logger, change <category value="WARN"> to <category value="DEBUG">. Then, save the SASDecMgrCommon-log4j.xml file.
6. In the SASDecMgrShell-log4j.xml file, locate the following loggers:
   
   <category additivity="false" name="com.sas.decisionbuilder"> <category additivity="false" name="com.sas.analytics.crm.ccs"> <category additivity="false" name="com.sas.ci.saslogging"> <category additivity="false" name="org.springframework">
   Within each logger, change <category value="WARN"> to <category value="DEBUG">. Then, save the SASDecMgrShell-log4j.xml file.
7. Start the SAS Web Application Server instances on which where SAS Decision Manager and SAS Model Manager Common components are deployed. Typically, these server instances are SASServer7_1 and SASServer11_1.

After you re-create the problem, send the following log files to SAS Technical Support:

• SASModelManagerrelease-number.log (from the SAS-configuration-directory/Levn/Web/Logs/SASServer11_1 directory)
• SASDecMgrShellrelease-number.log from the SAS-configuration-directory/Levn/Web/Logs/SASServer7_1 directory)
• SASDecMgrCommonrelease-number.log from the SAS-configuration-directory/Levn/Web/Logs/SASServer7_1 directory.
• server.log from the SAS-configuration-directory/Levn/Web/WebAppServer/SASServerX_Y/logs directory where SASServerX_Y is SASServer7_1 and SASServer11_1.

Operating System and Release Information