Question
Rabobank
SE
Last activity: 4 Jul 2023 3:02 EDT
How to replace Hazelcast Jar files in Pega 8.6
Hi,
We found that there are some vulenaribilities with Hazelcast V3 in Pega 8.6.
We are trying to upgrade it to Hazelcast v4.2.7 , but there is no clear steps on how to upgrade. We removed the old jars from engine classes and imported v4.2.7. But after every restart, old hazel cast version jars are being created .
Can you someone point to the files and folders we need to use to update ? Pega Support docs are not helping.
Pegasystems Inc.
IN
Hazelcast 4.x EE requires an additional prconfig setting:
Prconfig value = “cluster/hazelcast/v4/enabled” = "true”
Upgrading to Hazelcast 4.x requires downtime. Therefore, consider which option to use:
- Keep the current Hazelcast version enabled during your installation of or upgrade to Pega 8.6.
- Install or upgrade to Pega 8.6 first and then take downtime to upgrade to Hazelcast 4.x.
Refer: section: Hazelcast 4.x with Pega 8.6 and later releases in https://support.pega.com/support-doc/updates-hazelcast-support#hazelcast-4x-pega86
Rabobank
SE
@SuhasKumar I read this document , but it did not say on exactly "How to upgrade to Hazelcast 4.x" .
We did some change and now Pega uses Hazelcast 4.x but the problem is old version Hazelcast 3.x is still in the tomcat path which the issue.
How do we remove the old jars ?
Pegasystems Inc.
IN
@Sarath Prashanth By Adding the prconfig, HZ v4 version will be in use. Pega Platform would handle the switch.
additional prconfig setting:
Prconfig value = “cluster/hazelcast/v4/enabled” = "true”.
As long as above setting is present, HZ v4 version will be in use.
Regarding HZ v3 jars, to patch the vulnerabilities, apply all critical hotfix(s) provided by Pega. For PegaCloud environments, critical hotfix(s) are applied automatically.
If they are still concerns, please raise support request , to get fix for the concerned issue.
It is not recommended to remove OOTB jars manually.