You can configure the OnDemand Decision Engine to enable key performance indicators (KPI) on the rules monitoring screen. The SAS OnDemand Decision Engine sends transactions to the Transaction Analysis Server (TAS) to generate two indicators: Customer Impact Ratio and Analysis Impact Ratio. In SAS Fraud Management 6.1 Hot Fix 9 and later, an error occurs in the TAS log when KPIs are enabled. The transactions are inserted into the Transaction Data Repository (TDR) database but are not indexed by TAS.

The error in the TAS console.log file is as follows:

2023-02-20 19:14:02,359 [WARN|ByteToTransactionDecoder:77|
nioEventLoopGroup-5-1] java.lang.NoClassDefFoundError:
org/apache/logging/log4j/LogManager
io.netty.handler.codec.DecoderException: java.lang.NoClassDefFoundError: org/apache/logging/log4j/LogManager
at io.netty.handler.codec.ByteToMessageDecoder.callDecode
(ByteToMessageDecoder.java:461)

Workaround

To work around this error, add an entry for Log4J2 to the end of the picklist file located in the SASHome/SASFraudTransactionalAnalysisEngine/6.1 directory. Then, restart TAS. 

An example of the Log4J2 entry to add is as follows:

Note: The value for the version can vary. To check for available versions on the server where TAS is installed, complete the following steps:

1. Change to the SASHOME/SASVersionedRepository/eclipse/plugins directory.  
2. Run the following: find . -name "Log4J2*" 
3. Use the latest Log4J2 version that is listed in the output.  

Important Notes

• You should use the -alwaysoverwrite option for the SAS^® Deployment Manager for future hot fix installations. Here is an example: ./sasdm.sh -alwaysoverwrite
• Future hot fix installations might overwrite the picklist file. After installing the hot fix, check the picklist file for a Log4J2 entry. If the entry does not exist, add it again. 
• This issue also occurs in SAS^® Fraud Management 4.4M1 (TS1M1) at Hot Fix 10 (version 5 release 16) and later.