SA-28214

Summary

User have  AES 7.1.7 on PRPC 7.2.1.

 AES manager portal is not displaying the node information on enterprise health tab .

Error Messages

Rule-Connect-SOAP.PegaAES-Data-AlertOrigin.GetActivityData  - Exception
com.pega.pegarules.pub.services.RemoteApplicationException: SOAP service failed
    at com.pegarules.generated.activity.ra_action_invokeaxis_9ef2dcb432ce73a3cff35a859a998338.step9_circum0(ra_action_invokeaxis_9ef2dcb432ce73a3cff35a859a998338.java:1411)
    at com.pegarules.generated.activity.ra_action_invokeaxis_9ef2dcb432ce73a3cff35a859a998338.perform(ra_action_invokeaxis_9ef2dcb432ce73a3cff35a859a998338.java:205)
    at com.pega.pegarules.session.internal.mgmt.Executable.doActivity(Executable.java:3527)
    at com.pegarules.generated.activity.ra_action_invoke_8171c74e56fb26f2c41f9a69e39e4099.step8_circum0(ra_action_invoke_8171c74e56fb26f2c41f9a69e39e4099.java:1037)
    at com.pegarules.generated.activity.ra_action_invoke_8171c74e56fb26f2c41f9a69e39e4099.perform(ra_action_invoke_8171c74e56fb26f2c41f9a69e39e4099.java:189)
    at com.pega.pegarules.session.internal.mgmt.Executable.doActivity(Executable.java:3527)
    at com.pegarules.generated.activity.ra_action_executegetactivitydata_2b89bbb940a6a1b28105714de8f33cbc.step8_circum0(ra_action_executegetactivitydata_2b89bbb940a6a1b28105714de8f33cbc.java:829)
    at com.pegarules.generated.activity.ra_action_executegetactivitydata_2b89bbb940a6a1b28105714de8f33cbc.perform(ra_action_executegetactivitydata_2b89bbb940a6a1b28105714de8f33cbc.java:203)
    at com.pega.pegarules.session.internal.mgmt.Executable.doActivity(Executable.java:3527)
    at com.pega.pegarules.session.internal.mgmt.Executable.invokeActivity(Executable.java:10674)
    at com.pegarules.generated.activity.ra_action_getruleinfo_d8fba9ad84eeeaf00ab660592c0acd8b.step8_circum0(ra_action_getruleinfo_d8fba9ad84eeeaf00ab660592c0acd8b.java:793)
    at com.pegarules.generated.activity.ra_action_getruleinfo_d8fba9ad84eeeaf00ab660592c0acd8b.perform(ra_action_getruleinfo_d8fba9ad84eeeaf00ab660592c0acd8b.java:188)
    at com.pega.pegarules.session.internal.mgmt.Executable.doActivity(Executable.java:3527)
    at com.pega.pegarules.session.internal.mgmt.Executable.invokeActivity(Executable.java:10674)
    at com.pegarules.generated.activity.ra_action_researchorigins_b85a2d4be68d2552cd50ddd2a55b7b7b.step2_circum0_PegaAES_Data_AlertOrigin(ra_action_researchorigins_b85a2d4be68d2552cd50ddd2a55b7b7b.java:245)
 

Steps to Reproduce

Not Applicable

Root Cause

The user has updated soap servlet url of monitoring node on the PDC landing page of monitored node. Then, the user updated the exception and alert appenders in prlogging.xml of monitored node. Original connection string url  is showing  wrong monitored node url in  pegaaes-data-nodes instance for the operator aesdeveloper.
 

Resolution

All the exception and alert appenders related to AES has been removed .
User confirmed context root has been changed for monitored node .

So after updating  the correct monitored node url in new connection string of pegaaes-data-nodes ,system information started displaying .