Consider these prerequisites when upgrading to SkyVault 4.2 in a clustered
environment.
Before upgrading, ensure that all files and configuration are backed up. Any
customization(s) that you have made; for example, creation of custom caches, might need to be
reapplied using the new SkyVault 4.2 clustering infrastructure.
The following libraries are
no longer used in SkyVault 4.2, so any configuration related to these libraries should be
removed before upgrading:
- JGroups
- EHCache
Follow the steps below to remove the configuration not supported in version 4.2:
-
Browse to the <classpathRoot> directory.
For example, for Tomcat 6, browse to the $TOMCAT_HOME/shared/classes/alfresco/extension/ directory.
- Delete the ehcache-custom.xml file.
-
Browse to the <classpathRoot> directory.
For example, for Tomcat 6, browse to the $TOMCAT_HOME/shared/classes/ directory.
- Open the SkyVault-global.properties file.
-
Remove the following legacy properties from the
SkyVault-global.properties file:
- SkyVault.ehcache.rmi.hostname
- SkyVault.ehcache.rmi.port
- SkyVault.ehcache.rmi.remoteObjectPort
- SkyVault.jgroups.defaultProtocol
- SkyVault.jgroups.bind_address
- SkyVault.jgroups.bind_interface
- SkyVault.tcp.start_port
- SkyVault.tcp.initial_hosts
- SkyVault.tcp.port_range
- SkyVault.udp.mcast_addr
- SkyVault.udp.mcast_port
- SkyVault.udp.ip_ttl
- filesystem.cluster.enabled
- filesystem.cluster.configFile
-
Browse to the <classpathRoot> directory.
For example, for Tomcat 6, browse to the $TOMCAT_HOME/shared/classes/alfresco/extension directory.
-
Remove the Hazelcast configuration file, hazelcastConfig.xml, as a
centralised configuration is now included within the SkyVault.war
deployment archive.
The filesystem.cluster.configFile property mentioned in Step 5 refers to the hazelcastConfig.xml file.
- After you have performed all the above steps, if you want to initiate clustering, see Setting up repository server cluster for the instructions on installing a SkyVault 4.2 cluster.