Pega 8.8.2 Hazelcast Configuration

General
, , , ,
1

I have installed Pega 8.8.2 on WebSphere Application Server. There are four application servers running on four different hosts:

App Server devServer01 running on PServNode01 node on 172.30.149.14

App Server devServer02 running on PServNode02 node on 172.30.149.15

App Server devServer03 running on PServNode03 node on 172.30.149.16

App Server devServer04 running on PServNode04 node on 172.30.82.21

Please inform,

  1. if I should add the below JVM arguments for App Server devServer01 only or for all four App Servers?

–add-exports java.base/jdk.internal.ref=ALL-UNNAMED
–add-opens java.base/java.lang=ALL-UNNAMED
–add-opens java.base/java.nio=ALL-UNNAMED
–add-opens java.base/sun.nio.ch=ALL-UNNAMED
–add-opens java.management/sun.management=ALL-UNNAMED
–add-opens jdk.management/com.ibm.lang.management.internal=ALL-UNNAMED
–add-opens jdk.management/com.sun.management.internal=ALL-UNNAMED

  1. Will Pega select devServer01 as the hazelcast server if the above JVM arguments are added to devServer01only?

  2. Should I add the below lines in prconfig.xml (externalized) of App Server devServer01 only?

  1. Should I place prconfig.xml (externalized) in all four application servers and add the below lines to prconfig.xml files in all four servers?

Please inform.

2

@DebrajB16819133

Hi,

  1. if I should add the below JVM arguments for App Server devServer01 only or for all four App Servers?

If all the four devServer01 - devServer04 (preferable to call as JVM) under one Server, there’re 2 options you can achieve.

A. You can add required JVM arguments in the Primary / One JVM from Websphere and Sync it with all other 3 JVM’s if you have WAS / Middleware Team support as per your organization structure.

B. If no support from WAS Team but you have direct access to Websphere console, Please add all the required JVM arguments across all the 4 JVM’s manually through Websphere console and Save them.

Note: if you’re going with Option B, Make sure to plan the Application Maintenance so that the changes will apply. But with Option A, through Sync option, WAS / Websphere Team will make sure changes gets rolled out at the earliest.

  1. Will Pega select devServer01 as the hazelcast server if the above JVM arguments are added to devServer01only?

As per my Knowledge and experience, There’s no specific Nodetype triggers the Hazelcast clustering from Pega. But, Hazelcast is clustering technique which ever the nodetype first starts, Other nodetypes will follow the first one to join in the same cluster.

But as per On-Prem structure, below structure is recomended. Whichever the nodetype starts first, other node-types will join in the First node-type cluster.

Start-up sequence: Stream, BackgroundProcessing & Search, Webuser

Shutdown sequence: Webuser, BackgroundProcessing & Search, Stream

Based on the above input, there’s no valid point of hazelcast server and which one will follow etc…If you’re not going to add / maintain the JVM arguments across all the JVM’s, Application functionalities will be effected.

3 & 4. Should I add the below lines in prconfig.xml (externalized) of App Server devServer01 only? &

Should I place prconfig.xml (externalized) in all four application servers and add the below lines to prconfig.xml files in all four servers?

Eventhough, there’re the four different JVM’s, it’s practice to deploy the application with a single Application Jar file and you’ll need to update in that jar file which holds prconfig.xml and sync all the JVM’s (like I explained step a and step b in the second query).

Note: Feel free to click on the Accept Solution