When the SAS Fraud Management web application reports an error or has performance issues, the default logging level might not be detailed enough to identify the cause of the issue. More detailed logging, including the SQL statements that are executing, is often useful for troubleshooting application issues.

You can use the following procedure to enable trace logging in SAS Fraud Management. You should implement these logging changes only during periods of low usage and for a short duration. Extensive logging can cause slowness in the application. Once you perform the actions that cause the error, immediately disable the trace logging.

Steps to enable trace logging:

1. Log on as the SAS installation/configuration user. Change to the SAS-configuration-directory/Lev1/Web/Common/LogConfig directory.
2. Make a backup of the SAS Fraud Management log4j configuration file. The file has a name that is similar to SASFraudMgmtMidTier4.4Auth-Domain-log4j.xml.
3. Edit the log4j configuration file and add the bold lines between the BEGIN FILE UPDATES and END FILE UPDATES lines, as shown below:
   <category additivity="false" name="com.sas.finserv">
      <priority value="INFO"/>
      <appender-ref ref="SAS_FILE"/>
   </category>
   <!-- BEGIN FILE UPDATES -->
   <category additivity="false" name="com.ibatis.sqlmap">
      <priority value="FINEST"/>
      <appender-ref ref="SAS_FILE"/>
   </category>
   <category additivity="false" name="java.sql">
      <priority value="FINEST"/>
      <appender-ref ref="SAS_FILE"/>
   </category>
   <!-- END FILE UPDATES -->
   <root>
      <priority value="warn"/>
      <appender-ref ref="SAS_FILE"/>
   </root>
4. Restart the SAS Web Application Server that is running the SAS Fraud Management web application.

   For example, if the web application server is SASServer8_1, then submit this command:

   cd SAS-configuration-directory/Lev1/Web/WebAppServer/SASServer8_1/bin
   /tcruntime-ctl.sh stop

   Wait for the web application server to stop. Then, run this command:

   ./tcruntime-ctl.sh start

   Wait for the web application server to fully start.

5. Log on to the SAS Fraud Management web application and perform the actions that cause the issue. Then, log off.
6. Remove the logging updates from the log4j configuration file. Or, copy the backup file that you create in step 2 back to its original location.

   Note: You might want to save a copy of the trace log4j configuration in case you need it in the future.

7. Restart the web-application server a second time.
8. Review the SAS Fraud Management web-application log.

For example, if the web application server is SASServer8_1, then the log is found in the SAS-configuration-directory/Lev1/Web/Logs/SASServer8_1 directory. The log file has a name that is similar to SASFraudMgmtMid-Tier4.4Auth-Domain.log