AES not working after change to HTTPS URL
SummaryThe user have been using standalone AES for monitoring PRODUCTION environment. User have recently changed HTTP URL to HTTPS protocol in AES system. Since then, AES stopped monitoring PRODUCTION system.
The user have also ensured that all necessary AES SSL certificates have been installed into all production JVM Servers.
After user changed AES URL to https, they have logged into PRODUCTION SYSTEM and navigated to Designer studio --> system --> settings --> Predictive Diagnostic Cloud. In that landing page they have modified end point URL with the approriate "https" scheme.
Steps to Reproduce
- Enable site specifc TLS / HTTPS.
- Installed all necessary SSL Certificates in AES server and Monitored nodes.
- Logged into PRODUCTION SYSTEM and navigated to Designer studio --> system --> settings --> Predictive Diagnostic Cloud and updated URL to "https" scheme.
Root CauseA defect or configuration issue in the operating environment. The existing AES-Data-Nodes instances had stale connection string URLs.
Make the following change to the operating environment:
Navigated to each individual instances of AES-Data-Nodes class and updated the connection string values to reflect the correct scheme.
Published May 8, 2017 - Updated May 11, 2017