Prerequisites for upgrades - Alfresco Content Services - 23.4 - 23.4 - Ready - Alfresco - external

Alfresco Content Services

Platform
Alfresco
Product
Alfresco Content Services
Release
23.4
License

There are a number of prerequisites for upgrading from a version of Content Services prior to 4.2 in a clustered environment.

Before upgrading, ensure that all files and configuration are backed up. Any customization(s) that you’ve made, for example, creation of custom caches, might need to be reapplied using the new Content Services clustering infrastructure.

The following libraries are no longer used in 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’re upgrading from Content Services 4.2. This information is only relevant if you’re upgrading from any version prior to 4.2.

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

  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 alfresco-global.properties file.
  5. Remove the following legacy properties from the alfresco-global.properties file:
    • alfresco.ehcache.rmi.hostname
    • alfresco.ehcache.rmi.port
    • alfresco.ehcache.rmi.remoteObjectPort
    • alfresco.jgroups.defaultProtocol
    • alfresco.jgroups.bind_address
    • alfresco.jgroups.bind_interface
    • alfresco.tcp.start_port
    • alfresco.tcp.initial_hosts
    • alfresco.tcp.port_range
    • alfresco.udp.mcast_addr
    • alfresco.udp.mcast_port
    • alfresco.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 centralized configuration is now included within the alfresco.war deployment archive. The filesystem.cluster.configFile property mentioned in Step 5 refers to the hazelcastConfig.xml file.
  8. After you’ve performed all the specified steps, if you want to initiate clustering, see Set up repository server cluster.