Can we upgrade/update to 7.2.1 with hazelcast disabled?
**Re Creating this post here as directed by pega mesh community
Background: As part of our 7.1.8 upgrade we had to disable hazelcast ( by a prconfig setting <env name="identification/cluster/protocol" value="none" />). This is because the client security policy does not allow us to open up ports to other data centers. As per discussions with Pegasystems earlier this year looks like newer versions of pega ( 7.1.9 +) are adding more/disruptive features based on hazelcast clustering technology. So we want validate it before we update to 7.2.1
Question : Is turning on hazelcast a mandatory thing if we have to upgrade to 7.2.1? Please let us know.
**Re Creating this post here as directed by pega mesh community
Background: As part of our 7.1.8 upgrade we had to disable hazelcast ( by a prconfig setting <env name="identification/cluster/protocol" value="none" />). This is because the client security policy does not allow us to open up ports to other data centers. As per discussions with Pegasystems earlier this year looks like newer versions of pega ( 7.1.9 +) are adding more/disruptive features based on hazelcast clustering technology. So we want validate it before we update to 7.2.1
Question : Is turning on hazelcast a mandatory thing if we have to upgrade to 7.2.1? Please let us know.
--- If answer is YES, it kind puts a blocker in our way with the security concerns mentioned above)
Thanks
Pegasystems Inc.
US
yes. Clustering technology is mandatory for 721. Customer must determine how to either re-assess policy to allow for fairly standard clustering technologies to be deployed, or to engage pega consulting for recomendations to leverage advanced DBMS features to create a semi-split cluster.