Activating hazelcast after switch from jboss to tomcat
Hi all,
we are currently switching from jboss to tomcat.
While we have used jboss as a loadbalancer between our 2 nodes we will now run tomcat and therefore will use embedded hazelcast (not client-server mode).
Can you tell me what settings we have to check that everything is running smoothly. We are going onto PEGA Infinity 23.1.1.
Updated: 28 Nov 2024 11:34 EST
Pegasystems Inc.
GB
To ensure that everything is running smoothly while switching from JBoss to Tomcat with embedded Hazelcast, you should check the following settings in the `prconfig.xml` file for each Pega Platform node: 1. Set the public address using the following setting: `<env name="identification/cluster/public/address" value="IP address" />`. For example, if the IP address of the node is Proprietary information hidden, add `<env name="identification/cluster/public/address" value=" Proprietary information hidden" />`. 2. Specify the IP address that Hazelcast uses to communicate with its cluster members by adding: `<env name="cluster/hazelcast/interface" value=" Proprietary information hidden" />`. Make sure to use only one IP address for this setting. These configurations will help manage the network traffic between the application server nodes running Pega Platform effectively.
⚠ This is a GenAI-powered tool. All generated answers require validation against the provided references.
Preparing to configure an Apache Tomcat application server
Please go through all the available documentation by carrying out a search :
To ensure that everything is running smoothly while switching from JBoss to Tomcat with embedded Hazelcast, you should check the following settings in the `prconfig.xml` file for each Pega Platform node: 1. Set the public address using the following setting: `<env name="identification/cluster/public/address" value="IP address" />`. For example, if the IP address of the node is Proprietary information hidden, add `<env name="identification/cluster/public/address" value=" Proprietary information hidden" />`. 2. Specify the IP address that Hazelcast uses to communicate with its cluster members by adding: `<env name="cluster/hazelcast/interface" value=" Proprietary information hidden" />`. Make sure to use only one IP address for this setting. These configurations will help manage the network traffic between the application server nodes running Pega Platform effectively.
⚠ This is a GenAI-powered tool. All generated answers require validation against the provided references.
Preparing to configure an Apache Tomcat application server
Please go through all the available documentation by carrying out a search :
@KOHNF is this something your team could help answer?