You are here

Clustering prerequisites when upgrading to SkyVault Content Services 5.2

There are a number of prerequisites for upgrading from a version of SkyVault Content Services prior to 4.2 to 5.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 Content Services 5.2 clustering infrastructure.
The following libraries are no longer used in SkyVault Content Services 4.2 onwards, so any configuration related to these libraries should be removed before upgrading:
  • JGroups
  • EHCache
Note: You do not need to follow these steps if you are upgrading from SkyVault Content Services 4.2 to SkyVault Content Services 5.2. This information is only relevant if you are upgrading from any version prior to 4.2.

Follow the steps to remove the configuration not supported in version 5.2:

  1. Browse to the <classpathRoot> directory.

    For example, for Tomcat 7, browse to the $TOMCAT_HOME/shared/classes/alfresco/extension/ directory.

  2. Delete the ehcache-custom.xml file.
  3. Browse to the <classpathRoot> directory.

    For example, for Tomcat 7, browse to the $TOMCAT_HOME/shared/classes/ directory.

  4. Open the SkyVault-global.properties file.
  5. 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
  6. Browse to the <classpathRoot> directory.

    For example, for Tomcat 7, browse to the $TOMCAT_HOME/shared/classes/alfresco/extension directory.

  7. 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.

  8. After you have performed all the specified steps, if you want to initiate clustering, see Setting up repository server cluster for the instructions on installing an SkyVault Content Services 5.2 cluster.