Question

1
Replies
289
Views
Close popover
Tim Burton (TimB6627)
Pegasystems Inc.

Pegasystems Inc.
US
TimB6627 Member since 2016 1 post
Pegasystems Inc.
Posted: February 2, 2018
Last activity: October 12, 2018
Closed

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****

Pega Autonomic Event Services System Administration Installation and Deployment
Moderation Team has archived post,
Close popover This thread is closed to future replies. Content and links will no longer be updated. If you have the same/similar Question, please write a new Question.