Question
standard chartered
MY
Last activity: 17 Jul 2017 1:04 EDT
AES connection string
Every time we restarted the monitored node, the connection string will become blank. It is not ideal for us to update the connection string every time we restart node.
Can somebody explain on this situation? Is this normal?
***Updated by moderator: Lochan to update Categories***
-
Like (0)
-
Share this page Facebook Twitter LinkedIn Email Copying... Copied!
Pegasystems Inc.
US
That sounds like a bug I've seen before. What version of AES are you using?
standard chartered
MY
AES 7.2
node version 7.2.2
attached is the log file
we configured the prconfig and prlogging file for the node to connect to the AES instead of using the PDC
Pegasystems Inc.
US
I believe Hfix-33866 resolves this issue. Please open an SR to request this hotfix and provide the SR number here for reference.
Pegasystems Inc.
US
Hmmm Hfix-31977 may also be applicable as well. I would recommend getting both.
Pegasystems Inc.
IN
Hi Norashikinr,
Refer the following article to get more information on obtaining the hotfix.
Raising Support Requests for Hotfixes now made easy!
Hope the information is helpful.
Thanks!
Pegasystems Inc.
AU
Hi,
These hotfixes are for AES and you have to apply on AES instance:
HFix-33866: change in step 14 of activity process_alert_line, you can verify post applying the fix
Similarly the HFix-3197: Change in activity PEGAAES-DATA-ALERT ALERTCREATENODE and activity PEGAAES-DATA-NODES NODECREATE
Regards,
Basavaraj
standard chartered
MY
Hi Basavaraj
just want to confim, i need to deploy both of the hotfixes?
Pegasystems Inc.
AU
yes, you may have to apply both the fixes
standard chartered
MY
Hi Basavaraj
please help to give the latest catalog file to install
its not available here
Pegasystems Inc.
AU
Hi,
Have you tired to click on the FTP link provided there? Is it not downloading?
Regards,
Basavaraj
standard chartered
MY
Hi,
I have tried, it not downloading.Please refer to attached screenshot and provide the valid link.
Ford Motor Company
US
Hi All,
We do got the same issue and its resolved by HFix.Its applicable for if your running Websphere as application server.
Hi All,
We do got the same issue and its resolved by HFix.Its applicable for if your running Websphere as application server.
Apply below hotfix:
HFIX-33089
HFIX-32365
Hfix-33866
HFIX-31977
HFIX-33972
HFIX-34665
IN AESREMOTE
hfix-31710
Regards,
Anandh Palanisamy
standard chartered
MY
Hi Basavaraj,
Am trying to find out what exactly got changed when we installed hotfix HFix-33866.
I have scanned both the activities (activity PEGAAES-DATA-ALERT ALERTCREATENODE and activity PEGAAES-DATA-NODES NODECREATE) but unable to find the any difference from previous versions of the activity.
Can you please help me finding what exactly got changed.
Thanks.
Regards,
Nora.