Details
When the NFA 9.2 Console and Anomaly Detector 9.2 are installed on the same server it creates a conflict with the RIB service. This will cause either no NFA data or no AnomalyDetector data or both in CAPC.
**This does not impact NPC, only CAPC views**
If you look at the '\CA\NFA\RIB\logs\rib-wrapper.log' file you will see errors like below:
INFO: Servlet transport factory already registered
INFO | jvm 1 | 2014/01/09 16:08:43 | 2014-01-09 16:08:43.589:INFO::Deployable added: C:\CA\NFA\RIB\webapps\ADRIB
INFO | jvm 1 | 2014/01/09 16:08:46 | 2014-01-09 16:08:46.606:WARN::Failed startup of context o.e.j.w.WebAppContext{/ADRIB,file:/C:/CA/NFA/RIB/webapps/ADRIB/},C:\CA\NFA\RIB\webapps\ADRIB
INFO | jvm 1 | 2014/01/09 16:08:46 | java.lang.IllegalStateException: Web app root system property already set to different value: 'webapp.root' = [C:\CA\NFA\RIB\webapps\NFARS] instead of [C:\CA\NFA\RIB\webapps\ADRIB] - Choose unique values for the 'webAppRootKey' context-param in your web.xml files!
Solution
To work around this, you can update the web.xml file from the '\CA\NFA\RIB\webapps\ADRIB\WEB-INF' directory and add the lines below where 'D:\CA\NFA\RIB\webapps\ADRIB' reflects the drive and path that your ADRIB web.xml file is located.
Then save the file:
<context-param>
<param-name>webAppRootKey</param-name>
<param-value>D:\CA\NFA\RIB\webapps\ADRIB</param-value>
</context-param>
Once completed recycle the 'CA NFA RibSource' service and check the 'rib-wrapper.log' again for any new errors.
If no errors you should now be able to see your Anomaly Detector and/or NFA data in CAPC.
This also has been published as a Tech Doc on Support.ca.com here TEC604798.
This document was generated from the following discussion: Tech Tips: Anomaly Detector 9.2 on same server as NFA 9.2 Special Config