Cluster configuration has been simplified in eXo Platform 4.1. The changes in summary:
Default protocol for JGroups is UDP.
JGroups configuration is externalized for both JCR and IDM.
Externalized variables are in exo.properties that replaces configuration.properties.
Variable namespaces are now exo.jcr.cluster and exo.idm.cluster.
There is no longer default standalone/configuration/gatein/jgroups/ files.
exo.properties is now recommended to configure JGroups.
Default JCR index is local in 4.1 (shared in 4.0).
quartz.properties and scripts are now provided in the package. Quartz datasource is defaulted.
This section helps you migrate your configuration once you upgrade from 4.0 to 4.1.
Quartz migration
Quartz datasource is now defaulted with the name exo-quartz.
quartz.properties is ready-made in standalone/configuration/gatein/quartz, and is
activated by -Dorg.quartz.properties.
This file matches the default datasource.
Quartz version is now 2.1.7, so it is recommended you re-create tables to avoid any possible incompatibility.
The scripts are packaged in standalone/configuration/gatein/quartz/dbTables.
JGroups externalized variables
In eXo Platform 4.0, a few JGroups properties (for JCR only) are configured via
$PLATFORM_JBOSS_HOME/standalone/configuration/gatein/configuration.properties.
If you have used those properties, you can migrate them to the new file -
$PLATFORM_JBOSS_HOME/standalone/configuration/gatein/exo.properties.
However, the names are changed. See the mapping:
| Old variable | New variable | JGroups name |
|---|---|---|
| jgroups.tcp.start_port | exo.jcr.cluster.jgroups.tcp.start_port | TCP start_port |
| jgroups.tcpping.initial_hosts | exo.jcr.cluster.jgroups.tcpping.initial_hosts | TCPPING initial_hosts |
| jgroups.tcpping.num_initial_members | exo.jcr.cluster.jgroups.tcpping.num_initial_members | TCPPING num_initial_members |
| jgroups.udp.mcast_addr | exo.jcr.cluster.jgroups.udp.mcast_addr | UDP mcast_addr |
| jgroups.udp.mcast_port | exo.jcr.cluster.jgroups.udp.mcast_port | UDP mcast_port |
| jgroups.udp.ip_ttl | exo.jcr.cluster.jgroups.udp.ip_ttl | UDP ip_ttl |
jgroups.bind_addr is now either
exo.jcr.cluster.jgroups.udp.bind_addr for UDP or
exo.jcr.cluster.jgroups.tcp.bind_addr for TCP.
Customized JGroups xml files
It is recommended that you alter to exo.properties to configure JGroups in 4.1.
However, if you want to re-use your customized JGroups xml files, it is possible.
See Using customized JGroups xml files to activate your files.
JCR indexing
eXo Platform 4.1 uses local JCR index by default. This is to make default configuration simpler. So if you were using shared index in 4.0, just re-configure to continue using it. Follow JCR index in cluster mode.