SAP Hybris cluster : usage and limitations

Image for post
Image for post

What it is a cluster ?

In a computer system, a cluster is a group of servers (nodes) that act like a single system and enable high availability and, in some cases, load balancing and parallel processing.

More details here

How to configure an SAP Hybris cluster ?

SAP hybris cluster can be configured in three ways:

+ JGroups communication toolkit
+ UDP multicast
+ UDP unicast

To stay simple, I have choose the JGroups method !

Step 1: Activate the cluster mode in of each node

clustermode =true

Step 2: Set JGroups as the communication’s protocol in the SAP Hybris cluster ( of each node)


Step 3: Set cluster id

You can set cluster id of SAP Hybris nodes in two different ways :

  • Manually by setting in (different value per node)<cluster_id_integer>
  • Automatically by autodiscovery option (5.5 SAP Hybris version and above)

By using the second option SAP Hybris will calculate the cluster id and save it under the table “CLNodeInfos”, so if you try the following request in HAC (Hybris Administration Console)

select * from CLNodeInfos

You will get something like that :

Step 4: Set the JGroups’s communication protocol

  • Set the JGroupsBroadcastMethod as the communication listener between nodes,

JGroupsBroadcastMethod class is the SAP hybris’ implementation of JGroups listener

  • The SAP hybris implementation of JGroups support two transport protocols (TCP,UDP)

for TCP, you should put the following lines in your

# <node_ip> : is the ip address of the SAP hybris node
# communication port, by defaut it is 7800 as set by SAP hybris

And for UDP (default mode)

# the SAP hybris default upd multicast port

The default jgroups-udp.xml / jgroups-tcp.xml paths are


you can set any path in the properties cluster.broadcast.method.jgroups.configuration under, for example


Below an example of settings using Jgroups/TCP transport protocol/autodiscovery


How to configure an SAP Hybris cluster locally?

Make sure to unroll all the above steps and that you have change the following tomcat setting between nodes :


then run ‘ant server’ on each node under /bin/platform

ant server


- Once autodiscovery is activated, no way to control the interval ids (for example it is not possible to start autodiscovery from the id 5 and above)

- You can have duplicated node ids by using autodiscovery due to network communication issues

- By using autodiscovery, you can not exclude nodes from task execution since the id calculation is done dynamically


original post :

Written by

Jakarta ee & SAP Hybris architect | AWS Developer | DevOps Enabler

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store