Why would AES (7.13) display production level zero for the monitored clusters (7.1.9) in the Enterprise Health Console?
AES (7.13) displas production level zero for the monitored clusters (7.1.9) in the Enterprise Health Console for any clusters regardless of production levels of the monitored clusters. I checked the dynamic system settings and found that the dss for SearchSOAP URI (Pega-RULES • SearchSoapURI) and dss for Pega-Engine • prconfig/pdcconfig/altsoapurl/default are not different. what could be the root cause and resolution? The AES has Pega-RULES • SearchSoapURI in its connection string.
Pegasystems Inc.
IN
Hi Gyan, Kindly refer the below PDN article. https://community.pega.com/support/support-articles/aes-production-level-always-displays-0-zero You may need the Hfix to address the behavior.
Hawaii Medical Service Association
US
Hi Sushant,
Thanks, I checked the PDN article. There are other clusters configured earlier that have their production level reflected accurately. Only those that I am currently configuring are displaying zero and when I over over it, it has the tultip 'unknown'.
Pegasystems
IN
SearchSoapURI is used by the nodes within the cluster to point to one of the nodes where search index files are present. This node is identified on the search landing page in the index host nodes section. Note that this was only used till 7.1.6. From 7.1.7, with the introduction of Elastic Search, this is no longer used.
prconfig/pdcconfig/altsoapurl/default should point to the AES server and not to a node within the cluster.
Updated: 15 Mar 2016 2:23 EDT
It's similar to AES monitored node URL. The servlet name "PRServlet" is replaced with "PRSOAPServlet"
Sample connection URL: