Mandatory Cluster Properties
Besides mandatory Cluster properties, you need to set other necessary properties which are not specifically related to the Cluster environment. Database connection must be also configured; however, besides direct connection, it is alternatively possible to configure proxing using another Cluster node/nodes. For details, see the property cluster.datasource.type.
These properties must be properly set on each node of the Cluster.
Table 42.1. Mandatory Cluster properties
Switch whether the Server should start in the standalone or Cluster node mode.
The property isn't set at all (empty value) by default,
which means that the mode is chosen according to the loaded license.
It is strongly recommended to set the property to |
|cluster.node.id||String||Each Cluster node must have a unique ID.||node01|
|cluster.jgroups.bind_address||String, IP address||An IP address of the ethernet interface which is used for communication with another Cluster nodes. Necessary for inter-node messaging.||127.0.0.1|
|cluster.jgroups.start_port||int, port||Port where a jGroups server listens for inter-node messages.||7800|
A URL of the CloverDX Cluster node.
It must be an HTTP/HTTPS URL to the root of a web application.
Typically it would be ||http://localhost:8080/clover|
|cluster.jgroups.tcpping.initial_hosts||String, in format: "IPaddress1[port1],IPaddress2[port2],..."||List of IP addresses (with ports) where we expect running and listening nodes. It is related to other nodes "bind_address" and "start_port" properties. Necessary for inter-node messaging.||127.0.0.1|
|sandboxes.home||String, URL||For more information, see sandboxes.home.|