This article provides steps to enable debug traces for SAS Infrastructure for Risk Management web application failures in Linux and Microsoft Windows operating environments.

Windows Operating Environments:

1. Open the SASIRM-log4j.xml file that resides in the SAS-configuration-directory\Lev1\Web\Common\LogConfig\ directory and locate the following code:
   <logger name="com.sas.solutions.risk.irm.mid" additivity="false">
      <level value="INFO" />
      <appender-ref ref="SAS_FILE"/>
      <appender-ref ref="SAS_CONSOLE"/>
   </logger>

   Update that code as follows:

   <logger name="com.sas.solutions.risk.irm.mid" additivity="false">
      <level value="DEBUG" />
      <appender-ref ref="SAS_FILE"/>
      <appender-ref ref="SAS_CONSOLE"/>
   </logger>
2. Stop and restart SASServer8_1.
3. Reproduce the problem and collect the following log data:
    
   • SAS-configuration-directory\Lev1\Web\Logs\SASServer8_1\SASIRM.log
   • SAS-configuration-directory\Lev1\Web\WebAppServer\SASServer8_1\logs\catalina.out

Linux Operating Environments:

1. Open the SASIRM-log4j file that resides in the SAS-configuration-directory/Lev1/Web/Common/LogConfig/ directory. Locate the following code lines:
   <logger name="com.sas.solutions.risk.irm.mid" additivity="false">
      <level value="INFO" />
      <appender-ref ref="SAS_FILE"/>
      <appender-ref ref="SAS_CONSOLE"/>
   </logger>

   Update those lines as follows:

   <logger name="com.sas.solutions.risk.irm.mid" additivity="false">
      <level value="DEBUG" />
      <appender-ref ref="SAS_FILE"/>
      <appender-ref ref="SAS_CONSOLE"/>
   </logger>
2. Stop and restart SASServer8_1.
3. Reproduce the problem with a Live ETL job, and collect the following log data:
    
   • SAS-configuration-directory/Lev1/Web/Logs/SASServer8_1/SASIRM.log
   • SAS-configuration-directory/Lev1/Web/WebAppServer/SASServer8_1/logs/catalina.out