7.6. Migrating eXo Platform cluster 4.0 to 4.1

Cluster configuration has been simplified in eXo Platform 4.1. The changes in summary:

This section helps you migrate your configuration once you upgrade from 4.0 to 4.1.

Quartz migration

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 variableNew variableJGroups name
jgroups.tcp.start_portexo.jcr.cluster.jgroups.tcp.start_portTCP start_port
jgroups.tcpping.initial_hostsexo.jcr.cluster.jgroups.tcpping.initial_hostsTCPPING initial_hosts
jgroups.tcpping.num_initial_membersexo.jcr.cluster.jgroups.tcpping.num_initial_membersTCPPING num_initial_members
jgroups.udp.mcast_addrexo.jcr.cluster.jgroups.udp.mcast_addrUDP mcast_addr
jgroups.udp.mcast_portexo.jcr.cluster.jgroups.udp.mcast_portUDP mcast_port
jgroups.udp.ip_ttlexo.jcr.cluster.jgroups.udp.ip_ttlUDP 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.

Copyright ©. All rights reserved. eXo Platform SAS
blog comments powered byDisqus