Support Article
AES not displaying all details in the Enterprise tab on AES Mgr
Summary
Autonomic Event Services (AES) 7.1.7 is setup on Tomcat and SQL Server database to monitor Pega 7.1.8 based applications on WebSphere / SQL Server database.
And, user is facing the following issues:
1) Lot of details are not being displayed in the AES Manager portal.
2) SOAP exceptions in AES logs (404 transport error).
3) AES is displaying the incorrect Node PRPC URL and Node SOAP endpoint URLs.
Error Messages
ERROR aesdeveloper - Exception
com.pega.pegarules.pub.services.RemoteApplicationException: SOAP service failed
at com.pegarules.generated.activity.ra_action_invokeaxis2_e0a499f26a95053ac6300b525bd7d41f.step15_circum0(ra_action_invokeaxis2_e0a499f26a95053ac6300b525bd7d41f.java:3994)
at com.pegarules.generated.activity.ra_action_invokeaxis2_e0a499f26a95053ac6300b525bd7d41f.perform(ra_action_invokeaxis2_e0a499f26a95053ac6300b525bd7d41f.java:308)
at com.pega.pegarules.session.internal.mgmt.Executable.doActivity(Executable.java:3500)
at com.pegarules.generated.activity.ra_action_invoke_c28ff8c27ac24045d30f5561679549d1.step8_circum0(ra_action_invoke_c28ff8c27ac24045d30f5561679549d1.java:1037)
at com.pegarules.generated.activity.ra_action_invoke_c28ff8c27ac24045d30f5561679549d1.perform(ra_action_invoke_c28ff8c27ac24045d30f5561679549d1.java:189)
at com.pega.pegarules.session.internal.mgmt.Executable.doActivity(Executable.java:3500)
at com.pegarules.generated.activity.ra_action_deferloadrunstate_2542e3edd7bf00eb1b0ea5e297332a9c.step5_circum0(ra_action_deferloadrunstate_2542e3edd7bf00eb1b0ea5e297332a9c.java:644)
Steps to Reproduce
1. Setup AES 7.1.7 on Tomcat and SQL Server database.
2. Configure it to monitor Pega 7.1.8 on WebSphere or SQL Server database.
3. Check if all the details are being displayed in AES manager portal.
4. Check if SOAP exceptions in AES logs.
Root Cause
No health appender were added in the prlogging.xml.
Resolution
Application name must be unique and prweb.war file name can be kept same for all applications. This would help resolve the incorrect URL issue.
For loading monitored node information (browser response time, cache summary) in the Enterprise tab on the AES Manager portal, add the AES Health Message appender and appender-ref in the prlogging.xml in the monitored node:
<appender name="AES-HEALTH-MSG" class="com.pega.pegarules.priv.util.SOAPAppenderPega">
<param name="BufferSize" value="512"/>
<param name="Blocking" value="false"/>
<param name="EndPointURL" value="http://<AES_Server:Port>/prweb/PRSOAPServlet"/>
<param name="Mode" value="ALERT" />
<param name="AllowLiveChanges" value="false"/>
<param name="OutputEnabled" value="true"/>
<layout class="com.pega.apache.log4j.PatternLayout">
<param name="ConversionPattern" value="%m%n" />
</layout>
</appender>
<appender name="ALERT-ASYNC" class="com.pega.apache.log4j.AsyncAppender">
<param name="BufferSize" value="512"/>
<param name="Blocking" value="false"/>
<filter class="com.pega.apache.log4j.varia.LevelMatchFilter">
<param name="LevelToMatch" value="ALERT"/>
<param name="AcceptOnMatch" value="true"/>
</filter>
<filter class="com.pega.apache.log4j.varia.DenyAllFilter"/>
<appender-ref ref="ALERT-PERFORMANCE"/>
<appender-ref ref="ALERT-SECURITY"/>
<appender-ref ref="ALERT-AES-SOAP"/>
// adding health appender
<appender-ref ref="AES-HEALTH-MSG"/>
</appender>
Published August 23, 2017 - Updated December 2, 2021
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.