AES monitored nodes not sending messages to AES node
We have just moved to AWS, using PRPC 7.2 on RHEL/tomcat/Oracle. WE have AES installed in QUA & PRO. Trying to port back to DEV system. copied QUA AES DB and restored to DEV, and removed to known instances. I can login to AES console, but no instances are recognised. From the monitored nodes, under Endpoint SOAP URL definition, Test Connectivity fails. In DEV, I don't see the PEGA0008 message on server startup coming thru (that I can see in QUA/PRO). AES server restarts first, before monitored nodes. If the Test Connectivity can succeed, why doesn't the monitored node send the PEGA0008 on startup?
***Edited by Moderator Marissa to update platform capability tags****
Pegasystems Inc.
IN
Did you verify test connectivity from other environments to AES node.I hope it would be successful.Since test connection is getting failed in DEV so monitored node is not able to set up a connection with AES console(monitoring node).Please try to check the firewall opening and find out why connection is getting failed.
once this issue will be resolved then make sure that all the PegaAESRemote agents(mentioned below) are running on monitored node.
1.InitializeHealthInfo
2.PushLogUsageData
3.PushDBIndexes
4.PushGuardrailData