cancel
Showing results for 
Search instead for 
Did you mean: 
angelborroy
Community Manager Community Manager
Community Manager

This blog post describes a simple upgrading from a real Alfresco 5.2 deployment using default installer to Alfresco 7.0 deployment using Docker Compose.

Inventory for Alfresco 5.2

First step is to identify all the elements required to be migrated to the new environment.

Storage for PostgreSQL (DB), Repository (Content) and SOLR (Search Indexes)

  • alf_data/contentstore + alf_data/contentstoredeleted
  • alf_data/postgresql
  • alf_data/solr4

Configuration for Alfresco, Share and SOLR

  • Alfresco: tomcat/shared/classes/alfresco-global.properties
  • Share: tomcat/shared/classes/alfresco/web-extension/share-config-custom.xml
  • solr4/conf/shared.properties
  • solr4/workspace-SpacesStore/conf/solrcore.properties
  • solr4/archive-SpacesStore/conf/solrcore.properties

Customizations (Addons)

  • Alfresco: amps
  • Share: amps_share

Installing the new environment

Create a local deployment for testing the version. Alfresco Docker Installer may be used to generate this Docker Compose template: https://github.com/Alfresco/alfresco-docker-installer 

Once everything is working as expected, copy all the generated files to the new server and install on that server (if required) Docker & Docker Compose tools.

Deploying customisations

Verify that your original configuration for Alfresco Repository (alfresco-global.properties) has been applied to alfresco service in Docker Compose.

Verify that your original configuration for Alfresco Share (share-config-custom.xml) has been applied to share service in Docker Compose.

Since Alfresco 5.2 is using SOLR 4, likely your configuration won't be applicable to Alfresco 7.0, as it's based in SOLR 6 and it requires re-indexing all content and metadata from scratch. Anyway, you can also check that original SOLR configuration is present in Docker Compose.

Finally you need to check that Alfresco and Share addons are available in your Docker Compose.

Once all these elements are applied, test the environment again.

Upgrading process

Create a backup in your original Alfresco 5.2 for Database and Content Store.

Restore the backup for Database and Content Store in the new Alfresco 7.0.

After waiting some time (it depends on the size of the repository) to SOLR indexing process, Alfresco 7.0 will be ready to be used with the same customisations, content and metadata coming from Alfresco 5.2.

6 Comments