3. Make sure all AES agents are running on the AES server and PegaAESREmote on the monitored nodes.
Go to the System Management Application on the AES Server as well as monitored Pega server and under Agent Management look for Agents that correspond to PegaAES and PegaAESRemote Rulesets respectively
4. Authentication at app server level (authentication profile set to match on AES remote)
You may need to use the AESRemoteUser authentication profile.
5. Examine legacy contents of prconfig and prlogging.xml and remove all AES entries.
prlogging.xml and prconfig.xml files (use dynamic appenders and PDC URL spec from ) should not have any legacy AES related appender or config settings respectively.
6. Check for SSL handshake issues between AES server and monitored node
Only applies if using HTTPS endpoints
7. Front end Webserver or Load balancer configurations:
If you have your AES or Pega application hosted on an Application server cluster front-ended by a web-server or a load balancer the SOAP messages used for AES to Pega communication cannot pass through to directly communicate. Then you need to make the monitored node or the AES node the front end url.