Decision Services flows can be remotely deployed to a SAS Real-Time Decision Manager run-time server environment through the remote-deployment feature that is available in a SAS Real-Time Decision Manager environment.

In a run-time server environment, an excessive number of the following warnings might be generated in the SASServer1_1 server.log file because a run-time server does not include SAS^® Customer Intelligence Studio software components:

Because the run-time server does not include SAS Customer Intelligence Studio, these warnings should not be generated.

To circumvent this problem, follow the steps below:

1. Make a backup copy of the SASWIPServices-log4j.xml, SASPrincipalServices-log4j.xml, and SASWIPClientAccess- log4j.xml files. These files are located in the following directory (where your middle-tier machine is configured):
   SAS-configuration-directory\LevN\Web\Common\LogConfig
2. Open the SASWIPServices-log4j.xml, SASPrincipalServices-log4j.xml, and SASWIPClientAccess-log4j.xml files. These files should contain the following category XML tag:
   <!-- ensures that unchecked exceptions are logged on the server side --> <category additivity="false" name="org.springframework.remoting.support.RemoteInvocationTraceInterceptor"> <priority value="WARN"/> <appender-ref ref="SAS_CONSOLE"/> <appender-ref ref="SAS_FILE"/> </category>

   Change the <priority> value from WARN to ERROR, as shown below:

   <!-- ensures that unchecked exceptions are logged on the server side --> <category additivity="false" name="org.springframework.remoting.support.RemoteInvocationTraceInterceptor"> <priority value="ERROR"/> <appender-ref ref="SAS_CONSOLE"/> <appender-ref ref="SAS_FILE"/> </category>
3. Restart the middle-tier SAS web application servers.

Click the Hot Fix tab in this note to access the hot fix for this issue.

Operating System and Release Information

A fix for this issue for SAS Marketing Automation 6.4 is available at: