Is there any guide to setup Hazelcast Cluster Service directly on top of VM, without docker?
Hi All,
Is there any guide to setup Hazelcast Cluster Service directly on top of VM, without docker?
Thanks,
Ferdinan
***Edited by Moderator Marije to add Capability tags***
Accepted Solution
Updated: 23 Jan 2025 8:39 EST
Pegasystems Inc.
GB
@FerdinanP the documentation can be found here:
- Deploying external Hazelcast on a Virtual Machine cluster
- Connecting to your managed Hazelcast service
- CLSA Community: Externalizing Kafka, Elasticsearch and friends
If the below content answers your question, please mark this reply as 'Accepted Solution':
⚠ Below is a GenAI-powered tool. All generated answers require validation against the provided references.
Here's a comprehensive step-by-step guide to deploy and configure the Hazelcast Cluster Service:
@FerdinanP the documentation can be found here:
- Deploying external Hazelcast on a Virtual Machine cluster
- Connecting to your managed Hazelcast service
- CLSA Community: Externalizing Kafka, Elasticsearch and friends
If the below content answers your question, please mark this reply as 'Accepted Solution':
⚠ Below is a GenAI-powered tool. All generated answers require validation against the provided references.
Here's a comprehensive step-by-step guide to deploy and configure the Hazelcast Cluster Service:
- Prerequisites
- Pega Platform 8.8 or later
- A VM cluster environment (local or in a public cloud)
- prcluster_service.war file from your Pega Platform installation package
- Proper network connectivity between VMs in the cluster
- Java Runtime Environment (JRE) installed on the VMs
- Deployment Steps
a. Prepare the Environment
-
- Create a dedicated directory for the Hazelcast service on each VM
- Copy the prcluster_service.war file to this directory
- Ensure the required ports are open for Hazelcast communication (typically 5701)
b. Deploy the Service
-
- Extract the prcluster_service.war file
- Configure the application server (Tomcat/WebSphere/WebLogic) to host the service
- Deploy the WAR file to your application server
- Configuration
a. Update prconfig.xml Add the following configuration to your prconfig.xml file:
<env name="cluster/hazelcast/interface" value="YOUR_VM_IP_ADDRESS" />
Replace YOUR_VM_IP_ADDRESS with the actual IP address of your Hazelcast node.
b. Configure Communication
-
- Set up the connection details between the Pega cluster and Hazelcast cluster
- Configure the Dynamic System Settings (DSS) in the prconfig.xml file
- Ensure proper network connectivity between all nodes
- Verification Steps
- Start the Hazelcast service on each node
- Check the service logs for successful startup
- Verify cluster formation between nodes
- Test the connection from your Pega Platform installation
Important Notes:
- Ensure the database is available before starting the application to avoid initialization errors
- Repeat the configuration steps for each node in your cluster
- Monitor the cluster formation to ensure proper communication between nodes
- It's recommended to test the setup in a non-production environment first
HCA Healthcare
US
Yes you can set up a Hazelcast cluster directly on VMs without using Docker. Please check this link. thanks
https://docs.hazelcast.com/management-center/4.2021.06/getting-started
Bank Mandiri
ID
Hi @Sairohith,
Thanks for the response, but URL you shared is for Hazelcast Management Center. The one I asked is, how to setup hazelcast cluster service, using prcluster_service.war which included in Pega Platform installation package.
Regards,
Ferdinan
Accepted Solution
Updated: 23 Jan 2025 8:39 EST
Pegasystems Inc.
GB
@FerdinanP the documentation can be found here:
- Deploying external Hazelcast on a Virtual Machine cluster
- Connecting to your managed Hazelcast service
- CLSA Community: Externalizing Kafka, Elasticsearch and friends
If the below content answers your question, please mark this reply as 'Accepted Solution':
⚠ Below is a GenAI-powered tool. All generated answers require validation against the provided references.
Here's a comprehensive step-by-step guide to deploy and configure the Hazelcast Cluster Service:
@FerdinanP the documentation can be found here:
- Deploying external Hazelcast on a Virtual Machine cluster
- Connecting to your managed Hazelcast service
- CLSA Community: Externalizing Kafka, Elasticsearch and friends
If the below content answers your question, please mark this reply as 'Accepted Solution':
⚠ Below is a GenAI-powered tool. All generated answers require validation against the provided references.
Here's a comprehensive step-by-step guide to deploy and configure the Hazelcast Cluster Service:
- Prerequisites
- Pega Platform 8.8 or later
- A VM cluster environment (local or in a public cloud)
- prcluster_service.war file from your Pega Platform installation package
- Proper network connectivity between VMs in the cluster
- Java Runtime Environment (JRE) installed on the VMs
- Deployment Steps
a. Prepare the Environment
-
- Create a dedicated directory for the Hazelcast service on each VM
- Copy the prcluster_service.war file to this directory
- Ensure the required ports are open for Hazelcast communication (typically 5701)
b. Deploy the Service
-
- Extract the prcluster_service.war file
- Configure the application server (Tomcat/WebSphere/WebLogic) to host the service
- Deploy the WAR file to your application server
- Configuration
a. Update prconfig.xml Add the following configuration to your prconfig.xml file:
<env name="cluster/hazelcast/interface" value="YOUR_VM_IP_ADDRESS" />
Replace YOUR_VM_IP_ADDRESS with the actual IP address of your Hazelcast node.
b. Configure Communication
-
- Set up the connection details between the Pega cluster and Hazelcast cluster
- Configure the Dynamic System Settings (DSS) in the prconfig.xml file
- Ensure proper network connectivity between all nodes
- Verification Steps
- Start the Hazelcast service on each node
- Check the service logs for successful startup
- Verify cluster formation between nodes
- Test the connection from your Pega Platform installation
Important Notes:
- Ensure the database is available before starting the application to avoid initialization errors
- Repeat the configuration steps for each node in your cluster
- Monitor the cluster formation to ensure proper communication between nodes
- It's recommended to test the setup in a non-production environment first